Plans & limits

Every SendOps plan — Free, Team and Business — puts a number on each thing it measures: seats, templates, segments, active workflows, broadcasts per period, contacts and so on. When an action would take your organization past one of those numbers, the API refuses it with 402 plan_limit_exceeded and tells you which limit, where you stand, and what lifts it.

This page covers the contract an integration needs:

• the 402 problem and the full limit_type list;
• reading usage from GET /v1/account;
• the public plan catalogue at /plans.json;
• what POST /v1/import does with a bundle that does not fit.

Some things hold on every plan:

• One AWS account per organization.
• Website identity sites: none on Free, one on Team and Business.
• Custom image domains: none on Free, one on Team, five on Business. These are hard caps with no overage.
• Contacts are a ceiling. They are never priced and never billed as overage, on any plan.
• Overage exists only on monthly Business, on exactly eleven limits (see /plans.json). With overage switched on, those limits stop refusing and the usage above them is billed at the end of the period. Annual Business has no overage, so its limits are hard caps.

The 402 problem

A refusal is an RFC 7807 problem document with status 402 and code: plan_limit_exceeded. On top of the standard fields it carries the limit and your position against it:

{
  "type": "https://developers.sendops.dev/api-reference/errors/plan_limit_exceeded",
  "title": "Plan limit exceeded",
  "status": 402,
  "code": "plan_limit_exceeded",
  "detail": "plan limit reached: segments (3/3 on free plan)",
  "limit_type": "segments",
  "current": 3,
  "limit": 3,
  "plan_tier": "free",
  "upgrade_tier": "team",
  "upgrade_url": "https://app.sendops.dev/acme/billing?reason=segments&upgrade=team",
  "overage_available": false,
  "purchase_available": false,
  "request_id": "req_01HX7QY3..."
}

A 402 is terminal. Retrying the same request will not succeed until the plan changes, overage is switched on, or usage drops below the limit — deleting a segment, or a new period starting for the per-period limits. Surface upgrade_url to the person who can act on it.

Every limit_type

Seventeen are usage axes, the same names GET /v1/account reports in plan.axes. A count axis is how many exist now; a consumption axis is how many were used in the current period.

The rest are features a plan includes or does not. They have no number to count against, so current and limit are 0:

Treat an unknown limit_type like any other 402: show detail and upgrade_url.

Reading usage: GET /v1/account

GET /v1/account (scope api.account.view) carries the plan and where the organization stands on every axis — the same numbers as the dashboard’s Billing → Usage page. The snapshot is recomputed at most every 30 seconds, and the response itself is cached for 60 (Cache-Control: max-age=60).

{
  "plan": {
    "tier": "business",
    "retention_days": 365,
    "api_rate_limit_per_minute": null,
    "version": 2,
    "overage_enabled": true,
    "period": { "start": "2026-10-01T00:00:00Z", "end": "2026-11-01T00:00:00Z" },
    "axes": [
      { "axis": "segments",  "kind": "count",       "used": 7,  "limit": 500,     "enforced": true, "overage": { "unit_cents": 100, "per_units": 1 },    "ceiling": false },
      { "axis": "enrollments", "kind": "consumption", "used": 6, "limit": 2000000, "enforced": true, "overage": { "unit_cents": 25,  "per_units": 1000 }, "ceiling": false },
      { "axis": "contacts",  "kind": "count",       "used": 9,  "limit": 5000000, "enforced": true, "overage": null, "ceiling": true },
      { "axis": "sites",     "kind": "count",       "used": null, "limit": 1,     "enforced": true, "overage": null, "ceiling": false }
    ]
  }
}

The axes array above is trimmed. The real one has all seventeen axes, always in the same order.

version, overage_enabled, period and axes are present together or not at all.

The plan catalogue: /plans.json

GET https://api.sendops.dev/plans.json is the plan matrix itself: every tier’s price, every limit and every overage price. It is public: no credential, CORS enabled for sendops.dev, and cacheable for five minutes with an ETag (a conditional request answers 304). The pricing page on sendops.dev is generated from it, so it is the authority for the numbers.

