openapi: 3.0.1 info: title: CloudTalk Agents Other API description: "# Introduction\nWelcome to CloudTalk API reference! Many of these businesses use the CloudTalk API to automate and enhance their customer support with CloudTalk Support. With CloudTalk we are re-building telco industry from the ground and taking it to the next level with first-class customer support system. Please find below the full documenation to CloudTalk.\n\n# API Overview\n\nThe API is organized around the following resources:\n\nAPI Area | Description\n----------------|-------------\nCalls | Browse your call history, download recordings and access all your calls data.\nContacts | Create and update Contacts. Use filters to get lists of Contacts, or access their profiles individually.\nNumbers | Automate Numbers modifications. List all your numbers.\nAgents | Create or update your Agents, access their settings.\nConversation Intelligence | Get Conversation Intelligence data about your calls.\nVoiceAgent | Initiate VoiceAgent calls\n\n\n[JSON](http://www.json.org/) is returned in all responses. XML is not supported.\n\nThe API also uses common approaches for the following:\n\nFunction | Description\n----------------|-------------\nData | API data is JSON encoded with UTF-8. API JSON is either a single object or a list of objects.\nErrors | 4xx and 5xx responses returning JSON with error codes\nRate Limiting | Controls how many requests can be made in a time window\nHTTP | Methods are used in accordance with HTTP (GET POST and DELETE are the primary methods used) and resources are identified using URIs. All API requests are sent over HTTPS.\n\n\n## Authentication\n\nThis is an HTTPS-only API. Authentication is based on API Access Key ID and Access Key Secret. The API Access Key ID and Access Key Secret is passed via HTTP Basic Authentication.\n\n Basic Auth credentials are used to determine on which project should this request be executed on. List of all Basic Auth credentials for the project can be found by Administrators in the Cloudtalk Dashboard Account → Settings → API keys tab.\n\nTo try the API via curl on the command-line, the general form used would be:\n```\ncurl -u ACCESS_KEY_ID:ACCESS_KEY_SECRET API_URL\n```\n\nFor instance, you would execute:\n```\ncurl -u ABCDEFGHIJTESTKEY1:X05Dg4c331c3h61An https://my.cloudtalk.io/api/calls/index.json\n```\n\n## Usage\n\nThe API may rate limit submission of requests for your application. Such limits are managed as an allowed number of operations per time window, where an operation might be read or an update. In that case a **'429 Too Many Requests'** response code will be returned along with the following headers -\n\nHeader name | Description\n----------------|-------------\nX-CloudTalkAPI-Limit | Maximum number of API requests allowed in the current time window.\nX-CloudTalkAPI-Remaining | Number of API requests left in the current window.\nX-CloudTalkAPI-ResetTime | Time when rate limit window will be reset as a Unix timestamp.\n\nNote that the default rate limit is **60 operations per minute per company**. If you need to make more requests, please contact our support with detailed explanation of your use case.\n\n## Response Envelopes\n\n**Note:** Conversation Intelligence doesn't follow envelopes.\n\nThe API returns one of three envelopes depending upon the request issued:\n\n1. Single Item Envelope\n2. Collections Envelope\n3. Error Envelope\n\n### Single Item Envelope\n\nAll dates/times are returned in ISO8601 format and in UTC timezone.\n\n```\nStatus: 200 OK\n{\n \"responseData\": {\n \"id\": 123,\n ...\n \"created\": \"2018-01-10 12:34:56\"\n }\n}\n```\n\n### Collections Envelope\n\nAll dates/times are returned in ISO8601 format and in UTC timezone.\n\n```\nStatus: 200 OK\n{\n \"responseData\": {\n \"itemsCount\": 65,\n \"pageCount\": 3,\n \"pageNumber\": 1,\n \"limit\": 30,\n \"data\": [\n {\n \"id\": 123,\n ...\n \"created\": \"2018-01-10 12:34:56\"\n },\n {\n \"id\": 456,\n ...\n \"created\": \"2017-10-19 09:21:29\"\n },\n ...\n ]\n }\n}\n```\n\n### Error Envelope\n\n```\nStatus: 404 Not Found\n{\n \"responseData\": {\n \"status\": 404,\n \"message\": \"Not Found\"\n }\n}\n```\n\n## Encoding\n\nData is encoded as defined by JSON in [RFC4627](http://www.ietf.org/rfc/rfc4627.txt). The default encoding for APIs is UTF-8.\n\nSome query parameters may need to be [url encoded](https://www.wikiwand.com/en/Percent-encoding) when sending - for example, the email parameter value used to query users should be encoded.\n\n## Use of HTTP\n\nRequest methods are used in accordance with HTTP -\n\n- `GET` is used to access resources and perform queries. The API does not allow modifications (creates, updates, deletes) to occur via GET.\n- `PUT` is used to create resources.\n- `POST` is used to update resources. PATCH is not currently used by the API.\n- `DELETE` is used to delete resources.\n\nResponses use standard HTTP codes. Where there are client or server errors, a list of of one or more errors in JSON format is returned in the body.\n\nThe `Accept` header must be used by a client used to indicate a preferred response for `GET/HEAD` requests. Requests without an `Accept` header of `application/json` may be rejected with a client error of 404 or 406. The `Content-Type` header should be used by clients to indicate the submitted format for `POST/PUT` requests." contact: name: CloudTalk API Support url: https://www.cloudtalk.io/contact version: '1.7' x-logo: url: https://my.cloudtalk.io/img/logo-cloudtalk-color.png servers: - url: https://my.cloudtalk.io/api tags: - name: Other description: All other helper endpoints. paths: /countries/index.json: get: tags: - Other summary: List countries responses: '200': description: All countries content: application/json: schema: type: object properties: responseData: type: array items: type: object properties: Country: $ref: '#/components/schemas/Country' example: responseData: - Country: id: '61' name: Denmark country_code: DK iso3: DNK calling_code: '45' - Country: id: '235' name: United Kingdom country_code: GB iso3: GBR calling_code: '44' /blacklist/index.json: get: tags: - Other summary: List blacklist description: List blacklisted numbers. parameters: - name: id in: query description: Filter by ID schema: type: integer - name: country_code in: query description: Filter by country calling code schema: type: integer - name: type in: query description: Filter by type schema: type: string enum: - all - incoming - outgoing - name: public_number in: query description: Filter by number schema: type: string - name: limit in: query description: Max. number of items in response data. schema: maximum: 1000 minimum: 1 type: integer - name: page in: query description: Number of page to return. schema: minimum: 1 type: integer responses: '200': description: Blacklist data content: application/json: schema: type: object properties: itemsCount: $ref: '#/components/schemas/PaginationData/properties/itemsCount' pageCount: $ref: '#/components/schemas/PaginationData/properties/pageCount' pageNumber: $ref: '#/components/schemas/PaginationData/properties/pageNumber' limit: $ref: '#/components/schemas/PaginationData/properties/limit' data: type: array items: type: object properties: Blacklist: $ref: '#/components/schemas/Blacklist' example: responseData: itemsCount: 2 pageCount: 1 pageNumber: 1 limit: 2 data: - Blacklist: id: '123' type: all public_number: 442012345678 - Blacklist: id: '456' type: incoming public_number: 442012345679 /blacklist/add.json: put: tags: - Other summary: Add number to blacklist description: Add number to blacklist. requestBody: content: application/json: schema: required: - public_number - type type: object properties: type: $ref: '#/components/schemas/Blacklist/properties/type' public_number: $ref: '#/components/schemas/Blacklist/properties/public_number' required: true responses: '201': description: No error content: application/json: schema: type: object properties: status: $ref: '#/components/schemas/StatusCode/properties/status' data: type: object properties: id: $ref: '#/components/schemas/Blacklist/properties/id' example: responseData: status: 201 data: id: '12345' '406': description: Invalid input content: application/json: schema: $ref: '#/components/schemas/ErrorInvalidData' example: responseData: status: 406 message: Invalid input data. data: public_number: - Please supply only valid numbers. Number +441234 is not valid. '500': description: Something went wrong content: application/json: schema: $ref: '#/components/schemas/ErrorData' example: responseData: status: 500 message: Something went wrong. x-codegen-request-body-name: body /blacklist/edit/{id}.json: post: tags: - Other summary: Edit number on blacklist description: Edit blacklisted number. parameters: - name: id in: path description: ID to edit required: true schema: type: integer requestBody: content: application/json: schema: required: - public_number - type type: object properties: type: $ref: '#/components/schemas/Blacklist/properties/type' public_number: $ref: '#/components/schemas/Blacklist/properties/public_number' required: true responses: '200': description: No error content: application/json: schema: type: object properties: status: $ref: '#/components/schemas/StatusCode/properties/status' example: responseData: status: 200 '404': description: Not found content: application/json: schema: $ref: '#/components/schemas/ErrorData' example: responseData: status: 404 message: Not found. '406': description: Invalid input content: application/json: schema: $ref: '#/components/schemas/ErrorInvalidData' example: responseData: status: 406 message: Invalid input data. data: public_number: - Please supply only valid numbers. Number +441234 is not valid. '500': description: Something went wrong content: application/json: schema: $ref: '#/components/schemas/ErrorData' example: responseData: status: 500 message: Something went wrong. x-codegen-request-body-name: body /blacklist/delete/{id}.json: delete: tags: - Other summary: Delete number from blacklist description: Delete the number from blacklist. parameters: - name: id in: path description: ID to delete required: true schema: type: integer responses: '200': description: No error content: application/json: schema: $ref: '#/components/schemas/SuccessGeneralData' example: responseData: status: 200 '404': description: Blacklist not found content: application/json: schema: $ref: '#/components/schemas/ErrorData' example: responseData: status: 404 message: Not found. '500': description: Something went wrong content: application/json: schema: $ref: '#/components/schemas/ErrorData' example: responseData: status: 500 message: Something went wrong. components: schemas: PaginationData: properties: pageNumber: type: integer description: current page in the response format: int64 limit: type: integer description: number of objects sent per page format: int64 itemsCount: type: integer description: number of resources in the response format: int64 pageCount: type: integer description: number of pages found format: int64 ErrorInvalidData: type: object properties: status: type: string description: Status code message: type: string description: The error message data: type: object properties: {} description: More data explaining the error StatusCode: properties: status: type: string description: Status code Blacklist: type: object properties: id: type: integer description: Blacklist ID type: type: string description: Type of calls enum: - all - incoming - outgoing public_number: type: string description: Blacklisted number in E.164 format created: type: string description: Created date and time format: date-time modified: type: string description: Last modified date and time format: date-time description: Blacklist data Country: type: object properties: id: type: integer description: Country ID name: type: string description: Name country_code: type: string description: Country code by ISO_3166-1 Alpha-2 iso3: type: string description: Country code by ISO_3166-1 Alpha-3 calling_code: type: string description: Country calling code description: Country data ErrorData: type: object properties: status: type: string description: Status code message: type: string description: The error message SuccessGeneralData: type: object properties: status: type: string description: Status code