1. Scope
These Developer & API Terms supplement the Terms of Service. They apply to API keys, public collection endpoints, OGC API services, SDKs, generated OpenAPI contracts, webhooks, developer app profiles and related integration features.
2. Credentials
Treat server-side API keys, tokens and secrets as confidential. Do not embed confidential credentials in public JavaScript, mobile bundles that expose them, public repositories, screenshots, exported automation files or client-deliverable documents.
Browser keys are designed to be public identifiers and must be restricted using the supported origin and permission controls. A browser key should not be treated as a substitute for server-side authorization where confidential access is required.
3. Published collections and data scope
API access is limited to collections, properties and capabilities deliberately published by an authorized user. Publishing a collection may expose data to anyone who has the applicable key or, where configured, to the public. Review personal-information, confidentiality and source-licence restrictions before publishing.
4. Rate and usage limits
You must respect documented request limits, pagination, maximum page sizes, payload limits, timeouts and retry guidance. Do not intentionally distribute requests across multiple credentials or accounts to evade plan or rate limits.
Clients should implement bounded retries and exponential/backoff behavior for 429 or transient server errors rather than aggressive retry loops.
5. Webhooks
Use HTTPS endpoints for production webhooks. Validate incoming requests using the verification mechanism provided by the relevant GeoLayers feature where available. Do not assume a webhook was delivered exactly once; integrations should be designed to tolerate retries and duplicate events where applicable.
6. SDKs and generated code
SDKs, examples, OpenAPI files, TypeScript declarations, environment templates and code samples are provided to help integration. They may contain errors or require adaptation for your environment. You remain responsible for security review, testing, dependency management and production deployment.
7. Security testing
Do not bypass key expiry, origin restrictions, access controls, rate limits or other security mechanisms. Good-faith security testing that could affect production systems requires prior written authorization.
Report security concerns to info@geolayers.co.za.
8. OGC and interoperability
GeoLayers may expose selected OGC API capabilities. Only capabilities expressly documented as supported should be relied upon. The existence of an endpoint does not imply certification or support for every optional OGC conformance class.
9. Compatibility and versions
GeoLayers may evolve APIs, SDKs and schemas. Where a versioned contract is provided, design integrations against that version and monitor release notes. GeoLayers will use reasonable efforts to avoid unnecessary breaking changes but does not promise indefinite support for every preview or legacy interface.
10. Usage data and logs
GeoLayers may log requests, collection identifiers, status codes, timing, IP/security information and usage counters to provide the service, enforce limits, investigate incidents and improve reliability, subject to the Privacy Policy.
11. No resale of the API service
Unless authorized in writing, you may not resell raw GeoLayers API access or create a competing data/API service that primarily republishes GeoLayers-provided content. You may build legitimate applications and client solutions using the APIs within your plan and data licences.
12. Suspension and revocation
GeoLayers may rate-limit, rotate, expire or revoke credentials and may suspend an integration for security risk, abuse, material breach, non-payment or unlawful activity. Where appropriate, GeoLayers will attempt to provide notice and a path to remediation.
13. Attribution and licences
You are responsible for preserving attribution and licence obligations attached to datasets delivered through the API. An API response does not erase third-party rights or metadata requirements.
14. Contact
Developer questions: info@geolayers.co.za
Documentation: Developer Platform and Documentation