Skip to content
Changelog

Report a bug

Mixmax integration: operations for AI agents

Mixmax connects to Type.com as an integration. This page lists the 135 operations documented for Claude and Codex in Type.com: 67 read, 45 write, 23 destructive.

About Mixmax

The #1 Sales Engagement Platform for Gmail. Mixmax provides email tracking, scheduling, sequences, and productivity tools for sales teams.

Categories: Email & Messaging

How to connect Mixmax to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

135 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

135 operations listed.

Calendar

  • Read

    /appointmentlinks/me

    Returns your Mixmax Calendar link name, the last part of https://cal.mixmax.com/ . You can also change it in the Calendar settings of the Mixmax dashboard. If you have no link yet, one is created for you and returned.

  • Read

    /meetinginvites

    Lists the meeting invites you sent: emails where you offered times to meet. Times are Unix milliseconds. Booked meetings appear under the time slot that was picked, in timeslots[].events.

  • Read

    /meetinginvites/:id

    Retrieves one of your meeting invites.

  • Read

    /meetingtypes

    Lists your meeting types: the kinds of meeting people can book with you, each with its own length, availability and booking link.

  • Read

    /meetingtypes/:id

    Retrieves one of your meeting types. Like the list, reading it can repair it and email you about the change.

  • Write

    /appointmentlinks/me

    Changes your Mixmax Calendar link name, the last part of https://cal.mixmax.com/ . The old link stops working as soon as the name changes. Names must be unique across all Mixmax users. Returns 204 with no body on success.

  • Write

    /meetingtypes

    Creates a meeting type. The body must include every required field (see the schema), and userId must be you or someone in your workspace. Creating one also creates its reminder automation, as a paused rule.

  • Write

    /meetingtypes/:id

    Updates one of your meeting types. Send only the fields to change; any field of the meeting type can be updated. Changes apply to the live booking page at once.

  • Destructive

    /meetingtypes/:id

    Deletes one of your meeting types and its automation rules. You cannot delete your last meeting type. If it was your default for any kind of meeting, that default is cleared.

Code snippets

  • Read

    /codesnippets

    Lists the Formatted Code enhancements you created, newest first, one page at a time. Pass the next value from a response to get the following page.

  • Read

    /codesnippets/:id

    Returns one of your Formatted Code enhancements. A snippet that does not exist, or that belongs to someone else, returns 404 with an empty body.

  • Write

    /codesnippets

    Creates a Formatted Code enhancement that you can then insert with the /code command in the editor. No field is required and values are stored as sent, without validation, so a request with an empty body still creates an empty snippet.

File requests

  • Read

    /filerequests

    Lists the file requests you sent, newest first. You create file requests in the Mixmax editor; the API can only read them. Each upload is recorded under uploads.

  • Read

    /filerequests/:id

    Retrieves one of your file requests.

Reports

  • Read

    /insightsreports

    Lists the saved Insights reports you can access, 50 at most per page.

  • Write

    /insightsreports

    Saves an Insights report. To run a report's query, use POST /v1/reports/data/table.

  • Write

    /reports/data/table

    Queries messages and meetings. If you're looking to query for any analytics in Mixmax, this is likely the API you want.

  • Write

    /insightsreports/:id

    Updates a report you can edit: yours, or one shared with you with edit rights. Only the fields you send change.

  • Destructive

    /insightsreports/:id

    Deletes a report you own.

Integrations

  • Read

    /integrations/commands

    Lists the slash commands available to you in the Mixmax editor: Mixmax's own, and those you or your workspace added. Each has an id, used to delete it, and a separate id used only for analytics.

  • Read

    /integrations/enhancements

    Lists the editor enhancements available to you, Mixmax's own and those you added.

  • Read

    /integrations/linkresolvers

    Lists the link resolvers available to you. A link resolver turns a pasted URL that matches its regex into a rich preview from resolverUrl.

  • Read

    /integrations/sidebars

    Lists the sidebar apps available to you. Do not pass limit; this list returns 500 when you do.

  • Write

    /integrations/commands

    Adds a slash command to your account. Only you can use it; email support@mixmax.com to share it. Mixmax calls commandParameterHintsUrl as you type and commandResolverUrl to insert the result.

  • Write

    /integrations/enhancements

    Adds an editor enhancement to your account: a button in the Mixmax editor that opens editorUrl and inserts what resolverUrl returns. Only you see it; email support@mixmax.com to share or publish it.

  • Write

    /integrations/linkresolvers

    Adds a link resolver to your account. A broad regex takes over every matching link you paste.

  • Write

    /integrations/sidebars

    Adds a sidebar app to your account. Give it an iconImage, or both iconName and iconColor.

  • Destructive

    /integrations/commands/:id

    Deletes a slash command you added.

  • Destructive

    /integrations/linkresolvers/:id

    Deletes a link resolver you added.

  • Destructive

    /integrations/enhancements/:id

    Deletes an enhancement you added.

  • Destructive

    /integrations/sidebars/:id

    Deletes a sidebar app you added.

