REST API
Review endpoint and authentication concepts.
Explore →DEVELOPER DOCUMENTATION
REST API
Work with GeoLayers collection and feature endpoints over HTTP.
Browser-based GISGeoAI + spatial analyticsSouth African context
GUIDE
Published collections
Only layers explicitly published through the API workflow should be exposed. Database/project tables remain private by default.
GUIDE
Feature queries
The API supports collection discovery and feature retrieval with common parameters such as bbox, limit, offset and property selection where available.
GUIDE
Authentication
Use the API key type appropriate to the application. Do not pass credentials in query strings.
GUIDE
Errors and limits
Design integrations to handle validation errors, authentication failures, missing resources and HTTP 429 rate limits without endless retry loops.
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.