Tattle · Rate Limits

Tattle Rate Limits

Tattle markets an open, REST-based, API-first platform but does not publish a public API reference, developer portal, or rate-limiting documentation. No per-second, per-minute, per-key, or per-IP request limits, throttling behavior, or response headers are documented publicly. API access is included as a feature across all subscription tiers and is provisioned per location; custom and partner integrations are coordinated through Tattle's integrations team (customersuccess@gettattle.com), which is where any applicable request limits would be communicated. The entries below are descriptive placeholders pending access to partner documentation and should not be treated as verified numeric limits.

Tattle Rate Limits is the machine-readable rate-limit profile for Tattle on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring varies.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Rate Limiting, Restaurant, Guest Feedback, and Integrations.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-03.
Written by API Evangelist on 2026-06-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingRestaurantGuest FeedbackIntegrations

Limits

API request rate (open / partner API) account
varies
Not published — coordinate limits via Tattle integrations team
No public rate-limit documentation exists. Tattle describes "Modern REST APIs with comprehensive documentation for custom integrations" but the reference is gated behind partner onboarding.
Location entitlement (subscription scope) account
varies
Per-location subscription; see plans/tattle-plans-pricing.yml
Platform access is scoped and billed per location rather than by API request volume. This is a commercial entitlement, not a request-rate throttle.

Policies

Partner-coordinated limits
Any request-rate or concurrency limits are communicated during partner integration onboarding rather than published in a public developer portal.
Recommended backoff
With no documented limits, integrators should apply conservative exponential backoff on 429/5xx responses and confirm thresholds with the Tattle integrations team before high-volume use.

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/tattle-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.