Errors

Every error response has the same format. It includes a stable code that your code can check, a message that describes what went wrong, a hint that explains how to fix it, a link to the error code's page, and the traceId that identifies the request in your logs.

{
  "success": false,
  "error": {
    "code": "CONNECTION_NOT_FOUND",
    "message": "No connected account was found for this request.",
    "hint": "The user may not have connected this provider yet. Start a connection with PyasConnect.",
    "status": 404,
    "traceId": "trc_5f2a9c1e7b3d4a6f8e0c2b1d",
    "docs": "https://developer.pyas.io/errors/CONNECTION_NOT_FOUND"
  }
}

• Check code in your error handling, never message. Messages are written for people and can be improved over time, but codes don't change.
• Write hint to your logs, where developers can read it.
• Keep the traceId. Include it when you contact support so that we can help you faster. To see what the request did, how the provider responded and why the request failed, call the endpoint below or run pyas logs get trc_...:

GET /v2/logs/{traceId}

The error codes are also available as data, for use in your tooling and your coding agent. This request returns every code with its status, causes, fix, whether retrying helps, and related codes:

GET https://api.pyas.io/v2/errors

Status codes

Every code