---
title: "List call control applications"
method: GET
path: "/call_control_applications"
tags: ["Call Control Applications"]
---

# List call control applications

`GET /call_control_applications`

Return a list of call control applications.

## Query parameters

- `filter` object
  - `application_name` object — Application name filters
    - `contains` string — If present, applications with <code>application_name</code> containing the given value will be returned. Matching is not case-sensitive. Requires at least three characters.
  - `outbound.outbound_voice_profile_id` string — Identifies the associated outbound voice profile.
  - `leg_id` string, uuid — The unique identifier of an individual call leg.
  - `application_session_id` string, uuid — The unique identifier of the call session. A session may include multiple call leg events.
  - `connection_id` string — The unique identifier of the conection.
  - `product` 'call_control' | 'fax' | 'texml' — Filter by product.
  - `failed` boolean — Delivery failed or not.
  - `from` string — Filter by From number.
  - `to` string — Filter by To number.
  - `name` string — If present, conferences will be filtered to those with a matching `name` attribute. Matching is case-sensitive
  - `type` 'command' | 'webhook' — Event type
  - `occurred_at` object — Event occurred_at filters
    - `eq` string — Event occurred_at: equal
    - `gt` string — Event occurred_at: greater than
    - `gte` string — Event occurred_at: greater than or equal
    - `lt` string — Event occurred_at: lower than
    - `lte` string — Event occurred_at: lower than or equal
  - `status` 'init' | 'in_progress' | 'completed' — If present, conferences will be filtered by status.
- `page` object
  - `after` string — Opaque identifier of next page
  - `before` string — Opaque identifier of previous page
  - `limit` integer — Limit of records per single page
  - `size` integer — The size of the page
  - `number` integer — The page number to load
- `sort` 'created_at' | 'connection_name' | 'active'

## Response `200`

Successful response with a list of call control applications.

- object
  - `data` CallControlApplication[]
    - `active` boolean — Specifies whether the connection can be used.
    - `anchorsite_override` 'Latency' | 'Chicago, IL' | 'Ashburn, VA' | 'San Jose, CA' | 'London, UK' | 'Chennai, IN' | 'Amsterdam, Netherlands' | 'Toronto, Canada' | 'Sydney, Australia' — <code>Latency</code> directs Telnyx to route media through the site with the lowest round-trip time to the user's connection. Telnyx calculates this time using ICMP ping messages. This can be disabled by specifying a site to handle all media.
    - `application_name` string — A user-assigned name to help manage the application.
    - `created_at` string — ISO 8601 formatted date of when the resource was created
    - `dtmf_type` 'RFC 2833' | 'Inband' | 'SIP INFO' — Sets the type of DTMF digits sent from Telnyx to this Connection. Note that DTMF digits sent to Telnyx will be accepted in all formats.
    - `first_command_timeout` boolean — Specifies whether calls to phone numbers associated with this connection should hangup after timing out.
    - `first_command_timeout_secs` integer — Specifies how many seconds to wait before timing out a dial command.
    - `tags` string[] — Tags assigned to the Call Control Application.
    - `id` string
    - `inbound` CallControlApplicationInbound
      - `channel_limit` integer — When set, this will limit the total number of inbound calls to phone numbers associated with this connection.
      - `shaken_stir_enabled` boolean — When enabled Telnyx will include Shaken/Stir data in the Webhook for new inbound calls.
      - `sip_subdomain` string — Specifies a subdomain that can be used to receive Inbound calls to a Connection, in the same way a phone number is used, from a SIP endpoint. Example: the subdomain "example.sip.telnyx.com" can be called from any SIP endpoint by using the SIP URI "sip:@example.sip.telnyx.com" where the user part can be any alphanumeric value. Please note TLS encrypted calls are not allowed for subdomain calls.
      - `sip_subdomain_receive_settings` 'only_my_connections' | 'from_anyone' — This option can be enabled to receive calls from: "Anyone" (any SIP endpoint in the public Internet) or "Only my connections" (any connection assigned to the same Telnyx user).
    - `outbound` CallControlApplicationOutbound
      - `channel_limit` integer — When set, this will limit the total number of outbound calls to phone numbers associated with this connection.
      - `outbound_voice_profile_id` string — Identifies the associated outbound voice profile.
    - `record_type` 'call_control_application'
    - `updated_at` string — ISO 8601 formatted date of when the resource was last updated
    - `webhook_api_version` '1' | '2' — Determines which webhook format will be used, Telnyx API v1 or v2.
    - `webhook_event_failover_url` string, url, nullable — The failover URL where webhooks related to this connection will be sent if sending to the primary URL fails. Must include a scheme, such as `https`.
    - `webhook_event_url` string, url — The URL where webhooks related to this connection will be sent. Must include a scheme, such as `https`.
    - `webhook_timeout_secs` integer, nullable
    - `call_cost_in_webhooks` boolean — Specifies if call cost webhooks should be sent for this Call Control Application.
    - `redact_dtmf_debug_logging` boolean — When enabled, DTMF digits entered by users will be redacted in debug logs to protect PII data entered through IVR interactions.
  - `meta` PaginationMeta
    - `total_pages` integer
    - `total_results` integer
    - `page_number` integer
    - `page_size` integer

## Other responses

- `400` — Bad request
- `401` — Unauthorized. Authentication failed - the required authentication headers were either invalid or not included in the request.
- `404` — Resource not found

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/8f5f4e537994/schema)