Alderstone developer documentation

Use this documentation to connect your ERP to Alderstone OrderBridge and Nudge. You deploy a small piece of middleware that implements our REST contract; Alderstone calls your middleware, and your middleware talks to your ERP.

Choose your app

Alderstone ships two apps, each with its own integration surface. Most integrations start with one app and add the other later. The authentication model and conventions are shared across both apps.

App	What the integration does	Start here
OrderBridge	Matches purchase order lines against your ERP catalogue, validates pricing, and creates draft sales orders	Overview · REST API
Nudge	Syncs debtors, invoices, and payments from your ERP, and pushes outbound invoices and payments back	Overview · REST API

How it fits together

Every integration follows the same three-step shape:

1. You expose HTTPS endpoints that implement the Alderstone REST contract. On Workato, Make, n8n, or your own infrastructure.
2. Alderstone calls your endpoints with JSON over POST, authenticated with an Alderstone-generated Bearer API key.
3. Your middleware translates each request into your ERP's native APIs and returns the contract response.

Your ERP credentials never leave your middleware, and Alderstone never connects to your ERP directly. Read How integration works for the full architecture, or Choose your integration path if you're deciding between the built-in native connectors and REST middleware.