Skip to main content
PATCH
Updates an account-owned number request before provider identity is locked. Drafts accept partial fields and remain inert; required submission checks run when the draft is submitted. For a submitted request, the server merges supplied fields with the stored request and validates the complete result. Editing correction details does not require current verification, but submitting them to the provider does.
Carrier identity cannot be changed once brand registration has started or completed. Readiness corrections use the limited fields below and preserve the business identity, verification, request ID, and existing provider resources. Do not reset or replace a request to resolve a readiness finding.
phoneNumberType is immutable after creation. targetCountries can change only before a Resource Request exists. Changing it before that point clears stale international form values, documents, feedback, and status.
Changing addressCountry without identifierType clears the old type. A single-option country resolves automatically; AU, CA, FR, and ES require a new explicit country-scoped type.
Send an Idempotency-Key when retrying an update. The key is bound to this concrete request path and payload: an exact retry replays, while reuse for another request id returns 409 idempotency_conflict. See Idempotency.

Path parameters

string
required
Number request id.

Body

Readiness corrections

Read registration readiness first. When canCorrect is true, an inactive ordinary request can accept changed values for promotionSummary, exampleSmsMessage, messagingType, contactEmail, contactPhone, privacyPolicyUrl, termsConditionsUrl, and optInFormUrl. Send only the fields being corrected. This path supports eligible pending, under_review, approved, and rejected requests as well as drafts; active provider operations remain guarded. Saving does not reset status or submit the correction to a carrier. Read back the same request and recheck readiness before continuing. Identity changes remain locked, and agent-prepared requests require their owner revision flow in Trackly. A 409 requires readback and reconciliation of the existing request. For this correction path, summaries are limited to 1,000 characters, example messages to 4,000, support email to 255, support phone to 20, and each URL to 500. Correction URLs must pass the server’s public HTTP(S) URL validation.

Other editable requests

The body accepts the request-owned fields from Create Number Request, including:
  • brandName, companyLegalName, taxId, and identifierType;
  • business address and carrier contacts;
  • websiteUrl, optInFormUrl, termsConditionsUrl, and privacyPolicyUrl;
  • targetCountries, messaging program fields, and volume.
Use Confirm Business to change or renew the explicit business binding. Neither businessProfileId nor businessVerification is a general PATCH field. Identity edits can invalidate existing confirmation; check the returned businessVerification summary. taxId remains write-only in the response. termsConditionsUrl is syntax-checked as an HTTP(S) URL but does not need a publicly resolvable host; websiteUrl and optInFormUrl must remain publicly reachable.

Example

Error codes

Identifier errors include allowedIdentifierTypes when choices are available.

Next steps

Get Number Request

Verify the persisted request

Correct Resource Request

Return requested provider changes on the same id