Errors and rate limits

Peerlogic uses HTTP status codes and JSON response bodies to report request failures.

Common responses

Status	Meaning	Recommended action
`400`	The request contains invalid parameters or data.	Read the response body and correct the request.
`401`	Authentication is missing, invalid, or expired.	Request a token and verify the Bearer header.
`403`	The account cannot access the requested resource.	Confirm the account’s assigned access with Peerlogic.
`404`	The endpoint or resource was not found.	Verify the path and resource identifier.
`405`	The endpoint does not allow that HTTP method.	Use a method listed in the API Reference.
`429`	The request was rate limited.	Wait before retrying and honor `Retry-After` when present.
`500`, `502`, `503`, `504`	The service is temporarily unable to complete the request.	Retry with bounded exponential backoff.

Error bodies vary by endpoint. A response can contain a top-level message:

{
  "detail": "Authentication credentials were not provided."
}

Validation errors can identify individual fields or parameters:

{
  "practice_ids": [
    "Enter a valid practice identifier."
  ]
}

Retry safely

Retry only failures that may be temporary, such as 429 and 5xx responses. Use exponential backoff with jitter, cap the number of attempts, and avoid retrying invalid requests without changing them. Rate limits can vary by endpoint and customer agreement. If you need confirmed limits for your integration, contact Peerlogic before choosing a sustained request rate.

Start here

Core Concepts

Workflows

Common responses

Retry safely

​Common responses

​Retry safely

Common responses

Retry safely