canonical: https://jentic.com/apis/docswrite.com/docswrite

# Docswrite Public API

The Docswrite API publishes Google Docs and Markdown or HTML content to WordPress and other CMS platforms. It exports a Google Doc to a connected site, publishes content to one or more CMS connections, and lists an organization's connections and posts. Job and post status operations report publishing progress, and a re-publish operation pushes edits to an existing post.

## For AI agents

Publish Google Docs and Markdown or HTML to WordPress and other CMS connections with Docswrite, list connections and posts, and check publishing job status.

## Scope

Does not handle website hosting, SEO analysis, or design and theming. Use for publishing documents and content to WordPress and other CMS platforms only.

## Capabilities

- Publish a Google Doc to a connected WordPress site
- Publish Markdown or HTML content to one or more CMS connections
- List the organization's CMS connections and published posts
- Check the status of a publishing job or a published post
- Re-publish a post with updated content
- Move a published Google Doc into the connection's Drive folder

## Use cases

### Agent Content Publishing

An AI agent connected through Jentic takes a finished Google Doc or Markdown draft and publishes it to the right WordPress or CMS connection, then checks the job status. The Docswrite API exposes the export, posts, and status operations the agent needs, and Jentic injects the credential at call time.

Example prompt: Publish a Markdown draft to a named CMS connection and poll the post status until it is live

### Multi-Site Distribution

Teams publishing to several sites push one piece of content to multiple connections at once. The Docswrite API publishes content to one or more CMS connections and lists the organization's connections so an agent can target the right ones.

Example prompt: List the organization's connections and publish an HTML article to the three connections tagged for distribution

### Edit and Re-Publish

After an edit, teams push changes to the already-published post rather than creating a duplicate. The Docswrite API re-publishes a post with the updated content and reports the new status, keeping the live version in sync.

Example prompt: Re-publish an existing post with corrected content and confirm the updated post status

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/export` | Publish a Google Doc to WordPress |
| POST | `/api/posts` | Publish a Google Doc to any CMS connection |
| POST | `/api/v1/posts` | Publish Markdown or HTML to one or more connections |
| GET | `/api/v1/posts/{id}` | Get the status of a publish or post |
| PATCH | `/api/v1/posts/{id}` | Re-publish a post with changes |
| GET | `/api/connections` | List the organization's connections |
| GET | `/api/posts` | List the organization's posts across connections |
| POST | `/api/job/status` | Get publishing job status |

## Key resources

- **Posts** — Publish Google Docs or Markdown and HTML content, list posts, check status, and re-publish
- **Connections** — List the organization's WordPress and CMS connections
- **Jobs** — Report the status of a publishing job

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 53 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/docswrite.com/docswrite/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Docswrite by hand means choosing between an organization bearer key and per-site tokens in the `x-access-token` or `x-api-key` header, and polling job status yourself. Through Jentic you install once, import Docswrite from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Docswrite puts the post id in the URL path (`/api/v1/posts/{id}`) while the target connection travels in the request body, so rules bound which operations your agent may call. Limit the agent to the operations it needs, such as listing connections and publishing posts, so re-publish and move operations are not included unless you add them.
- **Credential handling:** Your Docswrite credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'publish a Google Doc to WordPress' or 'check a publishing job', and Jentic returns the matching Docswrite operation with its input schema so the agent calls the right endpoint directly.

## Related APIs

- **Contentful** — Contentful is a headless CMS you author in directly, while Docswrite publishes existing Google Docs and Markdown into a CMS.
- **Ghost** — Ghost is a publishing platform that can be a destination for content routed through Docswrite.
- **Webflow** — Webflow hosts the site whose CMS collections can receive content published via Docswrite.

## FAQ

### What authentication does the Docswrite API use?

The Docswrite API accepts an organization API key as a bearer token, per-site API tokens sent in the `x-access-token` or `x-api-key` header, and an oauth2 flow for connected apps, per its OpenAPI spec. Organization-key responses carry RateLimit headers. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.

### Can I publish a Google Doc to WordPress with the Docswrite API?

Yes. The API exports a Google Doc to a connected WordPress site, publishes a Google Doc to any CMS connection, and publishes Markdown or HTML to one or more connections. You can then check the publishing job status and the status of each post.

### Is there a Docswrite MCP server?

You don't need an MCP server to give your agent the Docswrite API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the export and posts operations. Operations load on demand, so your agent's context stays lean instead of holding another server's tool definitions.

### Can I limit what my agent is allowed to do with the Docswrite API?

Yes. Write a rule that allows only the list-connections and publish operations, so the agent can see your CMS connections and publish content but cannot re-publish or move existing posts. Every call the agent makes is logged.

### What are the rate limits for the Docswrite API?

Organization-key responses carry RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers, per the Docswrite spec, but it does not publish fixed numbers. Check the Docswrite documentation at https://docswrite.com for current limits before running a large publishing batch.

### How do I publish content with the Docswrite API through Jentic?

Search Jentic for an intent like 'publish a Google Doc to WordPress', add the Docswrite API from the directory, and store your credential once. Your agent then calls the publish operation for the connection you choose and polls the post status. To run it on your own infrastructure, install Jentic One from its GitHub repo.