Ops (Operations) Usage

Ops or Operations are used to meter usage of the Mailsac service.

A Mailsac account’s subscription (or free plan) provides a certain number of allowed operations. Ops are allocated on a monthly basis. Ops usage resets on the first of the month UTC.

If an account performs more Ops than are allocated, Mailsac will send warning emails before disabling API access for the remainder of the month. This “soft limit” allows additional time to upgrade or adjust usage.

Ops were referred to as “api calls” until November 2021. The name was changed to Ops because not all tracked operations are REST API calls.

What Counts as an Op?

The following actions count as one Op:

The following actions do not count as an Op:

  • Viewing messages via the website

  • Deleting messages via the website

  • Forwarding (re-routing) mail internally to another Mailsac address

Monitor Ops Usage

Ops usage can be monitored via the Ops Usage page. The page includes current month, past usage by month, and all time usage.

Usage is not updated in real time. The metrics are calculated periodically throughout the day.

Calculating Ops Usage

Ops are calculated by summing the number of calls to the REST API, messages published to WebSockets, Webhooks, and Slack, and messages sent to a custom domain.

Inbound Message Ops

Inbound messages are tracked as Ops. The first forward of the message to Slack, Webhook, or WebSocket does not count as an additional Op. Second and third forwards will count as additional Ops.

Public Domain Ops

Validated Custom Domains can be set as public. API calls to the domain, its addresses or messages will be tracked on the domain owners account, not necessarily the account which performs the action.

Example Ops Calculation - Fetch Messages and Body of an Email

Viewing the body of a message via the REST API requires 2 API calls.

  1. The first Op is used to list all the messages in the inbox.

  2. The second Op is used to retrieve the plaintext body of a specific message.

Example Ops Calculation - Forward Message from Custom Domain to Slack

Receiving a message and publishing to Slack requires 1 Op.

  1. The Op is to receive the message in a custom domain.

The first forward of an inbound message to Slack, Webhook, or WebSocket does not count as an additional Op.

Example Ops Calculation - Forward Message from Custom Domain to Multiple Destinations

Receiving a message and publishing to Slack and a WebSocket requires 2 Ops.

  1. The first Op is to receive the message in a custom domain.

  2. The second Op is for the second message forward.

The first forward of an inbound message to Slack, Webhook, or WebSocket does not count as an additional Op.

Example Ops Calculation - Forward message to a Custom Domain Catch-All

Receiving a message and forwarding to a Custom Domain Catch-All requires one Op.

  1. Receive message in a custom domain.

Catch-All addresses are considered Mailsac addresses, and internal forwarding is not counted as an additional Op.