content_tools:write
The content_tools:write scope allows you to generate supplementary data for content — SEO metadata, structured data schemas, social media snippets, page slugs, post tags, and search intent analysis. You can generate all tools at once or target a specific tool.
Endpoints
| Method | Path | Description |
|---|---|---|
POST | /public/content/{id}/content-tools | Generate all or selected content tools |
POST | /public/content/{id}/content-tools/{tool} | Generate a single content tool |
Available content tools
| Tool | Description |
|---|---|
seo-metadata | Page title, meta description, and keywords |
schemas | JSON-LD structured data (Article, Author, Organization, FAQ, etc.) |
social-snippets | Facebook, Twitter, Instagram, and Google Business snippets |
page-slugs | SEO-friendly URL slugs |
post-tags | Content categorization tags |
search-intent | Search intent analysis |
Generate content tools
content:read) to check when each component is ready, or subscribe to the content_tools.completed webhook event.
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string (UUID) | Yes | Article ID |
Request body (optional)
| Field | Type | Required | Description |
|---|---|---|---|
tools | array of strings | No | Specific tools to generate. If omitted, default tools are generated |
Example — Generate all tools
Response — 202 Accepted
Example — Generate only SEO metadata and schemas
Response — 202 Accepted
Status codes
| Code | Description |
|---|---|
202 | Content tool generation started |
400 | Validation error (invalid tool name, article ID missing) |
401 | Missing or invalid API key |
403 | API key does not have content_tools:write scope |
404 | Content not found or belongs to a different site |
500 | Internal server error |
Generate a single content tool
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string (UUID) | Yes | Article ID |
tool | string | Yes | The tool to generate (e.g. seo-metadata, schemas) |
Example
Response — 202 Accepted
Retrieving generated content tools
Once generated, retrieve the components using thecontent:read scope:
Status codes
| Code | Description |
|---|---|
202 | Content tool generation started |
400 | Invalid tool name or content ID missing |
401 | Missing or invalid API key |
403 | API key does not have content_tools:write scope |
404 | Content not found or belongs to a different site |
500 | Internal server error |
Error response — Missing scope
If your API key does not includecontent_tools:write, any request to these endpoints returns:

