Skip to main content
PUT
Confirm Business for Number Request
Requires an account-owned live API key with an associated user. Both the business and number request must belong to that account. The request must be inactive and editable; agent-prepared requests require owner review in Trackly. Fetch the business’s current verificationIdentityRevision, display the legal entity to the customer, and obtain their confirmation. Then send exactly:
expectedIdentityRevision is a non-negative integer. Use the returned 0 for a legacy business that has not yet initialized its verification revision. relationship is account_business or client_business; an existing confirmed relationship cannot be changed. confirmed must be the JSON boolean true.

Response and readiness

Returns 200 with the same request.id and a businessVerification summary containing profileId, status, identityRevision, relationship, ready, code, message, and confirmationRequired. Binding a pending business succeeds with ready: false. Finish the request while verification runs, then submit it once ready. Binding does not pay for verification, publish a site, submit a number, or copy business documents, carrier identifiers, brand, or support contacts. A matching current verified business can be confirmed for later number requests without another verification payment. The legal identity must match; different legal and carrier identifier types can remain distinct. For an older draft, recognized state or province names are saved in canonical form before confirmation. A competing edit returns 409; reload the request before confirming again.

Errors and retry

Retry a lost response by fetching the same request; do not create another business or number request. A later identity edit requires fresh customer confirmation. Malformed confirmation errors include fields, with a field and code for each missing, unexpected, or invalid value. Missing keys also appear in missingFields.