Help menu Backup, updates & tools
Let your tools collect codes and links
Turn on the Tasks API, copy the key, and test it with a code email.
Works in: Windows app8 minUpdated 2026-11-16
The Tasks API lets your tools wait for a verification code or login link sent to one of your addresses. Results pass through Mailman's server in memory only, and are dropped once collected or after an hour.
Turn it on 3 min#
- Open Settings → Tasks API and turn on Enable Tasks API. It applies at once.
- Under API keys, select + New key, name it after the tool that will use it, and copy the key. It's shown once. A key you already had is listed as "API key".
- Paste the key into your tool and keep Mailman open and signed in.
You can have up to eight keys. The key's name is the Source on every task it sends, so you can filter by it.

Test it 2 min#
- Open Tasks API in the left rail (under More on a phone) and select Test with a code email.
- Enter the receiving address and select Start test, then send it an email with "code" in the subject and a 4 to 8 digit code. To use an email that already arrived, set Look back.
The test works even while the Tasks API is off.
Read the task list#
- Tasks still waiting for an email stay at the top, with the time left. Finished tasks are grouped by day, newest first.
- Each row shows when the task was requested, the email, template, Source, how long it took, and the result. Select a code or link to copy it.
- Search by email, task ID, code or link, or paste a list of emails. Filter by status, time, template or source. The tiles at the top filter the list too.
- Select a task to see why it ended the way it did, with a fix to try: a timeout shows the closest email that almost matched. The Timeline shows every step to the millisecond, and Request & response shows the raw task.
- Live pauses and resumes new rows. Tasks keep running while paused. Export saves the list.
- In the page's settings, choose the default timeout, Match mail received (for retries and local tasks; API requests use their own
receivedAt), Show times in local time or UTC, and Keep history for (30 days by default). Clear history… deletes finished tasks; waiting tasks keep running.
Choose which inboxes#
- The Tasks API creates no inboxes. A task takes only mail sent to its exact address. By default Mailman matches your account emails and aliases, including
+tags and Gmail dot variants. - For others, such as a catch-all inbox, select Create template. Enter a Template ID and Label, pick groups or accounts, and select Save template. IDs ignore capitals, so
CatchAllandcatchallare the same template. The ID can't change, and edits affect new tasks only. - Under Advanced, Maximum active inboxes (200 by default, up to 10,000) caps how many inboxes Mailman watches. Select Save task settings.
- Developer tools has the test builder. Tool setup is on the Developers page.
If it didn't work#
| You see | Do this |
|---|---|
| "Mailman on another computer is using this API key" | Two computers share one key, as after a restored backup. Select Regenerate on one. |
| A tool gets "invalid task template" | The template ID is unknown, or the template matches no account. A tool that sends default gets the email and alias matching. |
What's next
Connect scripts and assistants
Turn on the local API or a remote connector, then revoke access when you are done.
Find and copy a verification code
Copy the newest code with one key, and check how old it is.
Back up Mailman and move computers
Export one encrypted file, then restore it on another computer.