MarginEdge · Rate Limits

Marginedge Rate Limits

The MarginEdge Public API is served through an AWS API Gateway fronting a custom authorizer, with access scoped by an API key (the x-api-key header) to the restaurants the caller is authorized to access. MarginEdge does not publish explicit numeric request-rate or quota values in its developer portal, so the per-second and per-day limits below are documented as references to the portal rather than fixed numbers; treat them as gateway-enforced and subject to standard AWS API Gateway throttling. The API is read-only (GET only) and returns large collections through opaque cursor pagination using the nextPage parameter and response field, which is the primary control on response volume. Limits apply per API key.

Marginedge Rate Limits is the machine-readable rate-limit profile for MarginEdge on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests_per_second and varies.

The profile also includes 4 backoff/retry policies defined and response codes documented for unauthorized, notFound, badRequest, and serverError.

Tagged areas include Rate Limiting, Restaurant, Invoices, and Products.

2 Limits
Rate LimitingRestaurantInvoicesProducts

Limits

Public API requests (per API key) key
requests_per_second
not publicly published; enforced by AWS API Gateway throttling — see developer.marginedge.com
Access is gated by the x-api-key header through a custom AWS API Gateway authorizer. Specific per-second throttle and burst values are not documented in the public developer portal.
Collection page size key
varies
server-determined page size; iterate with the nextPage cursor to retrieve all results
List endpoints (orders, products, vendors, categories, vendor items) return a bounded page plus a nextPage cursor. Continue requesting with nextPage until it is absent to page through the full result set.

Policies

API key scoping
Each API key is scoped to the specific MarginEdge restaurants the integration is authorized to access; requests for unauthorized restaurants return 403.
Cursor pagination
List responses include an opaque nextPage value. Pass it back as the nextPage query parameter to fetch the next page; stop when nextPage is no longer returned.
Read-only access
The Public API only supports data retrieval (GET); it cannot create or update data in MarginEdge, which removes write-rate concerns entirely.
Exponential backoff on 5xx / throttling
Because exact throttle numbers are not published, clients should implement exponential backoff and retry on 429/503-style throttling and 500 responses, and cache restaurant-unit lookups to minimize request volume.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/marginedge-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.