MobDial API quickstart

The external developer platform is currently preview/partial. Before integrating, confirm the authentication method, scopes, endpoint availability, and account capabilities exposed by your current MobDial environment. Do not assume package-registry SDKs or production API-key issuance until they are explicitly published and verified.

1. Review the current contract

Start with the API reference and the OpenAPI surface available to your environment. Internal/admin routes and product-internal contracts are not automatically part of the public developer API.

2. Obtain an approved credential

Use the authentication flow currently enabled for your organization. Store credentials as managed secrets, keep tenant and scope boundaries explicit, and never embed secrets in browser code or documentation examples.

MOBDIAL_ACCESS_TOKEN=<approved_environment_token>

3. Validate a repository-backed route

The calls service is mounted under /api/v1/calls in the current application contract. The example below shows the request shape only; required fields and permissions must follow the current OpenAPI/runtime contract.

curl -X POST https://api.mobdial.com/api/v1/calls \
  -H "Authorization: Bearer $MOBDIAL_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"to":"+14155550100","from":"+18005550100"}'

Next steps

• Handle validation, permission, rate-limit, and upstream failures explicitly.
• Use supported webhook/event contracts only after verifying the current delivery and signing behavior.
• Treat SDK generation artifacts as development tooling until package publication and compatibility evidence are complete.