A port-in order's pending 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.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Porting order ID (from the port-in list).
Response Body
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.phonenumbers.getPhoneNumberPortInOrderRequirements({ path: { id: 'abc123', },});console.log(data);{
"country": "string",
"requirements": [
{
"requirementId": "string",
"label": "string",
"kind": "text",
"description": "string",
"example": "string",
"acceptableValues": [
"string"
],
"status": "string",
"filled": true
}
]
}{
"error": "string",
"type": "invalid_request_error",
"code": "string",
"param": "string",
"platform": "string",
"platformError": {},
"details": {}
}{
"error": "Unauthorized"
}Get KYC form spec GET
For a Tier 3/4 country, the fields the end customer must provide (Telnyx regulatory requirements) before a number can be ordered: text, date, address, or file (document) per requirement.
Country porting requirements GET
The country-specific information a port-in needs BEYOND the LOA, invoice, and account/address details — e.g. an ID copy, proof of address, a tax id, or a porting code. Call it after the portability check (which returns each number's `countryCode` and `phoneNumberType`), render the fields, and pass the collected values as the create request's `requirements`. US/CA return an empty list.