---
title: "Update a number order"
method: PATCH
path: "/number_orders/{number_order_id}"
tags: ["Phone Number Orders"]
---

# Update a number order

`PATCH /number_orders/{number_order_id}`

Updates a phone number order.

## Path parameters

- `number_order_id` string, required

## Request body

- UpdateNumberOrderRequest
  - `regulatory_requirements` UpdateRegulatoryRequirement[]
    - `requirement_id` string, uuid — Unique id for a requirement.
    - `field_value` string — The value of the requirement. For address and document requirements, this should be the ID of the resource. For textual, this should be the value of the requirement.
  - `customer_reference` string — A customer reference string for customer look ups.

## Response `200`

Successful response with details about a number order.

- object
  - `data` NumberOrderWithPhoneNumbers
    - `id` string, uuid
    - `record_type` string
    - `phone_numbers_count` integer — The count of phone numbers in the number order.
    - `connection_id` string — Identifies the connection associated with this phone number.
    - `messaging_profile_id` string — Identifies the messaging profile associated with the phone number.
    - `billing_group_id` string — Identifies the messaging profile associated with the phone number.
    - `phone_numbers` PhoneNumber[]
      - `id` string, uuid
      - `record_type` string
      - `phone_number` string
      - `country_iso_alpha2` string — The ISO 3166-1 alpha-2 country code of the phone number.
      - `regulatory_requirements` SubNumberOrderRegulatoryRequirementWithValue[]
        - `record_type` string
        - `requirement_id` string, uuid — Unique id for a requirement.
        - `field_type` 'textual' | 'datetime' | 'address' | 'document'
        - `field_value` string — The value of the requirement, this could be an id to a resource or a string value.
      - `requirements_met` boolean — True if all requirements are met for a phone number, false otherwise.
      - `requirements_status` 'pending' | 'approved' | 'cancelled' | 'deleted' | 'requirement-info-exception' | 'requirement-info-pending' | 'requirement-info-under-review' — Status of document requirements (if applicable)
      - `status` 'pending' | 'success' | 'failure' — The status of the phone number in the order.
      - `bundle_id` string, uuid
      - `phone_number_type` 'local' | 'mobile' | 'national' | 'shared_cost' | 'toll_free' — Phone number type
      - `country_code` string — Country code of the phone number
    - `sub_number_orders_ids` string[]
    - `status` 'pending' | 'success' | 'failure' — The status of the order.
    - `customer_reference` string — A customer reference string for customer look ups.
    - `created_at` string, date-time — An ISO 8901 datetime string denoting when the number order was created.
    - `updated_at` string, date-time — An ISO 8901 datetime string for when the number order was updated.
    - `requirements_met` boolean — True if all requirements are met for every phone number, false otherwise.

## Other responses

- `400` — Bad request, the request was unacceptable, often due to missing a required parameter.
- `401` — Unauthorized
- `404` — The requested resource doesn't exist.
- `422` — Unprocessable entity. Check the 'detail' field in response for details.
- `500` — Unexpected error

---

[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/versions/8f5f4e537994/schema)