Errors
The Planning Center API uses the following error codes:
| Error Code | Description | Example Cause |
|---|---|---|
400 |
Bad Request | Something is wrong in your request |
401 |
Unauthorized | You did not use the proper API token and/or secret. |
403 |
Forbidden |
You tried to view a resource you don't have access to You tried to create a resource, but your user has an insufficient role. |
404 |
Not Found | You've tried to access a URL or resource ID that doesn't exist. |
409 |
Conflict |
A conflict occurs when creating a resource encounters a uniqueness validation error. Normally uniqueness errors will be returned in a 422 Validation Error. There are some cases (a multi-threaded application) where multiple threads will send simultaneous requests to create the same resource. If you are encountering this error, please make sure that you're app is only sending a single create request for a resource. If there is only one request, please file a bug report by creating an issue on Github |
422 |
Validation Error |
The value you have passed for an attribute isn't valid. The response body will provide the attribute that is invalid. Note: There can be more than one invalid attribute. |
500 |
Internal Server Error | We had a problem with our server. Try again later. |
503 |
Service Unavailable | We're temporarily offline for maintenance. Please try again later. |
Additionally, your error code may include an error hint.
| Error Hint | Description |
|---|---|
BLACKBIRD |
The request includes an unsupported kind parameter. |
CHINCHILLA |
The client application was not found or is invalid. |
FLAMINGO |
The authenticated user does not exist. |
LEMMING |
The authenticated organization does not exist. |
PELICAN |
The provided OAuth token does not have a required scope. |
BABOON |
The provided OAuth access token is expired. Prior to March 2025 this also included revoked OAuth tokens. |
CAPUCHIN |
The provided OAuth access token has been revoked. |
TRASH_PANDA |
The authenticated person does not have access to the requested application. |
WEASEL |
The signature's scope is not valid for the requested path. |
ANTEATER |
Signature validation failed with a missing authorization header. |
BLUE_JAY |
Signature authentication failed because the authorization header is an incorrect format. |
MOCKINGBIRD |
The signature authentication failed because of an invalid token. |