Developers
One integration surface, instead of one per provider.
A POS partner connects once, to OneAggrgtr's partner API. OneAggrgtr owns the connections onward to the marketplaces and delivery providers it supports.
- Partner API (v1)
- Built; not publicly published
- Developer Portal
- Available to invited partners
- Partner sandbox
- By invitation; simulated orders
- Production connections
- None yet
The partner API (v1) is built and documented, and is not publicly published. Its documentation and a hosted sandbox are available only to invited POS partners. The sandbox's orders are simulated, and no marketplace or delivery provider is connected to it. There is no self-service sign-up and no production access; ask us about access.
Ask about sandbox accessWhat it covers
What a POS does through the partner API.
- Read orders from one feed, in one format.
- Accept or reject an order, and mark a pickup ready and picked up. Each action carries an idempotency key, so repeating it with the same key has one effect.
- Send the catalog: categories and products, with your own references kept beside them.
- Send stock levels for each store.
Integration direction
Partners connect in. OneAggrgtr connects out.
Every partner-specific model stays at the edge and every provider-specific model stays behind an adapter, with one canonical model between them. Select a step.
Step 1 · POS partner
The partner calls OneAggrgtr's API with a partner key bound to one store. OneAggrgtr never calls into the POS.
The same API is meant to serve every POS partner, not only the first. Whether a given partner can connect this way depends on what that partner confirms it can do.
Building a POS integration?
Tell us how your system integrates with others today. If it fits, we will set up sandbox access, and we will be exact about what connecting would take.