Stibo Systems API
Stibo's STEP platform ships a semantic-versioned REST API V2 plus a Java Extension SDK, but the API reference lives inside each installation at [system]/sdk, not on a public portal. Basic auth is the REST default, and OIDC service accounts require a manual Service Portal ticket.
Frequently asked questions
Stibo Systems scores D on the API Report Card. Stibo's STEP platform ships a semantic-versioned REST API V2 plus a Java Extension SDK, but the API reference lives inside each installation at [system]/sdk, not on a public portal. Basic auth is the REST default, and OIDC service accounts require a manual Service Portal ticket.
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. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Stibo Systems is a Danish enterprise software vendor headquartered in Aarhus, Denmark, with US headquarters in Atlanta, Georgia.
Primary vertical: misc (cross-industry enterprise MDM/PIM). A global manufacturer or retailer deploys STEP as the enterprise system of record for product master data: SKUs, attributes, classification hierarchies, digital assets, supplier-provided data, regulatory and compliance attributes (REACH, RoHS, ingredient lists, country-of-origin, hazmat), and channel-specific variants.
High within enterprise MDM/PIM.
Founded: 1976 (Stibo Systems division); parent Stibo A/S founded 1794. HQ: Aarhus, Denmark (global); Atlanta, Georgia (US). Ownership: Privately held by Stibo Foundation (Stibo-Fonden). Employees: ~775 across 18 global offices. Customers: 550+ enterprise customers worldwide.
Stibo Systems was founded in 1976 as a division of Stibo A/S (founded 1794), making it one of the oldest continuously operating MDM/PIM vendors.
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.