invalid_requestThe body is not valid JSON, or the asset type is unknown.
What to do: Fix the request. Sending it again unchanged fails again.
insufficient_creditsThe workspace has fewer credits than the job costs. Nothing was charged.
What to do: Add credits at fix.url, or send fewer leads.
spend_cap_reachedThe job would take this API key past its monthly credit cap. Nothing was charged.
What to do: Send fewer leads, or ask a workspace owner to raise the cap at fix.url. Caps reset on the 1st (UTC).
plan_requiredA write (any method but GET, or an MCP tool that creates or changes something) on a workspace with no paid plan or trial with a card. Reads still work.
What to do: Show the user fix.url and stop writing. GET /workspace shows the same state in plan.
not_foundThe id is unknown, malformed, or belongs to another workspace. Over MCP with OAuth: the workspace slug is not yours, or you are in no workspace yet.
What to do: Use an id this workspace returned. No workspace yet: create one (fix.url, or create_workspace over MCP).
campaign_not_eligibleThe campaign_id is not active with automatic page generation on.
What to do: Leave out campaign_id, or fix the campaign at fix.url.
idempotency_conflictThe Idempotency-Key was used in the last 24 hours for a different request.
What to do: Use a new key for a new request. Send the exact same request to get the first job back.
brand_not_readyThe brand is still being read from its website.
What to do: Wait for the brand job with GET /jobs/{id}, then send the request again.
template_not_usableThe template call to action has no destination.
What to do: Show the user fix.url to finish the template in the app.
validation_failedA field is invalid, or every lead was rejected. errors[] lists each field.
What to do: Fix the listed fields and send again.
too_many_leadsMore than 25 leads in one job.
What to do: Split the leads into jobs of 25 and send them one at a time.
rate_limitedA limit was reached. The limit field says which one.
What to do: Wait the Retry-After seconds, then send the same request again.
internal_errorA bug on our side. It is logged with the request_id.
What to do: Retry once. If it repeats, contact support with the request_id.