Number Requests (v2)
Correct Resource Request
Return requested changes to the same provider Resource Request.
POST
Submits a complete correction to the existing provider Resource Request. Correction is allowed only when the stored provider status is:
UPDATE_REQUESTED; orUPDATE_REQUESTED_BY_INTERNAL_REVIEWER.
Send an
Idempotency-Key when retrying a correction. The key is bound to this concrete request path and payload; an exact retry replays the first successful response. See Idempotency.Path parameters
string
required
Number request id.
Optional body
When saved requirement and document data is already complete, omit the request body or send{}. To save changes and submit them in the same operation, send any of the three fields accepted by Update International Requirements:
internationalAcquisitionFormData;internationalAcquisitionDocuments;internationalAcquisitionDocumentRemovedKeys.
Content-Type: application/json. JSON null, malformed JSON, and a body sent with another content type return 400 validation_failed.
Behavior
Before calling the provider, Trackly:- loads the live requirement schema;
- preserves user-entered and provider-returned values;
- prefills only exact known keys from the NumberRequest;
- verifies every required field and document;
- rebuilds the full
{key, value}requirement array; - updates the same provider request id.
Example
Error codes
Provider update permission cannot be proven by read-only lookup. A 403 is returned as the safe
acquisition_update_unavailable capability error.
Next steps
Get Requirements
Poll status and feedback
Get Number Request
Track provisioning