sender_identity_not_verified
The sending company has not proven its identity yet, and without that it cannot write to external recipients from the shared sender domain. This is neither an exhausted quota nor a permission problem: the credential holds the scope, and waiting does not clear it.
| Code | Type | HTTP | Category |
|---|---|---|---|
sender_identity_not_verified | invalid_request_error | 422 | Account |
Cause
The sending company has not proven its identity yet, and without that it cannot write to external recipients from the shared sender domain. This is neither an exhausted quota nor a permission problem: the credential holds the scope, and waiting does not clear it.
What to do
Prove the account identity through either of the two equivalent routes — one is enough: activate a subscription in the account billing settings, or verify its tax identifier against the Spanish Tax Agency census. When the company is administered by an accounting firm — error.details.resolved_against reads managing_company — the firm is the one that must prove it, and this company needs no plan of its own.