The QuQi API
Two APIs behind one key: one that reads your finished work, and one that puts new work in. What each is for, and where to start.
There are two halves, and which one you want depends on which direction the work is travelling.
Both take the same key and answer in the same shape, so nothing is lost by using both. The platform half is deliberately read-only and is what the two connectors were built against; the Content half is the one you want if you are wiring up an automation.
Base URL
One base for both halves. The paths below are written relative to it.
The read-only endpoints sit under /platform; everything else is directly under /api/v1.
Putting work in
mode: publish — see Plan a post.
Reading work out
GET /status
Whether anything is connected, your brand name and domain, and this month’s article usage.
Status
GET /keywords
The article ideas scheduled in one month, with their search volume and difficulty.
Keywords
GET /articles/{id}
One article, with its full body, excerpt, cover image and meta fields.
One article
What one key can reach
A key belongs to you and reaches every website you are a member of, so one key serves all of them — you say which one you mean on each request. See Authentication.
There is a ceiling on how often you can call: 120 requests a minute and 2,000 an hour, counted against your key rather than your server, so one busy site never spends another site’s allowance. It is set high enough that normal use never reaches it — see Errors if you do. Errors come back as JSON, not as an HTML error page, so your code can read the reason instead of guessing from the status code alone.