Programmatic access for ingest and outbound events.
A typed API for pushing data into Northwind, and webhooks for reacting to changes inside it. In active development with design partners.
Programmatic access is in active development.
We are building a typed ingest API and outbound webhooks for early design partners. If your team has a workflow that would benefit, your input shapes the priority order; we are not shipping a generic API kit until it holds up against real use.
What we are building.
These are the API and webhook surfaces under active design. None are generally available yet; this page reflects what is in development, not what is shipped.
Ingest API
A typed endpoint for pushing structured records or files into a workspace, with the same schema discipline as a manual upload.
Outbound webhooks
Subscribe to changes inside a workspace (insight regenerated, dataset updated, audit event recorded) for downstream automation.
Scoped API keys
Keys scoped to a single workspace and a narrow set of operations; rotation and revocation are first-class.
Planned webhook signing
Outbound webhooks will be signed so the receiver can verify origin and reject replays.
Rate limits with backoff
Documented rate limits with backoff hints, so production callers can design against the contract instead of guessing.
Planned retry semantics
Idempotent ingest and at-least-once outbound delivery, so retries are safe and observable.
OpenAPI schema
The ingest API will publish an OpenAPI schema so teams can generate typed clients in their language of choice.
Delivery dashboard
A delivery view will surface recent webhook attempts, payloads, and response codes for debugging and observability.
We are working backwards from real use.
A generic CRUD API is easy. A useful API is one that holds up against the patterns teams actually run: nightly batch ingest, change-driven webhooks into a downstream system, signed payloads that better support the receiver`s security review. We are designing the surface against those patterns, not against a feature checklist.
If you have a concrete workflow that would benefit (a nightly job that lands records into Northwind, an automation that needs to react when an insight regenerates, a downstream system that wants signed webhook delivery), tell us. Priority is set by demand from teams that will actually use the result.
You will see a Live status here when the surface clears that bar, not before.
- Typed ingest API first; outbound webhooks second.
- Scoped, revocable API keys.
- Signed outbound webhooks with replay protection.
- Documented rate limits and retry semantics.
Tell us about the workflow you would automate.
If a missing API or webhook is blocking you, your input shapes the priority order. We are taking a short list of design partners now.