{
  "version": 2,
  "currency": "usd",
  "plans": [
    {
      "tier": "free",
      "price_cents": 0,
      "annual_price_cents": null,
      "limits": {
        "seats": 1, "templates": 3, "retention_days": 7, "domains": 1, "aws_accounts": 1,
        "active_workflows": 1, "enrollments_per_period": 1000, "segments": 3,
        "broadcasts_per_period": 10, "contacts": 50000, "inbox_mints_per_period": 0,
        "inbox_live": 0, "inbound_domains": 0, "inbound_msgs_per_period": 0, "sites": 0,
        "cdn_domains": 0, "cdn_storage_bytes": 104857600, "verified_senders": 0,
        "audit_window_days": 0, "allow_presets": false, "allow_platform_profile": false,
        "allow_audit_log": false, "allow_inboxes": false
      },
      "overage": [],
      "support": "email"
    },
    {
      "tier": "team",
      "price_cents": 2900,
      "annual_price_cents": null,
      "limits": {
        "seats": 5, "templates": 50, "retention_days": 90, "domains": 10, "aws_accounts": 1,
        "active_workflows": 10, "enrollments_per_period": 100000, "segments": 50,
        "broadcasts_per_period": 200, "contacts": 500000, "inbox_mints_per_period": 3000,
        "inbox_live": 25, "inbound_domains": 1, "inbound_msgs_per_period": 10000, "sites": 1,
        "cdn_domains": 1, "cdn_storage_bytes": 5368709120, "verified_senders": 10,
        "audit_window_days": 90, "allow_presets": false, "allow_platform_profile": false,
        "allow_audit_log": true, "allow_inboxes": true
      },
      "overage": [
        { "axis": "seats", "unit_cents": 600, "per_units": 1 }
      ],
      "support": "email"
    },
    {
      "tier": "business",
      "price_cents": 14900,
      "annual_price_cents": 163900,
      "limits": {
        "seats": 25, "templates": 200, "retention_days": 365, "domains": 50, "aws_accounts": 1,
        "active_workflows": 100, "enrollments_per_period": 2000000, "segments": 500,
        "broadcasts_per_period": 2000, "contacts": 5000000, "inbox_mints_per_period": 30000,
        "inbox_live": 500, "inbound_domains": 10, "inbound_msgs_per_period": 100000, "sites": 1,
        "cdn_domains": 5, "cdn_storage_bytes": 53687091200, "verified_senders": 100,
        "audit_window_days": 365, "allow_presets": true, "allow_platform_profile": true,
        "allow_audit_log": true, "allow_inboxes": true
      },
      "overage": [
        { "axis": "seats",            "unit_cents": 500, "per_units": 1 },
        { "axis": "templates",        "unit_cents": 50,  "per_units": 1 },
        { "axis": "domains",          "unit_cents": 200, "per_units": 1 },
        { "axis": "active_workflows", "unit_cents": 200, "per_units": 1 },
        { "axis": "enrollments",      "unit_cents": 25,  "per_units": 1000 },
        { "axis": "segments",         "unit_cents": 100, "per_units": 1 },
        { "axis": "broadcasts",       "unit_cents": 50,  "per_units": 1 },
        { "axis": "inbox_mints",      "unit_cents": 500, "per_units": 1000 },
        { "axis": "inbound_domains",  "unit_cents": 500, "per_units": 1 },
        { "axis": "inbound_msgs",     "unit_cents": 100, "per_units": 1000 },
        { "axis": "cdn_storage",      "unit_cents": 50,  "per_units": 1073741824 }
      ],
      "support": "priority"
    }
  ]
}

The limit keys differ slightly from the axis names in limit_type and plan.axes: enrollments_per_period is the enrollments axis, broadcasts_per_period is broadcasts, inbox_mints_per_period is inbox_mints, inbound_msgs_per_period is inbound_msgs, and cdn_storage_bytes is cdn_storage.

Bundle imports: POST /v1/import

A bundle is one intended state, so a bundle that does not fit the plan fails whole. The import checks it before writing anything:

• segments — every segment the bundle creates, and every archived one it brings back, counts;
• templates — every template it creates counts;
• image bytes (cdn_storage) — the bytes of every new or changed image count.

Workflows are not checked: an import creates them as drafts, so the active_workflows cap applies when you activate one. Archiving with prune=true runs after the creates, so it does not make room for the same push.

A dry run (dry_run=true, the default) answers 200 with plan.applicable: false and a plan.plan_limit naming the cap:

{
  "dry_run": true,
  "plan": {
    "applicable": false,
    "prune": false,
    "totals": { "create": 2, "unchanged": 14 },
    "objects": [ ... ],
    "diagnostics": [],
    "plan_limit": {
      "axis": "segments",
      "current": 3,
      "limit": 3,
      "would_be": 5,
      "upgrade_url": "https://app.sendops.dev/acme/billing?reason=segments&upgrade=team"
    }
  },
  "applied": false,
  "objects": []
}

An apply (dry_run=false) is refused with the standard 402 problem, plus plan_limit (as above) and plan (the full dry run), so a pipeline can print the axis and the numbers without a second call. Nothing is written. would_add is set when the bundle adds more than one.

A bundle that already fails validation is not checked against the plan: its diagnostics come first. Business with overage on passes the metered axes.

The sendops-push Action prints the refusal as one line and fails the step:

Import refused: plan limit — segments 5/3. Upgrade: https://app.sendops.dev/acme/billing?reason=segments&upgrade=team

An organization on its original plan is not checked this way. Past its template allowance, the import answers 200 with the kinds before templates applied, applied: false, applied_until: "templates" and the refusal in error.