Today's trending search topics
/ai/trending-topicsReturns today's trending Google searches with the news headlines behind
them, for a region. Direct REST equivalent of the chat trending_topics
tool — useful for "what's trending that we could promote against?".
Requires the ai key scope and a linked service user. A GET under /ai/
still requires the ai scope.
Authorization
apiKey Issued to you when your integration is provisioned. Determines which catalogue resources are visible and which AI tools are available.
In: header
Query Parameters
Region code (e.g. US, GB, DE, ZA). Defaults to the catalogue's region.
Maximum number of trends to return.
1 <= value <= 2010Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/ai/trending-topics"{ "data": { "geo": "GB", "trends": [ { "term": "solar eclipse", "traffic": "200K+", "news": [ { "title": "string", "source": "string" } ] } ] }}{ "success": false, "status": "fail", "message": "API key is required", "error": { "code": "NO_API_KEY", "message": "API key is required" }}{ "success": false, "status": "fail", "message": "This API key does not have the 'write' scope", "error": { "code": "INSUFFICIENT_SCOPE", "message": "This API key does not have the 'write' scope" }}{ "success": false, "status": "fail", "message": "string", "error": { "message": "API key is required", "code": "NO_API_KEY" }}Fetch a generated artwork image GET
Streams an artwork image produced by `POST /ai/generate-artwork`. Unlike `GET /ai/images` (which browsers can call via a signed URL), artwork images sit outside the chat image tree, so this route is fetched with the `X-Api-Key` header and is scoped to the linked user's own artwork directory (`/filestore/artwork/{userId}/...`). Requires the `ai` key scope and a linked service user. Pass the `path` value returned by the generate-artwork response.
Generate cover / A+ / concept / mock-up artwork POST
Runs the internal two-stage artwork pipeline for a resource: a concept model writes master prompts from the book metadata and cover, then the image model renders the first concept. Direct REST equivalent of the in-app artwork generator. **Synchronous.** Both stages block, so this call can take a while (tens of seconds to minutes) — it is genuinely synchronous, not job-queued. The rendered image is returned in the `{path, url}` shape; artwork lives outside the chat image tree, so its `url` points at `GET /ai/artwork/images` and is fetched with the `X-Api-Key` header (not a signed URL). Requires the `ai` key scope, a linked service user, and edit access to the resource. `asset_type` and `aspect_ratio` are required; all other artwork options (style, provider, A+ / mock-up settings) are accepted and forwarded verbatim to the internal generator.