Error Response Format
REST maps gRPC errors to non-2xx HTTP statuses, with top-levelcode and message fields. For example, a rate-limit rejection returns HTTP 429:
200 response can also contain a business error object. Check both the HTTP status and error; the response schema defines its service-level or endpoint-specific error fields.
Service-level Errors
Service-level errors useerror.serviceErrorCode and can be shared across endpoints. The API contract defines the following code for an organization’s pending signing request limit:
If this error is returned, reject pending signing requests before retrying creation. It is separate from request-rate limiting; automatic retries alone do not resolve it.
Common Error Codes
HTTP Status Codes
Rate limits
Enforced rate limits return HTTP429 or gRPC RESOURCE_EXHAUSTED with rate limit exceeded. Retry with exponential backoff and jitter; the API currently returns no retry interval. Request limits are managed by MPCVault and can differ by API.
For retried writes, follow Idempotency.