---
title: "Email send capacity for this shop"
method: GET
path: "/automations/email-capacity"
tags: ["Account & Billing"]
---

# Email send capacity for this shop

`GET /automations/email-capacity`

Today's email send capacity for a single shop — the email twin of `GET /automations/outreach-capacity` — so a consumer can pre-check before queuing email outreach and schedule the remainder for tomorrow.

`emails_sent_today` counts today's sends; `daily_limit` is the denominator the portal's daily-send bar uses, derived from the shop's effective plan entitlement.

`tier_limits` is that entitlement in full (`default` / `minimum` / `maximum`, Extra Limits grants applied). Note the enforced cap is **per email automation**, stored on the automation itself and clamped into this range when it is written — so a shop running several automations can exceed `daily_limit` in aggregate. A null field means the tier expresses no such limit, not zero.

Requires a single shop.

## Response `200`

Successful Response

- EmailCapacityResponse
  - `shop_id` integer, required
  - `emails_sent_today` integer, required — Emails sent by this shop today (server date).
  - `daily_limit` integer, required — The denominator the portal's daily-send bar shows.
  - `percent_used` number, required — emails_sent_today / daily_limit, as a percentage.
  - `tier_limits` EmailTierLimits, required — The shop tier's emails/day entitlement, Extra Limits grants applied.
    - `default` integer, nullable — Cap a newly created email automation gets.
    - `minimum` integer, nullable — Floor a cap is clamped up to.
    - `maximum` integer, nullable — Ceiling a cap is clamped down to; null when uncapped.

---

[API](https://skmtc.dev/reacherapp/apis/reacher-data-api.md) · [All operations](https://skmtc.dev/reacherapp/apis/reacher-data-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/reacherapp/reacher-data-api/revisions/3ea20a9f734b/schema)