Respond to the regulatory reviewer (message + corrections)
Send a single response to the reviewer on a number awaiting remediation:
a free-text message and/or corrected requirement documents, in one call.
If corrections are present they are PATCHed onto the requirement group and
re-submitted (the number goes back to "in review"); if a message or file
attachments are present they are posted to the reviewer's comment thread.
When both are present, your message is the thread comment and the resubmit
drives the state change. At least one of message, corrections, or
attachments is required. documents correct requirement slots; attachments
are loose files (their links are added to your message).
Authorization
bearerAuth API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
{ "status": "resubmitted", "posted": true, "phoneNumber": { "id": "string", "status": "string" }, "siblingsResubmitted": 0}Reply to the regulatory reviewer
Post a free-text reply (with optional file attachments) to the reviewer on a number awaiting remediation — for asks the structured form can't express (e.g. "is this personal or business?"). Attachments are stored by us and their links are added to the reviewer's comment thread (the carrier's number order takes no loose files). A reply to a comment-style ask moves the number back to "in review"; a reply on a formal decline is supplementary and you must still resubmit the fix. Requires text or at least one attachment.
Check portability
Pre-flight portability check: whether each number can be ported in and whether it qualifies for FastPort, BEFORE the user commits to a port order (LOA, invoice, service address). Read-only; creates no order and bills nothing.