OERENA

Documentation · Guides

Usage and troubleshooting

OERENA Document Intelligence API reference and integration guidance.

Usage, monitoring, and troubleshooting

Developer Console usage shows safe aggregates such as request counts and success/failure activity. Application grants show quota controls. The runtime records safe operational metrics including pages, status, latency, and request ID where applicable; it does not store OCR text in usage telemetry.

Troubleshooting

  • 401: verify the key, its status, and environment.
  • 403: verify an active capability grant.
  • 413: reduce the file size.
  • 415: use a valid PDF, JPEG, or PNG.
  • 429: respect Retry-After and inspect grant limits.
  • 5xx: retain request_id, retry safely where appropriate, and contact support.

Contact OERENA support with request_id, UTC time, status, and environment—never credentials or document text.