VeruSuite APIs

The workspace API you were about to write yourself.

Mail, calendar, contacts, files and user provisioning over plain HTTP. Make a key in the console, tick what it may do, curl it. No OAuth dance, no client registration, no sales call. It is already in your plan.

Read the reference Browse the endpoints

Four lines, one of which is the key

There is no onboarding. Create a key, tick mail.send, and send something. Nobody has to approve it and nothing has to be registered.

curl https://api.veruapis.com/v1/messages/send \
  -H "Authorization: Bearer vak_live_..." \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"to":["[email protected]"],"subject":"Nightly report","text":"All green."}'

That key sends mail. It cannot read any, because mail.send is all you ticked. And it acts as you, so it can never reach anything you could not reach yourself.

New

Let an agent do it, without handing over the whole mailbox.

Point Claude, Cowork or anything else that speaks MCP at a server you assemble in the console. You pick the tools. Everything you leave out does not exist as far as the client is concerned.

35 tools across mail and calendar, or start from a template and cut it down.
The client gets a token through OAuth. Nobody pastes a secret into a JSON file and forgets it is there.
Every call is in the log, and you can cut off one client without disturbing the others.

How MCP servers work Build one

One envelope, one cursor, one set of error codes

Every app your workspace already runs, behind the same contract. Learn it once on mail and it holds for calendar and files.

Mail

VeruMail

Read, organise and send email. Sending is its own permission, separate from writing.

21 endpoints

Calendar

VeruCalendar

Events, invitations, recurrence and availability.

14 endpoints

Contacts

VeruContacts

Address books and the people in them.

6 endpoints

Files

Space

Upload, download, organise and share files. Uploads are resumable, so a large file survives a dropped connection.

17 endpoints

Documents

Docs

Documents and their comments. Creating, renaming and trashing a spreadsheet happens here too, because a spreadsheet is a document.

11 endpoints

Spreadsheets

Sheets

The contents of a spreadsheet: reading and writing ranges, appending rows, and the structural changes that move data around. Changing structure is a separate permission from writing values.

9 endpoints

Workspace administration

Provisioning people, mailboxes, aliases and domains, plus the audit log. Separate permissions that only an administrator can put on a key.

0 endpoints

What people actually build

Nearly all of it is the same shape: something your business already knows, moved into or out of your workspace on a schedule.

Boring in the places it matters

The parts nobody mentions until the night they are missing.

Keys, not your password: A key carries the permissions you ticked and no others. Reading mail and sending it are separate. So are writing a file and sharing it.
Revoke means now: Keys are checked on every call, so a revoked one stops on the next request. You are not sitting out somebody else's token lifetime.
It works the same everywhere: Same envelope, same cursor paging, same error codes, whether you are in mail, calendar or files.
Retries are not scary: Every write takes an idempotency key, so a timeout is something you retry rather than something you go and investigate.
Your admins can see it: An administrator sees every key in the workspace, what it may do, when it was last used, and can revoke it.
Not an upsell: Every plan can use the API. The request allowance scales with the plan instead of being sold back to you.

Go make a key

Sign in with the VeruSuite account you already have, tick what the key may do, and copy it. It is shown once, so paste it somewhere before you close the tab.

Create a key How keys work