What we do
Tools
Industries
Department
How we workLet's talk →
Home/Wix/Wix API
Wix API

Wix API: Which Credential, Which Code Path, and What It Can Reach

Wix gives you three ways in: an API key for your own server talking to your own site, an OAuth app for something installed on sites you don't own, and Velo code that runs inside the site with no credentials at all. Most wasted days on a Wix integration come from starting with the wrong one. Pick yours below, then make the first call.

Which Wix API route is yours

Your server syncing your own Wix site with a CRM, ERP or warehouse: an API key. Long-lived, scoped, sent with every REST call along with the site ID.

An app other Wix sites will install: an OAuth app. API keys aren't available to third-party apps, so the app gets tokens per installation instead.

Code that runs on the site itself, reacting to a form or an order: Velo. Wix authenticates it for you, and it can call outside services or expose its own endpoints.

Match the Wix credential to what you are building

What you are building Use this Watch for
A nightly or event-driven sync between your Wix site and another system you run API key with only the scopes the sync needs, restricted to that one site The key has to come from the Wix account that owns the site. A key from a collaborator's account fails on site-level calls.
A tool for several client sites in one agency or enterprise account One API key with site access limited to those sites, called with each site ID in turn Every request names its target. Send the site ID for site work or the account ID for account work, never both.
A public or private app other businesses install from the Wix App Market OAuth app using the client_credentials grant per app instance App tokens last four hours and come with no refresh token. Your backend mints a new one from the app ID, secret and instance ID.
A custom front end (headless) that reads Wix Stores or Bookings OAuth visitor and member tokens through the JavaScript SDK Admin actions don't belong in the browser. Run them server side with the headless client secret or an API key.
Logic triggered inside the site: a form submit, a new order, a member signup Velo backend code, which calls Wix APIs with host auth Velo can call your other systems directly, so you may not need an outside server at all for small jobs.

Your first Wix REST call with an API key

This is the server-to-server route, the one most custom integrations for a single business use.

  1. 1

    Generate the key as the account owner

    Only an account owner or co-owner can create one, in the Wix dashboard. Give it the narrowest set of scopes the job needs, for example read access to orders and write access to contacts, and nothing else.

    Watch for: if you're a contractor, have the client generate the key from their own account. Keys from your account won't reach their site.

  2. 2

    Limit the site access

    A key can reach every site in the account or only the ones you pick. Pick. A call to a site outside the key's access is rejected whatever its scopes say.

  3. 3

    Find the site ID

    Site-level endpoints need it on every request. Account-level endpoints (managing sites, for instance) take the account ID instead.

  4. 4

    Send the request

    Put the key in the Authorization header and the site ID in wix-site-id. With the JavaScript SDK, ApiKeyStrategy does the same thing for you.

    Watch for: a 401 or 403 here is almost always the wrong account's key, a missing scope, or both ID headers sent at once.

  5. 5

    Keep it on the server

    The key stays valid until someone revokes or rotates it. Store it in an environment variable, keep it out of front-end code and version control, and use a separate key for testing.

Wix API errors that are really auth mistakes

The key works on one site and not another

How you'll know: Calls succeed on a test site and fail on the client's live site with a permissions error.

Fix: The live site sits in a different Wix account, or outside the key's site access. Generate the key from the owning account and add the site to its access list.

An app that goes quiet after a few hours

How you'll know: Your OAuth app works after install, then every call returns 401 later the same day.

Fix: App tokens expire after four hours and there's no refresh token for them. Request a fresh one with the client_credentials grant when the old one runs out, or before every batch.

An API key inside a Velo page or a browser script

How you'll know: The key appears in page code anyone can read.

Fix: Revoke it. Code on the site already has host auth, and admin calls that need more go in Velo backend code, not the page.

Trying to use an API key in a third-party app

How you'll know: You're building an app for the App Market and the key route seems simpler.

Fix: Wix doesn't offer API keys to third-party apps. Build on OAuth from the start so you don't rewrite authentication before launch.

App Market connector, Zapier, or your own code against the Wix API

Before writing anything, check the App Market. Connector apps exist for HubSpot, Mailchimp and a lot of popular CRMs, and they handle the plain case: a new Wix contact becomes a CRM contact, a form submission starts an email sequence. If that's all you need, don't build it.

Zapier and Make (the tool once called Integromat) cover the next step up: a few low-volume triggers with little branching. They get fragile once a sync needs conditions, such as routing large orders to a different sales rep, tagging customers by what they bought, or holding a record until a manager approves it.

That's where code against the Wix REST API or Velo takes over, usually for an ERP or a CRM with no App Market listing, or when the CRM needs order history and custom fields rather than a name and email. Velo code can call outside services directly, and its HTTP functions let another system push data into the site.

Questions people ask

Does Wix have an API?

Yes. Wix publishes REST APIs and a JavaScript SDK covering stores, contacts, bookings, members and more, plus Velo for code that runs inside the site. An API key, an OAuth app or Velo's built-in auth gets you in, depending on where your code runs.

Should I use a Wix API key or an OAuth app?

Use an API key when your own server talks to your own site or account. Use an OAuth app when you're building something other Wix sites will install, because API keys aren't available to third-party apps.

Does Wix integrate with HubSpot?

Yes, through an App Market app that syncs contacts and some form data. Deal stages, custom properties and conditional routing usually need custom work against both the Wix and HubSpot APIs.

Can I connect Wix to a CRM that has no App Market app?

Yes, through the Wix REST API or Velo code calling the CRM's own API. That's also the route when a connector exists but only copies names and emails, and you need order history, custom fields or approval steps attached.

Does Wix work with Zapier or Make?

Yes. Wix has a Zapier integration, and Make (formerly Integromat) covers similar ground. Both suit simple triggers such as a form submission posting to Slack. Syncs with branching logic or real volume are better as API code.

Can Wix and Shopify run side by side on one catalog?

There's no official connector between the two, since they compete. Keeping one catalog across both takes a custom sync through each platform's API, and it's usually a stage in a migration rather than a permanent setup.

Does Wix have a built-in CRM?

Wix has a Contacts tool with customer records, activity and Workflows boards for moving leads through stages, which covers simple needs. It isn't a full sales CRM with forecasting and sales reporting, so businesses with a real sales team usually run a separate CRM and connect it to the site through the API.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.