---
title: "Resolved plan entitlements for your shops"
method: GET
path: "/account/limits"
tags: ["Account & Billing"]
---

# Resolved plan entitlements for your shops

`GET /account/limits`

The per-category limits actually in force for each of your shops — CRM, automations and email automations — with any support-granted Extra Limits already folded in. This is the resolved number, not the advertised plan number, so a consumer can size a batch before it gets clamped.

`limits` is category → limit type → value; the types are typically `default` (what a new automation is created with), `minimum` and `maximum` (the enforced ceiling). A category missing for a tier means the plan expresses no opinion, not a limit of zero.

Covers every shop in `x-shop-id` — send `all` for the whole account.

## Response `200`

Successful Response

- AccountLimitsResponse
  - `data` AccountShopLimits[], required
    - `shop_id` integer, required
    - `shop_name` string, nullable
    - `plan` string, nullable — The shop's plan tier the limits were resolved against.
    - `limits` object — category → limit type → effective value, e.g. `{"crm": {"default": 5000, "maximum": 20000}}`.

---

[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/5eefff009b5b/schema)