Pluma
Docs index

Get started

What Pluma is Concepts First 5 minutes

Guides: the 5 steps of every site

Step 1 · Create the site Step 2 · Invite your agent Model your content Create and publish content Step 3 · Connect the MCP Images and files Step 4 · Invite your team Step 5 · Deploy on Netlify Deploy on Vercel Generic webhook deploy Composable pages Migrate from repo files Staging and previews Languages Migrate from Contentful · pending Billing · pending AI visibility Analytics AI answers Search Console and Bing Site preview

API

API · conventions Delivery API Preview API Management API Agents Webhooks

MCP

MCP MCP tools MCP OAuth

Reference

Rich text

Errors

Errors Error: check_unavailable Error: invalid_body Error: invalid_key Error: invalid_parameter Error: invite_expired Error: invite_used Error: key_cannot Error: missing_key Error: not_found Error: rate_limited Error: translation_unavailable Error: validation_failed Error: version_conflict Error: wrong_space

Frameworks

Astro Plain fetch
docs/errors/translation_unavailable.md View markdown →

translation_unavailable

HTTP 503 · The translation couldn't run.

Why it happens

  • Pluma has no AI provider key on this server, so Translate with AI is off.
  • The AI provider didn't answer, answered with an error, or sent back something unreadable.

details.reason says which one. Nothing was saved: the entry has the same versions it had.

How to fix it

Try again in a minute. If it keeps failing, write the translation yourself with PATCH /api/v1/spaces/:space_id/entries/:id?locale=en, or update_entry with locale. See Languages.

Example

{
  "error": {
    "code": "translation_unavailable",
    "message": "The translation couldn't run.",
    "fix": "details.reason says why: Pluma has no AI provider key, or the provider didn't answer. Nothing was saved; try again in a minute.",
    "doc_url": "https://pluma.so/docs/errors/translation_unavailable",
    "details": { "reason": "OpenAI answered 429: You exceeded your current quota" }
  }
}