Live feed

  • Read

    /livefeed

    Searches the live feed: messages you sent, or that teammates shared, with their tracking results, sorted by most recent activity first. By default only your own messages are returned (the query defaults to from:me).

  • Read

    /livefeed/events

    Lists tracking events (opens, clicks, downloads, replies, bounces and meeting invite responses) for one live feed message or for one contact, newest first. Pass messageId or contactEmail. With messageId, the last page ends with an extra sent event for the message itself.

Messages

  • Read

    /messages

    Lists your messages (emails) that are drafts, scheduled, sent, or failed to send, newest first by created. Deleted messages are left out. Mixmax removes the body of a message once it is sent, so sent messages have an empty or missing body.

  • Read

    /messages/:id

    Retrieves one message. You can read messages you sent, messages you sent as a delegate, and messages in sequences you can access. Deleted messages can still be read here, although GET /v1/messages leaves them out. Any other id returns 404 with an empty body.

  • Write

    /messages

    Creates a draft message (an email). This does not send it; use POST /v1/messages/{id}/send to send it or POST /v1/messages/{id}/schedule to schedule it. The response is the stored message, which includes some fields that the other message endpoints do not return.

  • Write

    /messages/:id

    Updates a message you sent or sent as a delegate. Only the fields you include change; each one replaces the stored value, so to, cc and bcc replace the whole list. Fields not listed below are ignored.

  • Write

    /messages/test

    Sends a test email to yourself. Mixmax creates a message addressed to your own account, fills in template variables in subject and body, and sends it right away. You cannot choose the recipient. Variables use double braces, for example {{first name}}.

  • Write

    /send

    Sends a plain email from your own mailbox right away, through Gmail or Outlook. Use it for simple transactional email. It creates no Mixmax message: there is no tracking, no Live Feed entry and no CRM logging.

  • Write

    /messages/:id/send

    Sends a saved draft message. Returns 202 once the message passes validation and is queued; delivery happens asynchronously. Returns 410 if the message was already sent or is sending.

  • Write

    /messages/:id/schedule

    Schedules a saved message to send later. It moves to your Outbox, and its Gmail draft is deleted. You must be the message's sender or delegator; otherwise the response is 404. The message is checked first: at most 100 recipients, all with valid addresses.

  • Destructive

    /messages/:id/schedule

    Cancels a scheduled send. The message goes back to being a draft; for Gmail users, a Gmail draft is written back. The response is plain text (sent as text/html).

