Commerce & Payments · Integration
BaseLinker
Add BaseLinker to your product for your customers, and give your AI agents governed access to it.
BaseLinker has an unusual shape for a modern API: every operation goes to one URL, POST https://api.baselinker.com/connector.php, with the operation name in a `method` form field and a JSON string in a `parameters` field, authenticated by an X-BLToken header. That means getOrders, addOrder, setOrderStatus, getInventoryProducts and createPackage all share a route, so per-endpoint routing and permissions have to be reconstructed from the method name. Errors do not use HTTP status codes: a bad token still returns HTTP 200 with a body of {"status":"ERROR","error_code":"ERROR_BAD_TOKEN"}, so any client that only checks the status line will silently treat failures as success. getOrders returns at most 100 orders per call and is walked forward with date_confirmed_from rather than an offset, so incremental sync means tracking the last confirmation timestamp and tolerating repeats. Orders arrive from many marketplaces at once, so the same buyer appears under different marketplace identifiers and needs deduplication on your side. fastn manages each customer's token, handles the single-endpoint call convention and keeps the connection healthy over time.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own BaseLinker account so their marketplace orders flow into your app without CSV exports
Push fulfilment updates back by calling setOrderStatus when your system ships an order
Sync inventory levels and product data from the BaseLinker catalogue into your own product records
Create courier parcels and retrieve labels for orders a customer dispatches through your interface
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which orders confirmed today are still unpaid or unshipped across a tenant's marketplaces
Have an agent set the status of a specific order and record why, with the write audited per tenant
Let an agent reconcile stock counts between a customer's warehouse export and the BaseLinker inventory
Example prompt
Which Allegro orders from this week have not been dispatched yet?
Set up BaseLinker in 4 steps
- 01Enable the BaseLinker connector from your fastn dashboard.
- 02Have each customer authorise their own BaseLinker account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the BaseLinker integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BaseLinker integration without building it. Your customers connect their own BaseLinker account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a BaseLinker update is not your on-call problem.
- One integration serves your product and your agents. The same governed BaseLinker connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to BaseLinker, across other categories.
NetSuite
Notion
Box
DocusignBaseLinker integration FAQ
How do I add a BaseLinker integration to my product?
Enable the BaseLinker connector in your fastn dashboard, then let each customer authenticate their own BaseLinker account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BaseLinker client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BaseLinker account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BaseLinker account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this BaseLinker integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which orders confirmed today are still unpaid or unshipped across a tenant's marketplaces
Who maintains the BaseLinker integration?
fastn does. When BaseLinker changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the BaseLinker integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the BaseLinker integration?
A common starting point: let a customer connect their own BaseLinker account so their marketplace orders flow into your app without CSV exports. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the BaseLinker integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BaseLinker does not change your per-connector cost. You can start free with 3 connected accounts.
Add BaseLinker to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.