intercom-common-errors

# Intercom Common Errors ## Overview Quick reference for Intercom API errors by HTTP status code, with real error response shapes and proven solutions. ## Intercom Error Response Shape All Intercom errors return this structure: ```json { "type": "error.list", "request_id": "req_abc123", "errors": [ { "code": "unauthorized", "message": "Access Token Invalid" } ] } ``` ## Error Reference ### 401 Unauthorized ```json { "type": "error.list", "errors": [{ "code": "unauthorized", "message": "Access Token Invalid" }] } ``` **Causes:** - Access token is expired, revoked, or malformed - Using a test token against production (or vice versa) - Token was regenerated in Developer Hub but not updated in app **Fix:** ```bash # Verify token works curl -s https://api.intercom.io/me \ -H "Authorization: Bearer $INTERCOM_ACCESS_TOKEN" \ -H "Accept: application/json" | jq '.type' # Should return "admin" # If invalid, regenerate at: # app.intercom.com > Settings > Developer Hub > Your App > Authentication ``` --- ### 403 Forbidden ```json { "type": "error.list", "errors": [{ "code": "forbidden", "message": "You do not have permission to access this resource" }] } ``` **Causes:** - OAuth app missing required scope - Trying to access a resource in another workspace - Admin permissions insufficient **Fix:** Add the required OAuth scope in Developer Hub > OAuth Scopes. --- ### 404 Not Found ```json { "type": "error.list", "errors": [{ "c...