Support
Error Reference
Every error code from the OnePath Connect API, explained.
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Human-readable description",
"details": []
}
}
| Code | Cause | Resolution |
|---|
INVALID_API_KEY | API key doesn't exist or was revoked | Check your key in the Partner Portal |
EXPIRED_API_KEY | Key has passed its expiry date | Rotate your key in the Partner Portal |
INVALID_CONSENT_TOKEN | JWT signature invalid or partner claim mismatch | Verify your private key and partner ID |
EXPIRED_CONSENT_TOKEN | JWT exp claim is in the past | Generate a fresh consent token |
MISSING_CONSENT_TOKEN | X-Consent-Assertion header absent | Include the consent token header |
| Code | Cause | Resolution |
|---|
INSUFFICIENT_SCOPE | Consent token scope doesn't cover this operation | Re-generate token with required scope |
PARTNER_SUSPENDED | Partner account is suspended | Contact partners@onepath.health |
| Code | Cause | Resolution |
|---|
USER_NOT_FOUND | No user with this ID exists for your partner | Verify the userId; call /onboard if new |
| Code | Cause | Resolution |
|---|
USER_ALREADY_EXISTS | externalId already onboarded | Use the existing user's onepath userId |
| Code | Cause | Resolution |
|---|
VALIDATION_ERROR | One or more fields failed validation | Check details array for field-level errors |
INVALID_FHIR_RESOURCE | Observation doesn't conform to FHIR R4 | Validate against the FHIR R4 spec |
UNSUPPORTED_CODE_SYSTEM | Code system not in LOINC/SNOMED CT | Use supported terminology systems |
| Code | Cause | Resolution |
|---|
RATE_LIMIT_EXCEEDED | Over 100 req/min in production | Respect Retry-After header; implement backoff |
Safe to retry. Use exponential backoff.