Error Handling
HTTP status codes and how to handle them
The Partners API uses standard HTTP status codes. All error responses include a JSON body with details.
Status codes
Error response format
Standard errors
Validation errors (422)
Validation errors include structured information about which fields failed:
Each error in the array includes:
type— the type of validation failureloc— the path to the invalid fieldmsg— a human-readable messageinput— the value that was provided
Handling specific errors
402 — Out of Partner API credits
Credits are split into six independent buckets (donors, enhancements,
exports, lists, networks, searches). When the bucket an endpoint
charges is empty, that endpoint returns 402 — even if your other buckets
still have a balance. The response body names the exhausted bucket:
To handle it:
- Stop sending requests to the affected endpoint
- Check your per-bucket balances with
GET /credits - Purchase more credits for that bucket (contact your account manager)
400 — Bad request
Common causes:
- Too many items: Enhancement requests are capped at 100 persons, result requests at 10 job IDs, progress requests at 1,000 job IDs, bulk member adds at 100 donor IDs
- Duplicate list name: List names must be unique within your team
- Non-removable list: System lists (like “All Saved Donors”) can’t be deleted
- Missing fields: Export requests require the
fieldsparameter
429 — Rate limited
Implement exponential backoff:
500 — Server error
These are rare. If you encounter one:
- Retry the request once after a short delay
- If it persists, contact support@donoratlas.com with the request details