DEVELOPER DOCUMENTATION

Webhook Integrations

Connect Spatial Automation outputs to trusted HTTPS services.

Browser-based GISGeoAI + spatial analyticsSouth African context
GUIDE

Use HTTPS

Spatial Automation webhooks require HTTPS/CORS-compatible endpoints in the browser execution model.

GUIDE

Payloads

Keep webhook payloads bounded and include only the run metadata or feature content needed by the receiving system.

GUIDE

Secrets

Credential-bearing headers are removed from stored browser workflow definitions. Authenticated receivers should sit behind trusted server or edge infrastructure.

GUIDE

Event contracts

Developer Platform 2.0 can generate schemas for automation completion events so receiving systems can validate the structure they expect.

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 →