Rules and webhooks

  • Read

    /rules

    Lists your rules, newest first, 50 at most per page. A rule watches for an event in Mixmax, such as a message being received, checks it against an optional filter, and then runs its actions, such as posting to your webhook. Rules are also managed in the Mixmax app under Rules.

  • Read

    /rules/events

    Lists the run history of your rules from the last 15 days, newest first, 50 per page by default.

  • Read

    /rules/events/:id

    Retrieves one rule event, including the full payload the rule ran on. You can retrieve your own events, and workspace admins can retrieve their teammates'. Mixmax stores events in blocks of three days, and finds an event by the block its date falls in.

  • Read

    /rules/:id

    Retrieves a rule. Workspace admins can retrieve the rules of anyone in their workspace; everyone else can retrieve only their own.

  • Read

    /rules/:id/actions

    Lists a rule's actions, 50 per page by default. Actions are the "then" part of a rule: what happens when it runs. Signing secrets are never listed; you get their last four characters instead.

  • Write

    /rules

    Creates a rule. A new rule has no actions: add them with POST /v1/rules/{id}/actions, for example a webhook. Create it with isPaused: true if you want to add its actions before it starts running. Triggers - event runs the rule each time eventName happens for you.

  • Write

    /rules/:id

    Updates a rule. Only the fields you send change; name, trigger, filter and isPaused can be updated. PUT on the same path behaves exactly the same way. Rules created under Settings API cannot be changed here.

  • Write

    /rules/:id/actions

    Adds an action to a rule. The action's type says what it does, and its other fields configure it. To send events to your own endpoint, use postToWebhook: - webhookUrl: your HTTPS endpoint. Addresses that resolve to a private network are refused.

  • Write

    /rules/:id/actions/:actionId

    Updates an action. Only the fields you send change. To replace a webhook's signing secret, send {"rotateSigningSecret": true}. The old secret stops working at once, and the response is the only time you see the new one.

  • Destructive

    /rules

    Deletes several rules and their actions at once. Send the rules' ids as ids in a JSON body; ids in the query string is ignored and fails with 400. Ids you cannot access are skipped without an error, so the response is 204 even when nothing was deleted.

  • Destructive

    /rules/:id

    Deletes a rule and its actions. Rules created under Settings API cannot be deleted here.

  • Destructive

    /rules/:id/actions/:actionId

    Deletes an action. Deleting an action that was already deleted returns 204 again.

Salesforce

  • Read

    /salesforce/account

    Lists the Salesforce Accounts visible to you, from Mixmax's synced copy of your Salesforce data. Changes made in Salesforce can take a while to show up here. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/account/implicit

    Finds the Salesforce Account for an email domain. Mixmax looks for synced Contacts whose email uses that domain and belong to an Account, and returns the most recently modified of those Accounts. Domains of free email providers, such as gmail.com, never match.

  • Read

    /salesforce/account/:id

    Gets a Salesforce Account by Id, from Mixmax's synced copy of your Salesforce data. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/contact/:id

    Gets a Salesforce Contact by Id, from Mixmax's synced copy of your Salesforce data. Both 15- and 18-character Ids are accepted. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/contact/:id/tasks

    Lists the Salesforce Tasks whose WhoId is this Contact, from Mixmax's synced copy of your Salesforce data. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/contactOrLead

    Finds the Salesforce Contact or Lead with an email address. A Contact is returned in contact, a Lead in lead, along with all of its synced fields and salesforceURL.

  • Read

    /salesforce/lead/:id

    Gets a Salesforce Lead by Id, from Mixmax's synced copy of your Salesforce data. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/lead/:id/tasks

    Lists the Salesforce Tasks whose WhoId is this Lead, from Mixmax's synced copy of your Salesforce data. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/opportunity/:id

    Gets a Salesforce Opportunity by Id, from Mixmax's synced copy of your Salesforce data. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/search

    Searches Salesforce records of one type by name, from Mixmax's synced copy of your Salesforce data. The match is on the start of the name and ignores case, so q=burl finds "Burlington Textiles". Searching Users returns active Users only.

  • Read

    /salesforce/syncedFields

    Lists the fields Mixmax syncs for one or more Salesforce object types, with each field's label, type, whether it's required or createable, and its picklist values. Use it to find the field API names to pass in fields and in request bodies.

  • Read

    /salesforce/task/:id

    Gets a Salesforce Task by Id, from Mixmax's synced copy of your Salesforce data. Requires a personal API token whose user is connected to Salesforce.

  • Read

    /salesforce/what/:id

    Gets a Salesforce Account or Opportunity by Id, from Mixmax's synced copy of your Salesforce data. Use it to resolve a Task's WhatId. Accounts are checked first. Add type to fields to learn which kind of record matched.

  • Read

    /salesforce/who/:id

    Gets a Salesforce Contact or Lead by Id, from Mixmax's synced copy of your Salesforce data. Use it to resolve a Task's WhoId. Contacts are checked first. Add type to fields to learn which kind of record matched. Requires a personal API token whose user is connected to Salesforce.

  • Write

    /salesforce/account

    Creates a Salesforce Account. The request body is the Account's fields, keyed by Salesforce field API name. Name is required by Salesforce, along with any fields your org makes required. Requires a personal API token whose user is connected to Salesforce.

  • Write

    /salesforce/contact

    Creates a Salesforce Contact. The request body is the Contact's fields, keyed by Salesforce field API name. LastName is required by Salesforce, along with any fields your org makes required. Requires a personal API token whose user is connected to Salesforce.

  • Write

    /salesforce/lead

    Creates a Salesforce Lead. The request body is the Lead's fields, keyed by Salesforce field API name. LastName and Company are required by Salesforce, along with any fields your org makes required. Requires a personal API token whose user is connected to Salesforce.

  • Write

    /salesforce/opportunity

    Creates a Salesforce Opportunity for a Contact, and adds that Contact to it as an Opportunity Contact Role. The request body is the Opportunity's fields, keyed by Salesforce field API name, plus ContactId.

  • Write

    /salesforce/task

    Creates a Salesforce Task. The request body is the Task's fields, keyed by Salesforce field API name, for example Subject, WhoId (a Contact or Lead), WhatId (an Account or Opportunity), ActivityDate and Status. Requires a personal API token whose user is connected to Salesforce.

  • Destructive

    /salesforce/account/:id

    Updates a Salesforce Account. Send only the fields you want to change, keyed by Salesforce field API name. The body must include the Account's Id. The Id in the URL is not used to pick the record, and a body without Id fails.

  • Destructive

    /salesforce/contact/:id

    Updates a Salesforce Contact. Send only the fields you want to change, keyed by Salesforce field API name. The body must include the Contact's Id. The Id in the URL is not used to pick the record, and a body without Id fails.

  • Destructive

    /salesforce/lead/:id

    Updates a Salesforce Lead. Send only the fields you want to change, keyed by Salesforce field API name. The body must include the Lead's Id. The Id in the URL is not used to pick the record, and a body without Id fails.

  • Destructive

    /salesforce/opportunity/:id

    Updates a Salesforce Opportunity. Send the fields you want to change, keyed by Salesforce field API name. The body must include the Opportunity's Id and a valid CloseDate, even if you aren't changing the close date. The Id in the URL is not used to pick the record.

  • Destructive

    /salesforce/opportunity/:id

    Deletes a Salesforce Opportunity. Requires a personal API token whose user is connected to Salesforce. The Opportunity is deleted with that user's Salesforce credentials.

  • Destructive

    /salesforce/task/:id

    Updates a Salesforce Task. Send only the fields you want to change, keyed by Salesforce field API name. The body must include the Task's Id. The Id in the URL is not used to pick the record. Unlike the other Salesforce updates, a Task update that Salesforce rejects returns 400.

  • Destructive

    /salesforce/task/:id

    Deletes a Salesforce Task. Requires a personal API token whose user is connected to Salesforce. The Task is deleted with that user's Salesforce credentials.

