BaseLinker
106 operations0 webhooks
E-commerce integration hub for orders, inventory, and multichannel marketplace management.
Supported operations
- Get Connect Integration ContractorsRead-only
Tool to retrieve a list of contractors connected to a selected Base Connect integration. Use when you need to discover available contractors for a specific integration before performing contractor-specific operations.
- Get Connect IntegrationsRead-only
Tool to retrieve a list of all Base Connect integrations on this account. Returns both integrations created on the account and integrations to which the account has connected.
FAQ
Install corsair and @corsair-dev/baselinker, add the BaseLinker plugin, and connect with an API key. Then call methods like corsair.baselinker.api.connect.getConnectIntegrationContractors() from your app. Corsair syncs data per tenant.
Yes. BaseLinker requires an API key from your BaseLinker account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit BaseLinker, GitHub, Notion, Stripe, and the rest. Trigger BaseLinker from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for e-commerce integration hub for orders, inventory, and multichannel marketplace management. Common builds include sync jobs, admin tooling, and agents that call BaseLinker APIs from your backend. Local DB entities let you query synced BaseLinker records without hitting the API on every read.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per BaseLinker API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/baselinker in the open repo. When BaseLinker ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your BaseLinker data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store BaseLinker data on your behalf.