The API Report CardAPI Index
Quable

Quable API

Document Management Systems · quable.com

A publicly documented REST API (v5, plus supported legacy v4) and a newer GraphQL endpoint span the PIM/DAM surface, with webhooks and Postman collections. Auth is a long-lived per-instance Bearer token with no OAuth flow, and a hard 6,000 requests per 10 minutes limit produces 429s.

Last verified: July 2026Retail & Ecommerce
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA public REST API (v5, with legacy v4 still supported) plus a newer GraphQL endpoint, documented at developers.quable.com.
AccessPOORTokens are issued per customer PIM instance, and a hard 6,000 requests per 10 minutes limit surfaces 429s on bulk syncs.
CoverageGOODREST v5 offers full CRUD over products, variants, classifications, assets, catalogs, workflows, and configuration, with webhooks.
AuthPOORLong-lived per-instance Bearer tokens; no OAuth or OIDC client-credentials flow is documented.
Docs & DXGOODPublic docs at developers.quable.com with Postman collections, GitHub recipes, and an embedded UI SDK.
StabilityMIXEDLegacy v4 stays supported alongside v5; webhooks retry three times before a notification is marked errored.
MORE FROM THE REPORT CARD
Supergood: Quable has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Quable scores D+ on the API Report Card. A publicly documented REST API (v5, plus supported legacy v4) and a newer GraphQL endpoint span the PIM/DAM surface, with webhooks and Postman collections. Auth is a long-lived per-instance Bearer token with no OAuth flow, and a hard 6,000 requests per 10 minutes limit produces 429s.

Tried to integrate with Quable?