The usual failure when an agent writes against a platform API is inventing a field name that sounds right. Being able to fetch the actual schema, then make the call, in the same conversation, removes the guess entirely — and when it does fail you can re-read the schema rather than retrying with a different invention. That pairing is more valuable than either half alone, and it is why documentation endpoints that cannot act are only half a tool.
Wix's endpoint is two things at once: a documentation surface for people building on Wix, and a live one for acting on the sites in your account.
- Searching their REST, SDK, design system, app-building and headless documentation
- Reading a full article, or an API schema
- Listing the sites in your account
- Calling a site's API, and site-level management operations
OAuth sign-in for interactive use; an API key with an account-id header for automation platforms. Clients without remote support use their published proxy.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen