---
title: "A port-in order's pending requirements"
method: GET
path: "/v1/phone-numbers/port-in/{id}/requirements"
tags: ["Phone Numbers"]
---

# A port-in order's pending requirements

`GET /v1/phone-numbers/port-in/{id}/requirements`

The live requirements on an EXISTING porting order: which are filled,
which are still pending, and which bounced on review
(`requirement-info-exception`). Use it to fix and resubmit a rejected
international port. Same field shape as the country-level requirements
endpoint, plus per-requirement status.

## Path parameters

- `id` string, required

## Response `200`

The order's requirements with statuses.

- object
  - `country` string
  - `requirements` object[]
    - `requirementId` string
    - `label` string
    - `kind` 'text' | 'date' | 'address' | 'file' | 'action'
    - `description` string
    - `example` string
    - `acceptableValues` string[]
    - `status` string — requirement-info-pending | requirement-info-under-review | requirement-info-exception | approved
    - `filled` boolean

## Other responses

- `400` — Invalid request
- `401` — Unauthorized
- `404` — Porting order not found

## Changes

- **2026-09-16** `3e6ddf2a99ea` — 1 info
  - added the optional property `details/budgetScope` to the response with the `400` status
- **2026-09-15** `0dba7d004d75` — 2 info
  - added the optional property `details/quotaExhausted` to the response with the `400` status
  - added the optional property `details/quotaScope` to the response with the `400` status

[Change history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/phone-numbers/port-in/:id/requirements/get.md)

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) · [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/eded32b62823?raw)