Developer Documentation
API Error Handling
Reference guide for FundraiserMax API error responses, status codes, and troubleshooting common error scenarios.
Error Handling
The FundraiserMax API uses standard HTTP status codes to indicate the outcome of a request. Error responses include a JSON body with a consistent structure to help you diagnose issues programmatically.
Error Response Format
{
"statusCode": 400,
"error": "Bad Request",
"message": "Validation failed: 'email' must be a valid email address.",
"details": [
{ "field": "email", "issue": "must be a valid email address" }
]
}Status Codes
| Code | Name | Description |
|---|---|---|
| 400 | Bad Request | The request body or query parameters are invalid. Check the details array for field-level validation errors. |
| 401 | Unauthorized | Missing or invalid API key or bearer token. Verify your X-API-Key and Authorization headers. |
| 403 | Forbidden | The API key does not have permission for this resource, or the request IP is not in the allowlist. |
| 404 | Not Found | The requested resource does not exist. Double-check the ID in your request path. |
| 429 | Too Many Requests | Rate limit exceeded. Wait the number of seconds in retryAfter before retrying. |
| 500 | Internal Server Error | An unexpected error occurred on the server. If this persists, contact support with the requestId from the response headers. |