List sending numbers and inspect current identity, quality, and tier state.
How it works
List sending numbers and inspect current identity, quality, and tier state. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.
Set it up
- Authenticate with a project key scoped to the intended environment and resource.
- Validate identifiers, fields, channel capability, and consent before the request.
- Persist resource IDs and reconcile asynchronous state from signed events.
What to expect
- The operation is traceable by stable request and resource identifiers.
- Acceptance, provider delivery, and customer interaction remain separate states.
- Retries and reordered events do not duplicate the customer action.
[!TIP] Keep API keys, signing secrets, customer addresses, and message bodies out of source and logs.