doc_url links to the section on this page for the returned code:
Request-Id header. Include it when contacting support@replo.app about a failed request.
invalid_request
Status: 400. The request body or query parameters are malformed, or theReplo-Api-Version header is missing or unsupported. The message explains what failed validation; fix the request and retry.
When the request fails validation, issues lists each rejected field (param, a dotted path such as name or variants.0.available) and why, up to 10. param is null for a rule that covers the whole request.
invalid_credentials
Status: 401. The API token is missing or invalid. Send your public API key as a bearer token in theAuthorization header. If the key was revoked, create a new one from your Replo Settings.
forbidden
Status: 403. The request is authenticated but was rejected outright. Ask a workspace owner to perform the action or to grant the key’s creator access. Note that a key missing a required scope does not get this response: scope and access failures surface as not_found so responses never confirm private resource IDs.not_found
Status: 404. The resource doesn’t exist, the key lacks a required scope, or the key’s creator lost access. Replo returns the same status for all three cases, so API responses do not confirm private resource IDs. If a known resource returns 404, check the key’s scopes in your Replo Settings and its creator’s current project access.conflict
Status: 409. The resource is in a state that conflicts with the request, such as a message sent while the agent is still working on the previous one, or while the session has a pending interaction. Wait for the turn to finish or resolve the interaction, then retry.rate_limit_exceeded
Status: 429. Too many requests. Wait for the number of seconds in theRetry-After header before retrying.
internal_error
Status: 500. Something failed on Replo’s side. Retry the request; if it keeps failing, contact support@replo.app with theRequest-Id header value.