Skip to main content
Once your Shops API integration is built, you can apply to have your platform listed directly in Base.com’s official integration directory. Until that approval is complete, your clients can still connect via the generic “Other shop” option — but a dedicated listing makes onboarding smoother and builds trust with end users.
1

Build the integration

Implement your integration according to the Shops API documentation, which includes a built-in tester to verify your responses. An example integration file is available as a practical starting point — you can adapt it to your platform’s language and data model.
2

Set up a test Base account

Create an account on the production version of Base at baselinker.com/en-GB/register/. Use this account to connect your integration file and run end-to-end tests. If the default trial period isn’t long enough to complete integration and testing, contact Base and they can extend it for you.
3

Until you're listed — use 'Other shop'

While your integration is pending approval, your clients can already connect your platform by selecting the generic “Other shop” option in the Base panel and entering your integration file URL and the bl_pass key. This is a fully functional connection — it just won’t have your logo or a dedicated entry in the list yet.
4

Send what's needed for approval

Once your integration is built and tested, send the following four items to Base for review:
  1. A logo — a link to the image file is fine. It will be displayed next to your integration name in the list when a user adds it.
  2. End-user setup instructions — the text shown in the left-hand panel when a user configures your integration. This must cover everything a user needs for a successful setup:
    • exactly where to go and what to click in your platform
    • what to enable or configure
    • what to copy and where to paste it
    • where to find any required keys or passwords
    • who to contact if something doesn’t work
    • what the integration supports (order sync, product sync, etc.)
  3. A test instance of your store with access credentials for Base — so their team can independently verify the integration before publishing.
  4. The login email of your Base account — the initial rollout is limited to specific accounts for final testing before the integration is made globally visible.
Prepare all four items together before submitting — having everything ready at once significantly speeds up the approval process.