A public API is on its way.

Today

No public API yet.

The interfaces behind the product still change as it grows. Publishing them now would mean breaking the integrations you build on them.

The browser extension

The extension uses a private, scoped connection.

The Smart Button talks to HyverMail through a private interface limited to what the extension needs. Each browser is connected with its own token, and disconnecting the extension revokes that token straight away.

Planned

What the public API will cover first.

The first version is planned around the tasks people automate most often:

• Creating, listing, pausing and deleting aliases.
• Choosing which verified inbox an alias delivers to.
• Delivery metadata for your own aliases, never message content.

Request access

Building something that needs it?

Tell us what you would like to automate. It shapes what we build first.