REST API
Review endpoint and authentication concepts.
Explore →
Connect Spatial Automation outputs to trusted HTTPS services.
Spatial Automation webhooks require HTTPS/CORS-compatible endpoints in the browser execution model.
Keep webhook payloads bounded and include only the run metadata or feature content needed by the receiving system.
Credential-bearing headers are removed from stored browser workflow definitions. Authenticated receivers should sit behind trusted server or edge infrastructure.
Developer Platform 2.0 can generate schemas for automation completion events so receiving systems can validate the structure they expect.
Use this checklist to reduce avoidable integration problems.
Use the related documentation pages to move from concept to a tested development workflow.