Errors and conflicts

Branch on the code, retry reads freely, and re-read before you change anything after a 409

Checked 2026-10-05

Every failed call on api.sylphx.com answers with one shape. Branch on code and status, log detail for a person, and never parse it: its wording is not a contract.

JSON

{
  "code": "UNAUTHENTICATED",
  "detail": "Send `Authorization: Bearer <Sylphx key>`.",
  "retryable": false,
  "status": 401
}

#Statuses

Field	Type	What it is
`400`	INVALID_ARGUMENT	A field, cursor or page size is wrong, and the detail names it. Retrying unchanged fails the same way.
`401`	UNAUTHENTICATED	There is no bearer key on the request. Send a Sylphx Access key with the workflows scope the call needs.
`404`	NOT_FOUND	The schedule does not exist, or is not in the key's scope.
`409`	conflict	The stored state disagrees with the request. Read the schedule again and reapply the change on top of what you read.
`501`	UNIMPLEMENTED	The method is not served. Creating and updating a Schedule are declared in sylphx.toml.
`5xx`	retryable	An unexpected failure. Retry the call after a pause.

Was this page helpful?

Tell us what is missing, wrong, or unclear — this opens a real inbox.

Send feedback

Platform links