Correct an existing SMS application
amend_sms_applicationCorrect an existing SMS registration at the needs_information step by submitting corrected fields, the existing address, and consent attestation; identity changes are rejected.
Instructions
Correct an existing SMS registration at the needs_information step.
The address must be accurate; saved details can be reused when still correct.
Identity changes are rejected. This operation does not create a replacement brand.
Actual consent evidence is required.
Limits are 100 fields and 64 KiB of combined fields and address. No documents are uploaded.
A later campaign filing can incur the normal review fee.
After a timeout, the existing registration can already reflect the correction.
Returns the updated registration or an error.Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"verification_id": "<verification_id>",
"fields": "<fields>",
"attest_authorized": "<attest_authorized>"
},
"name": "amend_sms_application"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | Yes | Complete corrected answers that satisfy the current requirements; ``get_sms_application`` returns the saved ones. | |
| address | No | The sender's original address, as saved; ``get_sms_application`` returns it. Omitted: the correction is refused, because Hail cannot confirm the sender is unchanged. | |
| verification_id | Yes | ID of the SMS registration at step ``needs_information``, from ``list_verifications``; the same paid application and identity. | |
| attest_authorized | Yes | ``true`` records that the applicant reviewed and approved these corrections. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||