Sequences

  • Read

    /sequences

    Lists the sequences you can access: your own, those shared with you, and, for workspace admins, those of the workspace. Up to 100 per page.

  • Read

    /sequences/:id/recipients

    Lists the recipients of a sequence you have access to, with per-stage activity. Only recipients that were added to the sequence are listed; recipients still in the draft are not. The response is a plain array, not an object with results and next.

  • Read

    /sequences/search

    Searches the recipients of every sequence you have access to, including sequences shared with you, and returns each match with its status and per-stage activity. A person in several sequences appears once per sequence. Neither query nor recipients is required.

  • Read

    /sequencefolders

    Lists the sequence folders you can access.

  • Read

    /sequencefolders/:id

    Retrieves a sequence folder you can access.

  • Write

    /sequences/cancel

    Stops recipients you added, in every sequence at once. Cancelled recipients get no further emails, their open sequence tasks are deleted, and they are marked completed. Paused recipients are included; recipients that already finished are left alone.

  • Write

    /sequences/:id/cancel

    Stops recipients of one sequence. With emails, it cancels the active recipients with those addresses: all of them if you have read-write access to the sequence, otherwise only the ones you added. Without emails, it cancels every active recipient you added to this sequence.

  • Write

    /sequences/:id/recipients

    Adds recipients to a sequence and, unless they are kept as drafts, starts sending to them. You need the sequence activation feature, otherwise the response is 403 with an empty body. The response is 200 even when some or all recipients were not added.

  • Write

    /sequencefolders

    Creates a sequence folder.

  • Write

    /sequencefolders/:id

    Renames a sequence folder. Always send name: a request without it clears the folder's name.

  • Write

    /sequencefolders/:id/sequences

    Moves sequences into this folder, taking them out of the folder they were in. You need read-write access to this folder, and for each sequence either read-write access to its current folder or write access to the sequence.

  • Destructive

    /sequencefolders/:id

    Deletes a sequence folder. Its sequences are kept and simply have no folder. Only the folder's owner, or an admin of the owner's workspace, can delete it; sharing it with you is not enough.

