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.
Authorization
bearerAuth 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
{ "country": "string", "requirements": [ { "requirementId": "string", "label": "string", "kind": "text", "description": "string", "example": "string", "acceptableValues": [ "string" ], "status": "string", "filled": true } ]}List port-in orders
Your porting orders, newest first (max 50). Poll this for port progress: pending, confirmed FOC date, exception reason, or ported.
Upload a porting document
Upload ONE porting document and get back its `documentId`. For the signed LOA / carrier invoice the id goes to `loaDocumentId` / `invoiceDocumentId`; for a country-specific document requirement (international ports) it becomes that requirement's `fieldValue`. Requirement documents are normalized to PDF automatically (regulators reject raw images). PDF, JPEG, or PNG, 10MB max. Uploads must be attached to an order within 30 minutes or the carrier deletes them.