---
title: "Schedule a future requirement version"
method: POST
path: "/requirements/{id}/versions"
tags: ["Requirements"]
---

# Schedule a future requirement version

`POST /requirements/{id}/versions`

Create a new pending version of a requirement with a future effective start date. Only one pending version may exist per requirement at a time.

## Path parameters

- `id` string, uuid, required

## Request body

- CreateRequirementVersionRequest
  - `effective_start_at` string, date-time, required — ISO 8601 formatted date-time indicating when the new version should become active. Must be a future date-time.
  - `requirement_type_ids` string[], required — List of requirement type UUIDs that apply to the new version. Replaces the existing requirement types for the new version.

## Response `201`

Pending version created successfully

- object
  - `data` DocReqsRequirement
    - `action` 'both' | 'branded_calling' | 'ordering' | 'porting' — Indicates whether this requirement applies to branded_calling, ordering, porting, or both ordering and porting
    - `country_code` string — The 2-character (ISO 3166-1 alpha-2) country code where this requirement applies
    - `created_at` string — ISO 8601 formatted date-time indicating when the resource was created.
    - `effective_end_at` string, date-time, nullable — When this version was superseded. NULL means this is the active or pending version.
    - `effective_start_at` string, date-time, nullable — When this version became (or will become) active.
    - `id` string, uuid — Identifies the associated document
    - `locality` string — The locality where this requirement applies
    - `phone_number_type` 'local' | 'national' | 'toll_free' — Indicates the phone_number_type this requirement applies to. Leave blank if this requirement applies to all number_types.
    - `record_type` string — Identifies the type of the resource.
    - `requirement_types` DocReqsRequirementType[] — Lists the requirement types necessary to fulfill this requirement
      - `acceptance_criteria` object — Specifies objective criteria for acceptance
        - `acceptable_characters` string — Specifies the allowed characters as a string
        - `acceptable_values` string[] — Specifies the list of strictly possible values for the requirement. Ignored when empty
        - `locality_limit` string — Specifies geography-based acceptance criteria
        - `max_length` integer — Maximum length allowed for the value
        - `min_length` integer — Minimum length allowed for the value
        - `time_limit` string — Specifies time-based acceptance criteria
      - `created_at` string — ISO 8601 formatted date-time indicating when the resource was created.
      - `description` string — Describes the requirement type
      - `example` string — Provides one or more examples of acceptable documents
      - `id` string, uuid — Identifies the associated document
      - `name` string — A short descriptive name for this requirement_type
      - `record_type` string — Identifies the type of the resource
      - `type` 'document' | 'address' | 'textual' — Defines the type of this requirement type
      - `updated_at` string — ISO 8601 formatted date-time indicating when the resource was last updated.
    - `updated_at` string — ISO 8601 formatted date-time indicating when the resource was last updated.
    - `version` integer — Version number. Increments with each new version. Defaults to 1.

## Other responses

- `404` — Resource not found
- `422` — Unprocessable entity. Check the 'detail' field in response for details.
- `default` — 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/revisions/3fdc16374d70/schema)