The public API
This is the API your own website or application talks to. It serves catalogues, lots, images and live bid state, and it accepts bids. If you want to build your auction front end yourself — in your own framework, on your own domain, with your own design system — this is the surface you build against, and the platform becomes infrastructure you never have to show anyone.
It is the same API our own front ends and our native apps use. There is no privileged internal interface that we keep for ourselves.
The integration API
This one connects the platform to the systems around it. It is used to move data in and out in bulk rather than to serve a browsing bidder.
| Direction | Typical use |
|---|---|
| Lots in | Import lots automatically from your own back office, stock system or consignor feed, rather than keying them in. |
| Invoices out | Push buyer and consignor invoices into your accounting system. Customers run this into Exact. |
| Results out | Export bid results and settlement data to finance or reporting systems. |
| Identity | Single sign-on, so bidders and staff authenticate against one identity across every system. |
The shape of it
Together the two APIs expose roughly ninety endpoints across twenty controllers. The bidder-facing surface is documented endpoint by endpoint in the API reference on this site, generated from the API’s own specification so it cannot drift from what is deployed — and there is Swagger for developers who prefer to read it live. A public read surface needs no authentication at all, for showing approved lots on a partner site or a marketing page without handing out credentials.
What this is actually for
Most auction platforms are a closed box: you get their website, their admin screens, and an export button. That is fine until your business needs something the box does not do.
Two documented APIs mean the platform is a component in your architecture rather than a replacement for it. You keep your CRM, your ERP, your accounting, your website — and the auction becomes a service they all talk to.
What this covers in full
The full feature list →Integration on the full list →
- Two APIs — a modern REST API and a legacy system-to-system APIBuild your own front end, or connect your existing systems, without waiting for us to build it for you.
- Around ninety endpoints across twenty controllersAlmost everything the platform does can be driven from your own software.
- Swagger documentationYour developer can read the API and start building the same day.
- Public read API needing no authenticationShow your live lots on a partner site or a marketing page without handing out credentials.
- OAuth2.0 with OpenID ConnectStandard, current authentication that your security team will recognise and approve.
- Single sign-on across every site and appOne login for the website, the app and the back office.
- Roles — administrator, bidder, guestSystems connecting to you get only the access they need.
- Outbound webhooks with per-endpoint secretsWhen a lot sells or a bidder registers, we notify your CRM or ERP immediately — no polling, signed so you know it is really us.
- Event system feeding bidder profiles into a CRMBuild a picture of what each bidder is interested in from what they actually do, and act on it in your CRM.
- Generic link registry across entitiesConnect anything to anything — a lot to a document, a member to a case — without a schema change.
- Lots imported from an existing back officeKeep using the system you already have for stock, and push lots into the auction from it.
- Invoices exported to accounting systemsSales and settlements land in Exact or your accounting package without rekeying.
- Listings pushed to Invaluable and Lot-tissimo, bids tracked backReach the marketplaces' audience while running your own platform, and see which channel produced each bid.
- Stripe, Mollie and QuickPayTake card, iDEAL and local payment methods, or plug in the provider you already use.
- Scheduled background jobsImports, exports and reminders run overnight on their own.