Skip to main content

Error Shape

Structured API errors use this shape:
Some validation errors may also include a details array. Future SDK methods should throw an Error when the API returns a non-2xx response. Log the backend requestId when support needs to trace a request.

Common Error Codes

Jurat API errors may include codes such as:
  • INVALID_SIGNER
  • INVALID_AUTH
  • INVALID_TOKEN
  • EXPIRED_TOKEN
  • INVALID_PASSWORD
  • UNAUTHORIZED
  • INPUT_VALIDATION_ERROR
  • NO_RECOVERY_CASE_TXS
  • RECOVERY_STATUS_ERROR
  • UNMATCHED_JRC_HASH
  • API_KEY_NOT_FOUND
  • EXCEEDED_API_KEY_AMOUNT
  • USER_FOUND
  • USER_NOT_FOUND
  • RESOURCE_NOT_FOUND
  • NO_FILE_UPLOADED
  • INVALID_FILE_FORMAT
  • NO_FILE_BUFFER
  • INTERNAL_SERVER_ERROR

Webhooks

Webhooks notify integrators when long-running recovery state changes. Recommended endpoint format:
Recommended event envelope:

Event Types

  • recovery_case.created
  • recovery_case.pending
  • recovery_case.rejected
  • recovery_case.executed
  • recovery_case.action_required

Webhook Security

Each webhook should include:
The signature should be an HMAC over:
Partners should reject old timestamps and replayed event IDs.