docs
UAEN
Docs/Platform/Troubleshooting

Troubleshooting

Common problems when working with Rekognita API and their solutions.

401 Unauthorized

Reason: Invalid or missing API key.

  • Check if the key starts with rk_sk_, rk_rk_, or rk_test_
  • Ensure the key hasn't been deactivated in the Dashboard
  • Check the header: Authorization: Bearer rk_sk_... (not API-Key)

429 Rate Limit

Reason: Too many requests.

  • Implement exponential backoff
  • Utilize the Retry-After header
  • Consider upgrading your plan: Limits

Low OCR Quality

Solution:

  • Use the rekognita-accurate model instead of rekognita-fast
  • Ensure the document has an image resolution ≥ 300 DPI
  • For scanned documents — check contrast and tilt
  • Specify the language parameter for better recognition

Processing Timeout

Reason: Document is too large or complex.

  • Split the document into sections (page_range parameter)
  • Use rekognita-fast for high volumes
  • Use webhooks instead of synchronous requests

Tables not recognized

  • Use rekognita-accurate — this model performs best with tables
  • Ensure that tables have distinct borders
  • Try the graph output format: Graph Structure

Webhooks not arriving

  • Check if your server is accessible from the internet
  • Ensure the endpoint returns 200 OK
  • Check logs in Dashboard → Webhooks → Delivery Log
  • Make sure the URL uses HTTPS

Contacting Support

If the issue persists, reach out to us: