REST API
Review endpoint and authentication concepts.
Explore →DEVELOPER DOCUMENTATION
API Authentication
Understand browser keys, server keys, origins and credential boundaries.
Browser-based GISGeoAI + spatial analyticsSouth African context
GUIDE
Accounts
GeoLayers uses authenticated accounts for cloud projects, subscriptions and collaboration. Keep credentials private and use supported account-recovery flows rather than sharing logins.
GUIDE
Project access
Projects carry access context such as ownership and collaboration. Application modules should respect the project access state rather than bypassing it.
GUIDE
Developer credentials
Public API keys are managed separately from interactive account authentication. Browser keys may be origin-restricted; server keys should remain confidential.
GUIDE
Security boundary
Do not place service-role secrets, private API keys or authentication tokens into frontend code, downloadable manifests or Spatial Automation workflow definitions.
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.