Skip to main content
The API Reference tab contains generated endpoint documentation for teams that automate SDX outside the portal. The public base URL is:
Use the product documentation first when you are learning how SDX features behave. Use the generated API groups when you already know the workflow you want to automate and need endpoint names, request shapes, response fields, and authentication details.

​
Before You Build

  • Use the paths exactly as shown in this reference. Several SDX services are mounted behind gateway prefixes such as /api, /workflows, /vpn, /content, /metrics, /reports, and /scripts.
  • Confirm the portal workflow manually before automating it.
  • Use API keys only for integrations that need server-to-server access.
  • Store credentials in a secret manager or the SDX vault where appropriate.
  • Prefer the narrowest role and team access that lets the integration do its job.
  • Test automation in a non-critical team or site before you run it across production.

​
What Is Included

This reference focuses on APIs that customers encounter in the portal or use for product automation. Internal service-to-service endpoints, local development endpoints, health checks, and backend-only token exchange routes are intentionally omitted.
API keys and workflow vault secrets can grant powerful access. Treat them like production credentials, rotate them when ownership changes, and remove unused keys.