REST API
Review endpoint and authentication concepts.
Explore →DEVELOPER DOCUMENTATION
Developer Platform Limits
Understand rate limits, collection limits and browser execution boundaries.
Browser-based GISGeoAI + spatial analyticsSouth African context
GUIDE
Why limits exist
GeoLayers intentionally bounds browser-side analysis, automation and API requests so the interface stays responsive and users can understand the scale of the operation.
GUIDE
Automation
Spatial Automation currently bounds workflow count, step count, history size, source feature count, webhook payload size and minimum interval.
GUIDE
Developer access
Public APIs apply request/feature limits and rate controls. Integrations should page through data instead of assuming a single unlimited response.
GUIDE
Analytical modules
Specialist modules such as Earth Observation, GeoML and Mobility also use browser-appropriate limits; large production workloads may require preprocessing or server-side execution.
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.