Templates

  • Read

    /snippets (aka Templates)

    Lists the templates you can access: your own, those shared with you directly or through a team or your workspace, and, for workspace admins, those of everyone in the workspace. In the backend templates are called snippets, and their folders snippet tags.

  • Read

    /snippets/:id

    Retrieves a template you can access. Templates in the trash return 404 unless you pass includeDeleted.

  • Read

    /snippettags

    Lists the template and snippet folders you can access. Folders are called snippet tags in the backend.

  • Read

    /snippettags/:id

    Retrieves a folder you can access.

  • Read

    /snippettags/:id/snippets

    Lists the templates in a folder, leaving out trashed ones. Templates with no content come last.

  • Write

    /snippets/:id

    Updates a template. You need read-write access to it or to its folder. Only the fields you send change. If the template has no name, setting title also sets name.

  • Write

    /snippets/:id/send

    Sends an email from a template, right away unless you pass scheduledAt. You only need read access to the template.

  • Write

    /snippettags

    Creates a template folder, or a snippet folder with ?isInline=true.

  • Write

    /snippettags/:id

    Renames a folder. You need read-write access to it. Always send name: a request without it clears the folder's name.

  • Write

    /snippettags/:id/snippets

    Creates a template in a folder, or moves an existing one into it. You need read-write access to the folder. - Create: send the template's fields, without id. - Move: send id. The template leaves every other folder. You need read-write access to the folder it is in now.

  • Destructive

    /snippets/:id

    Moves a template to the trash, or archives it with archive. You need read-write access to it or to its folder. It is also removed from its folders. To restore it, add it to a folder with POST /v1/snippettags/{id}/snippets.

  • Destructive

    /snippettags/:id

    Deletes a folder and moves every template in it to the trash. You need read-write access to the folder; otherwise, or if it does not exist, the response is 404.

Teams

  • Read

    /teams

    Lists the teams you are an accepted member of, newest first. Workspace admins also get every team in their workspace and every team with an accepted member from their workspace; pass accessThrough=myself to leave those out. Members are left out unless you pass expand=members.

  • Read

    /teams/:id

    Fetches a team you are an accepted member of, or, as a workspace admin, a team you can see through your workspace. Members are left out unless you pass expand=members.

  • Read

    /teams/:id/members

    Lists every member of a team, including pending invites, in one response. This list is not paginated. Pass expand=members.userId to add each Mixmax user's name and email.

  • Write

    /teams

    Creates a team with you as its admin and returns it with its members expanded. Each address in members is added and sent an invite email. A Mixmax user whose email domain matches yours is added as already accepted, except for gmail.com and googlemail.com addresses.

  • Write

    /teams/:id

    Renames a team. Only a team admin or a workspace admin can call it. name is the only field it changes; other fields are ignored. The response is the team's id as a JSON string.

  • Write

    /teams/:id/members

    Adds people to a team and sends them invite emails. Only a team admin or a workspace admin can call it. The response is the full list of members after the change, without names or emails. Addresses already on the team are skipped.

  • Write

    /teams/:id/members/:memberId

    Changes a team member's role to admin or member. Only a team admin or a workspace admin can call it. role is the only field that changes; other fields in the body are ignored. The response body is true. Only members who have accepted their invite can be changed.

  • Destructive

    /teams/:id

    Deletes a team. Only a team admin or a workspace admin can call it. Anything shared with the team stops being shared with it.

  • Destructive

    /teams/:id/members/:memberId

    Removes a member from a team. A team admin or workspace admin can remove anyone except the last accepted admin; a member with the member role can remove themselves to leave the team. Pending invites can be removed the same way.

