Skip to content

Settings and integrations resources

Read and update settings; configure app extensions, Apple Pay, OAuth, and groups.

Updated View as Markdown

Read and update settings; configure app extensions, Apple Pay, OAuth, and groups.

How it works

Read and update settings; configure app extensions, Apple Pay, OAuth, and groups. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.

Set it up

  1. Authenticate with a project key scoped to the intended environment and resource.
  2. Validate identifiers, fields, channel capability, and consent before the request.
  3. 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.

Navigation

Search for a question, a feature, or a task.

↑↓ to navigate↵ to openEsc to close