> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# List Enabled Telephony Network Groups

> List the DialNexa destination countries and prefixes enabled for outbound calling in the authenticated workspace.

<span data-api-safety-label="read-only"><Badge color="gray" size="sm" shape="pill">Read only</Badge></span>

List enabled telephony network groups to see which destination countries and prefixes the authenticated workspace can call. DialNexa combines active network-group configurations by country and returns one rule per country.

## When to list enabled network groups

* Validate destination availability before creating a call or batch.
* Explain why a valid E.164 number is blocked by workspace telephony policy.
* Build a country and prefix selector that reflects the current workspace configuration.

## Understand the response

| Field                            | Meaning                                                                             |
| -------------------------------- | ----------------------------------------------------------------------------------- |
| `prefix_mode`                    | `allow_only_listed` for the returned combined rules.                                |
| `from_phone_number_country_code` | Reserved source-country constraint. The combined response currently returns `null`. |
| `countryRule.country_iso`        | Two-letter destination country code.                                                |
| `countryRule.calling_code`       | Destination calling code without the leading `+`.                                   |
| `countryRule.prefixes`           | Unique prefixes enabled across active network groups for the country.               |

## Verify the result

Confirm the destination country is present and that its local number begins with an allowed prefix. An empty array means the workspace has no active network-group configuration for standard outbound routing.

## Errors and recovery

* `401 Unauthorized` means the API key is missing or invalid.
* `400 Bad Request` means the workspace context could not be resolved. Confirm the API key belongs to an active workspace.
* Do not retry a blocked call until the workspace telephony configuration changes or the destination is corrected.

## Related endpoints

* [List Phone Country Rules](/docs/api-reference/v1/phone-numbers/list-country-rules): read the global country catalog.
* [Create Call](/docs/api-reference/v1/calls/create): start a call after validating destination policy.
* [Workspace settings](/docs/platform/workspaces): locate Telephony Config in the dashboard.


## OpenAPI

````yaml GET /v1/phone-country-rules/enabled-network-groups
openapi: 3.0.0
info:
  title: DialNexa API
  description: Public `/v1` REST API for the DialNexa voice AI platform.
  version: 1.0.0
servers:
  - url: https://api.dialnexa.com
    description: DialNexa production API
security:
  - bearer: []
tags:
  - name: Agents
  - name: Batch Calls
  - name: Calls
  - name: Knowledge Base
  - name: Languages
  - name: LLMs
  - name: Phone Numbers
  - name: Transcribers
  - name: Webhooks
  - name: Voices
  - name: Workflows
  - name: Workflow Leads
paths:
  /v1/phone-country-rules/enabled-network-groups:
    get:
      tags:
        - Phone Numbers
      summary: List Enabled Telephony Network Groups
      description: >-
        Returns one combined destination rule per country enabled for the
        authenticated workspace.
      operationId: listEnabledTelephonyNetworkGroups
      responses:
        '200':
          description: Enabled destination rules returned successfully.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/EnabledTelephonyNetworkGroup'
        '400':
          description: Workspace context could not be resolved.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized - missing or invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearer: []
components:
  schemas:
    EnabledTelephonyNetworkGroup:
      type: object
      properties:
        prefix_mode:
          type: string
          enum:
            - allow_only_listed
        from_phone_number_country_code:
          type: string
          nullable: true
          example: null
        countryRule:
          type: object
          properties:
            country_iso:
              type: string
              example: IN
            country_name:
              type: string
              example: India Mobile
            calling_code:
              type: string
              example: '91'
            prefixes:
              type: array
              items:
                type: string
              example:
                - '98'
                - '99'
          required:
            - country_iso
            - country_name
            - calling_code
            - prefixes
      required:
        - prefix_mode
        - from_phone_number_country_code
        - countryRule
    ErrorResponse:
      type: object
      properties:
        statusCode:
          type: integer
          example: 400
        message:
          oneOf:
            - type: string
            - type: array
              items:
                type: string
          example: phone_number must be a valid E.164 phone number
        error:
          type: string
          example: Bad Request
      required:
        - statusCode
        - message
        - error
  securitySchemes:
    bearer:
      scheme: bearer
      type: http

````