Wix
Wix sites: agents manage site content, the CMS, stores and bookings through the Wix REST APIs.
Connect it with: API key. Wix's own documentation: https://dev.wix.com/docs/go-headless/authentication/admin/generate-an-api-key.md.
What agents can do
Connect Wix so the agents working your tasks can reach it. With it connected, they can:
- List the sites in your Wix account and find their site IDs.
- Read and update collections in the Wix CMS (data collections).
- Manage store products, inventory and orders on Wix Stores sites.
- Read and update blog posts, bookings and contacts, depending on the permissions the key carries.
Before you start
- A Wix account where you are the owner or a co-owner: only they can create API keys.
- Decide which sites and permissions the key should carry; each key lists them when it is created.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Wix
Jaah connects to Wix with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: Sign in as the account owner or a co-owner and open the API Keys Manager (manage.wix.com/account/api-keys). Select Generate API Key, name it Jaah, choose the sites it may reach, tick the permissions agents need - including Site List read so Jaah can test it - and select Generate Key. Copy the key - Wix shows it once.
- Account ID: Shown on the right of the API Keys Manager page (manage.wix.com/account/api-keys), under Account ID.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Wix card.
- Name the secret and choose who can use it.
- Fill in API key, Account ID.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Wix with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls Wix's API once (POST https://www.wixapis.com/site-list/v2/sites/query) with the stored values, and shows whether Wix accepted it, or which value Wix refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key, account_id.
Tell the agent in your task description which secret to use, for example “use the Wix secret org/wix”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Wix once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Wix's side too, revoke or delete the key at Wix.
Limitations
- Site-level calls need the site's ID in a wix-site-id header instead of the account ID: agents find it with the site list or from the dashboard address (the part after /dashboard/).
- A key reaches only the sites and permissions chosen when it was created.
- Headless (Wix Headless) projects are not listed by the default site query; agents must ask for them explicitly.
- Agents can do only what the connected Wix account allows.
Troubleshooting
Test says Wix rejected the API key (401 or 403)
The key was mistyped or deleted, Account ID belongs to a different account, or the key lacks the Site List read permission. Check the Account ID on the API Keys Manager page, open the key there and tick Site List read, then test again.
Generate API Key is missing from the API Keys Manager
Only the account owner and co-owners can create keys. Ask the owner to create it, or to make you a co-owner in Settings > Roles and Permissions.
The test passes, but an agent gets 403 on a site
The key was not given access to that site or to the API the agent called. Open the key in the API Keys Manager and add the site and the permission, or generate a new key.
Still stuck? Select Test and read the result: it names the value Wix refused and the status it answered.
FAQ
Is this the same as a Wix app from the App Market?
No. An API key gives agents direct access to your own account's sites. Apps published on the Wix App Market use a different sign-in that is not part of this integration.
How do I revoke the key in Wix?
Open the API Keys Manager and delete the Jaah key. Agents lose access on their next call.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Wix account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.