DEVELOPER DOCUMENTATION

API Errors & Troubleshooting

Interpret common HTTP errors and integration problems.

Browser-based GISGeoAI + spatial analyticsSouth African context
GUIDE

Authentication errors

Confirm that the key type matches the client, the key has not expired or been revoked, and browser origins are allowed where required.

GUIDE

404 and collection errors

Confirm the collection is published and enabled, and that the requested collection or feature identifier is correct.

GUIDE

429 rate limits

Respect Retry-After when supplied and reduce request frequency or page size rather than retrying aggressively.

GUIDE

Browser integration issues

Check HTTPS, CORS policy, network connectivity and whether the requested operation exceeds browser-side limits.

IMPLEMENTATION CHECKLIST

Before you move to production

Use this checklist to reduce avoidable integration problems.

  • Test the workflow with a small, known dataset before increasing scale.
  • Keep production credentials outside public source code and downloadable configuration files.
  • Handle network, validation and rate-limit errors explicitly in the client or service.
  • Record the collection, endpoint, version or workflow configuration used so the integration can be reproduced.
NEXT STEP

Continue with a practical integration

Use the related documentation pages to move from concept to a tested development workflow.

API

REST API

Review endpoint and authentication concepts.

Explore →
SDK

JavaScript SDK

Use typed client helpers in an application.

Explore →

Automation

Connect spatial workflows to integrations.

Explore →