openapi: 3.0.3 info: title: Exotel Call Details Numbers API description: 'Exotel is an Indian cloud telephony and customer-engagement (CPaaS) platform. This OpenAPI describes a representative, grounded subset of Exotel''s documented public REST API: placing outbound voice calls (connect two numbers, or connect a number to a call flow / applet), sending SMS, retrieving call details, looking up phone-number metadata, and managing call campaigns. Base URL is region-specific and Twilio-style: `https:///v1/Accounts//...` for the v1 telephony APIs and `https:///v2/accounts//...` for the v2 Campaigns API. All requests use HTTP Basic authentication with your API Key as the username and API Token as the password (credentials may also be embedded in the URL as `https://:@/...`). GROUNDING NOTE: Endpoint paths and HTTP methods for Calls/connect, Calls/{CallSid}, Numbers/{Number}, Sms/send, and the v2 Campaigns resource are confirmed from Exotel''s developer docs. Request/response SCHEMAS below are MODELED from the documented parameter lists and Exotel''s Twilio-style conventions - Exotel does not publish a machine OpenAPI, so field-level schemas should be verified against the live docs before production use. Exotel APIs return XML by default; append `.json` to a resource path to receive JSON (shown here as the JSON variants).' version: '1.0' contact: name: Exotel Developer Support url: https://developer.exotel.com x-grounding: confirmedEndpoints: - POST /v1/Accounts/{sid}/Calls/connect - GET /v1/Accounts/{sid}/Calls/{CallSid} - GET /v1/Accounts/{sid}/Numbers/{Number} - POST /v1/Accounts/{sid}/Sms/send - POST /v2/accounts/{sid}/campaigns - GET /v2/accounts/{sid}/campaigns/{campaign_id} - GET /v2/accounts/{sid}/campaigns/{campaign_id}/call-details modeledEndpoints: - GET /v1/Accounts/{sid}/Calls (bulk list; documented as existing, path follows Exotel convention) - GET /v1/Accounts/{sid}/Sms/Messages/{SmsSid} (SMS details; documented as existing, path follows Exotel convention) schemaStatus: All request/response body and form-field schemas are modeled from documented parameter lists, not from a vendor-published OpenAPI. servers: - url: https://api.exotel.com description: Singapore cluster (default) - url: https://api.in.exotel.com description: Mumbai / India cluster security: - basicAuth: [] tags: - name: Numbers description: Look up telecom metadata for phone numbers. paths: /v1/Accounts/{sid}/Numbers/{Number}.json: parameters: - $ref: '#/components/parameters/AccountSid' - name: Number in: path required: true description: The phone number (E.164) to look up. schema: type: string get: operationId: getNumberMetadata tags: - Numbers summary: Get phone-number metadata description: Returns telecom metadata (operator/circle, number type, DND status where available) for an Indian phone number. Confirmed endpoint; response schema modeled. responses: '200': description: Number metadata. content: application/json: schema: $ref: '#/components/schemas/NumberMetadata' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' components: responses: Unauthorized: description: Missing or invalid API Key/Token. NotFound: description: Resource not found. parameters: AccountSid: name: sid in: path required: true description: Your Exotel account Sid (Account SID). schema: type: string schemas: NumberMetadata: type: object description: Modeled from documented number-lookup fields. properties: PhoneNumber: type: string Circle: type: string description: Telecom circle (region). CircleName: type: string Type: type: string description: Number type (e.g. mobile, landline). Operator: type: string OperatorName: type: string DND: type: string description: Do-Not-Disturb registration status where available. securitySchemes: basicAuth: type: http scheme: basic description: HTTP Basic authentication. Username = API Key, Password = API Token (both from Exotel Dashboard -> Settings -> API Settings). May also be embedded in the URL as https://:@/...