QuiboDocs
HomeSign in

getting started

Connect Wix

API key + site ID. We publish through Wix Blog draft posts.

Quibo connects to Wix through the official Wix REST API (Blog and Media Manager). You create an API key in your Wix account, paste it into Quibo together with the site ID, and we publish each article as a Wix Blog post: created as a draft, then published, so it shows up in your blog feed exactly like a post written in the Wix editor.

What you'll need

  • A Wix site with the Wix Blog app installed (Dashboard, Blog).
  • An API key created in the Wix API Keys Manager with the Blog and Site Media permissions for that site.
  • The site ID of the Wix site (the GUID in the dashboard URL).
  • Optional: the member ID of the author the posts should belong to. Quibo detects the site owner automatically, so most sites can skip this.

Generate the API key

API keys are created at account level and then scoped to one or more sites. Only the account owner or a co-owner can create them, and a key only works for sites owned by that account.

  1. Sign in to Wix and open the API Keys Manager (account menu, API Keys).
  2. Click Generate API Key.
  3. Name it Quibo.
  4. Under permissions, open the site permissions and check Blog (Manage Blog) and Site Media (Manage Media Manager). Optional: Members (Read Members) lets Quibo show member names instead of member IDs in the author picker.
  5. Under site access, choose the specific site you are connecting rather than all sites.
  6. Click Generate Key and copy it right away. Wix shows the key only once; if you lose it, generate a new one and revoke the old one.

Get the site ID

  1. Open the site's dashboard at manage.wix.com.
  2. Look at the browser URL: https://manage.wix.com/dashboard/<site-id>/home. The site ID is the GUID between dashboard/ and the next slash, for example 3ecba886-4267-11ee-be56-0242ac120002.

Optional: author member ID

Every Wix Blog post belongs to a site member. When you connect, Quibo looks for the owner: the member who wrote most of your existing posts, or the oldest member when the blog is still empty and the key can list members. You can change the author later from the site's brand profile (Default author), which lists the members Quibo found.

If you want a specific member from the start, paste their member ID (a GUID) in the Wix credentials. It replaces the automatic detection. At publish time the order is: the Default author saved in the brand profile, then the member ID in the credentials, then the detected owner.

Plug it into Quibo

From Sites, then Connect a site pick Wix and fill in:

  • Site name (e.g. Acme Blog)
  • Site URL, your published Wix site URL (custom domain or username.wixsite.com/site). Used to extract your brand voice.
  • Output language
  • API key
  • Site ID
  • Author member ID (optional)

Click Connect site. Quibo verifies the key and the site ID against Wix before saving anything: if the check fails, nothing is stored and the error is shown in the wizard. Test connection on the site page stays available to re-check them later.

Auto-discovery

When you connect, Quibo reads:

  • Categories with GET /blog/v3/categories, listed in the site schema for reference (Quibo does not assign categories yet).
  • Members with GET /members/v1/members (only when the key has the Members permission) and the owners of your existing posts with GET /blog/v3/posts. Together they feed the Default author dropdown, with the detected owner first. Pick one and click Save brand profile.

Discovery runs again daily, or on demand with Re-crawl brand on the site page.

What we publish

For each article Quibo:

  1. Imports the cover image and any inline image into your Media Manager with POST /site-media/v1/files/import. Wix downloads the files from their URL, so they land in your media library like an upload.
  2. Creates a draft post with POST /blog/v3/draft-posts: title, excerpt (from the meta description), language, hero image, SEO slug, the owner member, the body as Ricos rich content, and the SEO settings (title tag, meta description, og:title and og:description when the article has a social title and description, and the Article JSON-LD as a <script type="application/ld+json"> tag). If Wix rejects the SEO settings, the draft is retried once without them.
  3. Publishes the draft with POST /blog/v3/draft-posts/{id}/publish and reads the public URL of the post back from GET /blog/v3/posts/{id}.

A content refresh updates the same draft with PATCH /blog/v3/draft-posts/{id} and publishes it again, so the live post is replaced in place at the same URL. The owner is not changed on a refresh.

Rich content conversion

Wix stores post bodies as Ricos JSON, not HTML. Quibo converts the article into Ricos nodes: paragraphs, headings, bold, italic, underline, strikethrough, links, bullet and numbered lists (nested lists included), quotes, code blocks, dividers and images. Inline code has no Ricos equivalent and is shown in a monospace font. The FAQ section becomes a heading followed by each question in bold and its answer, so readers see it in the post.

JSON-LD cannot be embedded in a Ricos document, so the article's schema goes into the post's SEO settings instead (see above).

Images

Because Wix imports images from a URL, Quibo cannot add the AI transparency marking (XMP metadata) to the files it sends to Wix. The marking is applied on connectors where Quibo uploads the image bytes itself.

Test the connection

In Sites, then your site click Test connection: we call GET /blog/v3/categories with your key and site ID. A 401 means the key is wrong or revoked, a 403 means the key lacks the Blog permission or access to this site, a 404 or 400 usually means the site ID is wrong.

Security

  • The API key is encrypted at rest.
  • It is never returned to the browser, never logged, never sent to a third party.
  • Revoke it any time from the API Keys Manager. To connect with a new key, open the site page in Quibo, use Update credentials in the Credentials card, and the new values are verified against your CMS before they replace the old ones.