Etsy Open API v3 vs MealMe API

Etsy Open API v3 82

Status page at www.etsystatus.com, now hosted on incident.io, with one component named Etsy and no API component, so the line is part met (15 of 20). Its feed lists three entries since 4 August 2026, site issues on 19 August, a 2.7.1 hotfix note on 1 October and site issues on 23 October (11:14 to 12:37 Eastern, no component marked affected). Each incident page has only generic status updates, names no scope and marks no component, and none touches the API on its own text, so the window is a clean record (30 of 30), as unscoped incidents with no component were read for openai-api. Limits per key are documented with example figures of 150 a second and 100,000 a day, while each app's own figures sit in the Developer Portal (12 of 15). 429 returns retry-after, and the docs ask for exponential backoff. The graded surface only reads (15 of 15). No SLA found (0 of 10). findAllListingsActive is marked General Release (10 of 10). Total 82.

MealMe API 19

Read with the hosted lines. No status page found on mealme.ai, the docs or llms.txt, and status.mealme.ai does not resolve (0). No readable incident history (5). No rate limit figures; each endpoint documents a 429 whose example message is 10 per 1 second(s)!, which the reference itself calls an example (0 of 15). The 429 is documented without Retry-After or backoff guidance, and Create Order has no idempotency key, only an order_id to update an existing order and a caller's customer_order_id to look up (4 of 15). No SLA found (0). The API is in production with versioned endpoints (10). Total 19.

Etsy Open API v3 45

The OpenAPI contract was last modified on 29 October 2026 and now lists 108 operations against 105 on 14 October, and listing and inventory webhooks were announced on 13 October (30 of 30). Two dated changes are established since 4 August 2026, the 13 October webhooks announcement and the 29 October contract change. The 14 October check counted fourteen announcements on GitHub Discussions between 13 July and 13 October without recording their dates, and GitHub refused us on 2 November, so a third in the window isn't established (0 of 20). Announcements and bug reports on GitHub Discussions and a developers@etsy.com address. Replies were not tested (10 of 15). No official SDK and no Etsy entry in the official MCP registry, searched 2 November 2026, which lists only third-party Etsy servers (0 of 15). The OpenAPI contract is regenerated and current, and there are no packages to check (5 of 10). Total 45.

MealMe API 6

Read as a closed service. The newest dated change is the release note of 6 May 2025 (Get Inventory v4), more than 180 days before 3 November 2026; the pricing and dashboard pages carry no date (0 of 30). No dated change in the last 90 days (0 of 20). A support address, release notes and no community channel (6 of 15). No official SDKs (0). No package to judge (0). Total 6.

Etsy Open API v3 62

API key in the form keystring:shared_secret, with self-service secret rotation, plus OAuth 2.0 with PKCE and 12 read or write scopes for private data. Public reads use one key with no scopes (24 of 30). The graded endpoints only read, and OAuth scopes split read from write (15 of 20). Listings return seller-written titles and descriptions, and no prompt-injection guidance was found (5 of 15). Rate-limit headers show usage per call, but no audit log was found (3 of 15). security.txt valid to May 2027 with a public Bugcrowd programme and hall of fame. No certification was checked (15 of 20). Total 62.

MealMe API 26

One API key per account in a custom Id-Token header, with no scopes, expiry, rotation or revocation documented (10 of 30). place_order defaults to false and charge_user can be turned off, so an agent can quote without buying, but there is no read-only key (8 of 20). Store descriptions, menus and support-chat messages are untrusted content with no guidance (3 of 15). Get Orders and a tracking webhook give order history; no per-call log for the operator is documented (5 of 15). No security.txt (400), disclosure policy, bug bounty or certification found; the Enterprise plan names a security review (0 of 20). Total 26.

Etsy Open API v3 58

Closed service. The API Terms of Use at www.etsy.com/legal/api answered with a bot check on 14 October and again on 2 November, so their clarity is unchecked (10 of 30). The privacy policy is on the same host behind the same check, so no data handling statement was read (0 of 30, unchecked). Dated deprecation notices, such as token_exchange on 30 July 2026 and inventory and shipping parameters on 29 July, per the 14 October check, but no written notice period (12 of 20). Subprocessors and data locations were not read (0 of 20, unchecked). Total 22.

MealMe API 47

Closed service. The API and SDK Terms of Use (18 June 2022) and MealMe Connect terms (4 April 2025) name MealMe, Inc. under Delaware law, but the API terms license use for personal, noncommercial purposes while the product is sold to businesses (15 of 30). The privacy policy of 1 January 2025 keeps data as long as needed, names no subprocessor and no DPA; the cookie policy names Google, Adobe, LinkedIn, Twitter and Facebook (10 of 30). Release notes record breaking changes with dates but there is no deprecation policy or notice period (6 of 20). Cookie providers named, no subprocessor list or data location (4 of 20). Total 35.

Etsy Open API v3 30

No x402, MPP or L402 (0 of 40). No fee for API access is stated anywhere in the reviewed documentation, and higher limits are requested by email, so there is no published price to score in full (10 of 20). The API is free with no card (20 of 20). A person must register the app in the Developer Portal, and use beyond one's own shop needs a Personal App review (0 of 20). Total 30.

MealMe API 20

No x402, MPP or L402 (0). $0.10 per successful call and $250 a month published without login (20). No free tier or trial; a card must be added before the key is created (0). Signup is a browser form with email, password and card (0). Total 20.

Etsy Open API v3 64

Pages of 1 to 100 listings, but no field selection, and each listing carries about 60 fields (12 of 25). Offset pagination with keyword, price range, taxonomy, location and buyer-country filters and four sort keys (20 of 20). Errors have documented HTTP codes and a text message, without codes in the body (13 of 20). Search is read-only and safe to retry. No idempotency keys were found for writes, which a shopping agent does not reach (12 of 20). One required header and sensible defaults, but no official SDK (7 of 15). Total 64.

MealMe API 69

Store search takes a projections list to choose response fields and a fetch_quotes switch that the docs say greatly increases response time, so responses can be sized (20 of 25). Page and next_page pagination, bounding-box, distance, rating, price, cuisine and open filters, maximum_miles defaults (18 of 20). Distinct status codes, 406 for a closed or out-of-range store, 420 for an unavailable product, 422 for checkout errors, each with a message naming the field or product (16 of 20). No idempotency key; the two-step order (202 quote, then place) and customer_order_id lookup are the safe-retry route (8 of 20). Only latitude and longitude required for search and sensible defaults, but no official SDK in any language, only an iframe embed (7 of 15). Total 69.