Contact Autodisc
Choose the path that matches what you need. These routes keep operational context attached to the right workspace while keeping credentials and private infrastructure details out of messages.
Account, deployment, and billing support
Sign in before opening a support request so the team can identify the correct workspace without asking you to place account credentials in a message. Include the affected project or deployment ID, the approximate time of the issue, and the action you expected to complete. Never send passwords, API keys, environment values, or Drop control tokens.
Open Autodisc supportDeveloper and API questions
Check the developer index, public OpenAPI document, authentication guidance, webhook contract, and API lifecycle policy first. When reporting an integration problem, include the endpoint, HTTP method, response status, and request ID when one is available. Redact authorization and cookie headers before sharing a request example.
Browse developer resourcesAvailability and incidents
Review the status page before reporting a service interruption. A useful incident report names the affected public URL or Autodisc project, the region if known, the first observed time, and whether the failure affects deploys, control-plane actions, or application traffic. Do not include private source code or production secrets.
Check service status