Unsubscribes

  • Read

    /unsubscribes

    Lists the addresses on your unsubscribe list. If you belong to a workspace, this is the workspace's list, including addresses other members added. Sequences do not send to addresses on this list.

  • Write

    /unsubscribes

    Adds addresses to your unsubscribe list, or your workspace's list if you belong to one. Sequences then stop sending to them. Addresses are stored in lowercase. Send email (and optionally name) to add one address, or emails to add several.

  • Destructive

    /unsubscribes

    Removes an address from your unsubscribe list. If you belong to a workspace, this also removes records other workspace members added for that address. The response is 204 whether or not the address was on the list.

Users

  • Read

    /userpreferences/me

    Returns your user preferences document. Without fields it returns every stored key, which can be large; the schema lists the common ones.

  • Read

    /userpreferences/me/autoBccExcludedEmails

    Checks whether one address is excluded from your auto BCC. Returns 200 with the plain-text body OK if it is, and 404 with Not Found if it is not. An address counts as excluded when it is on your autoBccExcludedEmails list or its domain is in your autoBccExcludedDomains.

  • Read

    /users/me

    Returns the id of the user the API token belongs to. Nothing else about the user is returned; use /userpreferences/me for settings.

  • Write

    /userpreferences/me

    Sets the preference keys in the body and returns them as sent. Keys you leave out are not changed. id and userId are ignored. Keys are not checked against a list: any key you send is stored, so check spelling.

  • Write

    /userpreferences/me/autoBccExcludedEmails

    Adds addresses to your autoBccExcludedEmails list, so messages to them are never auto BCC'd. Send one address as email or several as emails; when emails is an array, email is ignored. Each address gets its own result.

  • Write

    /userpreferences/me/autoBccExcludedEmails/exists

    Checks several addresses at once and says, for each, whether it is excluded from your auto BCC. An address is excluded when it is on your autoBccExcludedEmails list or its domain is in your autoBccExcludedDomains, including exclusions set by your workspace role.

Yes/No questions

  • Read

    /yesno

    Lists the Yes/No questions you have sent, newest first, one page at a time, with the email addresses of the people who picked each answer. Pass the next value from a response to get the following page.

  • Read

    /yesno/:id

    Returns one of your Yes/No questions with the email addresses of the people who picked each answer. A question that does not exist, or that belongs to someone else, returns 404 with an empty body.

Polls

  • Read

    /polls

    Returns the polls you have sent in Mixmax emails, newest first, with the people who voted for each option. A poll is saved when the email that contains it is sent, so polls that are still in a draft are not listed. Results are paginated.

  • Read

    /polls/:id

    Returns one of your polls by its id, with the people who voted for each option. Returns 404 with an empty body when the poll does not exist or belongs to someone else.

Meetings

  • Read

    /meetings/summaries/search

    Search and retrieve meeting summaries with optional filters. Returns summaries for meetings where the authenticated user is the owner, or if workspace-wide access is enabled via admin settings, summaries for all workspace members.

  • Read

    /meetings/transcripts/:id

    Retrieve the full transcript for a specific meeting by its summary ID. Returns the complete transcript with speaker identification and timestamps.

Q&A

  • Read

    /qa

    Lists your Q&A forms: questions you embedded in emails, with the answers recipients submitted. Each answer records who sent it. These are not the Yes/No questions in /v1/yesno.

  • Read

    /qa/:id

    Retrieves one of your Q&A forms with its answers.

Calls

  • Read

    /calls [beta]

    Limited beta. The Calls read API is currently gated by an access allowlist; callers without access receive 404 responses. To request access, email developer@mixmax.com. Lists calls placed with the Mixmax Dialer, newest first.

  • Read

    /calls/:id/recording [beta]

    Limited beta. The Calls read API is currently gated by an access allowlist; callers without access receive 404 responses. To request access, email developer@mixmax.com. Streams a completed call's recording as MP3 audio. Requires the Dialer calling feature on your workspace.

  • Read

    /calls/:id/transcript [beta]

    Limited beta. The Calls read API is currently gated by an access allowlist; callers without access receive 404 responses. To request access, email developer@mixmax.com. Returns the transcript of a completed call.

Tasks

  • Read

    /tasks

    Lists Mixmax tasks visible to the API key owner. The endpoint supports the same task types, filtering, sorting, and cursor pagination as the Mixmax Tasks product. Regular users can read their own assigned tasks.

See How connections work for access and permissions, or browse all integrations.

Reference date: October 27, 2026. Mixmax API docs.