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.
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.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Quable is a Paris-headquartered SaaS Product Information Management (PIM) and Digital Asset Management (DAM) platform, founded in 2013 and acquired by Ibexa Group (the Norwegian DXP vendor) in 2024.
Primary vertical: misc (cross-industry PIM/DAM). Closest Supergood sub-vertical: Document Management Systems, Quable manages structured product records and media assets as the system-of-record for everything a brand publishes externally. A fashion brand stands up Quable as the central product data hub: merchandising teams enrich SKUs with attributes, sizing, materials, marketing copy, and translations; the DAM stores hero shots, lifestyle imagery, and 360 video; workflows route product records through review and approval; and the platform then syndicates the finished records via the REST/GraphQL API and webhooks out to Shopify / Magento / Salesforce Commerce Cloud, Amazon and Zalando marketplaces, SAP/Microsoft ERPs, retail partner portals, and the brand's own mobile app and print catalogs.
Medium in its niche, concentrated in Europe (especially France and Southern Europe).
Quable is the system-of-record for everything a brand publishes about its products.
Founded in 2013, Quable has consistently shipped as cloud-native multi-tenant SaaS rather than carrying legacy on-prem code.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.