attio-common-errors

# Attio Common Errors ## Overview Every Attio API error returns a consistent JSON body. This skill covers the real error codes, response format, and proven solutions for each. ## Attio Error Response Format All errors from `https://api.attio.com/v2` return this structure: ```json { "status_code": 429, "type": "rate_limit_error", "code": "rate_limit_exceeded", "message": "Rate limit exceeded, please try again later" } ``` Fields: `status_code` (HTTP status), `type` (error category), `code` (specific code), `message` (human-readable). ## Error Reference ### 400 Bad Request -- `invalid_request` ```json { "status_code": 400, "type": "invalid_request_error", "code": "invalid_request", "message": "..." } ``` **Common causes and fixes:** | Message pattern | Cause | Fix | |----------------|-------|-----| | `Invalid value for attribute` | Wrong type for attribute slug | Check attribute type with `GET /v2/objects/{obj}/attributes` | | `Cannot query historic values` | Used history param on unsupported type | Remove `show_historic` for that attribute | | `Missing required field` | Required attribute not provided | Check `is_required` on attribute definition | | `Invalid filter format` | Malformed filter object | Use shorthand `{ "email": "x" }` or verbose `{ "$and": [...] }` | **Diagnostic:** ```bash # List attributes to verify types curl -s https://api.attio.com/v2/objects/people/attributes \ -H "Authorization: Bearer ${ATTIO_API_KEY}" \ | jq '.data[] | {slug: .a...