Mixmax

MESSAGING · MESSAGING

Sequences, snippets, messages, and meeting summaries under their own login.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

mixmax_delete_v1_contactgroups_by_id_contacts_by_contactidWRITE

/contactgroups/:id/contacts/:contactId [deprecated] via DELETE /v1/contactgroups/{id}/contacts/{contactId}

api

mixmax_delete_v1_snippettags_by_idWRITE

/snippettags/:id via DELETE /v1/snippettags/{id}

api

mixmax_get_v1_callsREAD

/calls via GET /v1/calls

api

mixmax_get_v1_calls_by_id_transcriptREAD

/calls/:id/transcript via GET /v1/calls/{id}/transcript

api