---
title: "Create a Private Wireless Gateway"
method: POST
path: "/private_wireless_gateways"
tags: ["Private Wireless Gateways"]
---

# Create a Private Wireless Gateway

`POST /private_wireless_gateways`

Asynchronously create a Private Wireless Gateway for SIM cards for a previously created network. This operation may take several minutes so you can check the Private Wireless Gateway status at the section Get a Private Wireless Gateway.

## Request body

- object
  - `network_id` string, uuid, required — The identification of the related network resource.
  - `name` string, required — The private wireless gateway name.
  - `region_code` string — The code of the region where the private wireless gateway will be assigned. A list of available regions can be found at the regions endpoint
  - `address_mode` 'static' | 'dynamic' — Determines how IP addresses are assigned to SIM cards using this gateway. With static, each SIM card gets a fixed IP address from the gateway's IP range that is preserved across sessions. With dynamic, an IP address is assigned by the network at attach time and may change between sessions. If omitted, the gateway is created with the default address mode, dynamic.

## Response `202`

Creation request accepted. Provisioning is asynchronous; poll GET /private_wireless_gateways/{id} with the returned id to check status.

- object
  - `data` WirelessPrivateWirelessGateway
    - `id` string, uuid — Identifies the resource.
    - `network_id` string, uuid — The identification of the related network resource.
    - `record_type` string
    - `created_at` string — ISO 8601 formatted date-time indicating when the resource was created.
    - `updated_at` string — ISO 8601 formatted date-time indicating when the resource was updated.
    - `name` string — The private wireless gateway name.
    - `address_mode` 'static' | 'dynamic' — The address mode of the private wireless gateway. With static, each SIM card gets a fixed IP address from the gateway's IP range that is preserved across sessions. With dynamic, IP addresses are assigned by the network at attach time and may change between sessions.
    - `region_code` string — The name of the region where the Private Wireless Gateway is deployed.
    - `status` PrivateWirelessGatewayStatus — The current status or failure details of the Private Wireless Gateway.
      - `value` 'provisioning' | 'provisioned' | 'failed' | 'decommissioning' — The current status or failure details of the Private Wireless Gateway. <ul> <li><code>provisioning</code> - the Private Wireless Gateway is being provisioned.</li> <li><code>provisioned</code> - the Private Wireless Gateway was provisioned and able to receive connections.</li> <li><code>failed</code> - the provisioning had failed for a reason and it requires an intervention.</li> <li><code>decommissioning</code> - the Private Wireless Gateway is being removed from the network.</li> </ul> Transitioning between the provisioning and provisioned states may take some time.
      - `error_description` string, nullable — This attribute provides a human-readable explanation of why a failure happened.
      - `error_code` string, nullable — This attribute is an [error code](https://developers.telnyx.com/docs/development/api-fundamentals/api-errors) related to the failure reason.
    - `ip_range` string — IP block used to assign IPs to the SIM cards in the Private Wireless Gateway.
    - `assigned_resources` PWGAssignedResourcesSummary[] — A list of the resources that have been assigned to the Private Wireless Gateway.
      - `record_type` string — The type of the resource assigned to the Private Wireless Gateway.
      - `count` integer — The current count of a resource type assigned to the Private Wireless Gateway.

## Other responses

- `422` — Unprocessable entity. Check the 'detail' field in response for details.
- `default` — Unexpected error

## Changes

> 99 revisions in range; 1 not diffed.

- **2026-09-23** `f6e9ed754d05` — 2 info
  - added the new optional request property `address_mode`
  - added the optional property `data/address_mode` to the response with the `202` status
- **2026-09-16** `a6a61a29ecdd` — 2 breaking
  - the `errors/items/code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `422`
  - the `errors/items/code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `default`
- **2026-08-17** `1571b0380bd7` — 2 breaking
  - the `errors/items/code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `422`
  - the `errors/items/code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `default`
- **2026-08-04** `8f5f4e537994` — 2 breaking
  - the `errors/items/code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `422`
  - the `errors/items/code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `default`

[Change history](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/changes/private_wireless_gateways/post.md)

---

[API](https://skmtc.dev/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/revisions/227c33b1ac9c?raw)