These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Partner needs data
- Bespoke endpoint added
- Docs written by hand
- Field change breaks partners
With SynaptaGrid
- Record type published
- Description generated from it
- Partner key scoped and limited
- Old version stays live
The situation
The contract is whatever the last integration needed. Documentation is written by hand and is stale by the next release, one credential is shared across partners because scoping it was never built, and taking a field away means calling everyone first.
How it is approached
Records live in one place, each record type and version with its own REST URL space, described by an API description the service publishes plus a schema and presentation description per published version. Partners get their own keys, scoped to particular record types, with their own rate limits, rotated or revoked without touching anyone else, and key holders are always served the published version rather than a working draft. Changes are pushed out as signed events with retries, a delivery log, and dead-lettering that can be redriven.
What changes
A new partner integrates against a description generated from the model rather than one written about it. Removing a field becomes a versioned change, with the previous version still active while partners move off it.