Connect a blog automation tool

Automation keys let a trusted tool create or update blog content without using a team member's password.

Create a key

1. Open Dashboard → Blog → Resources → Automation keys.
2. Enter a name that identifies the tool, such as “Editorial workflow”.
3. Choose Test while setting up the connection or Live for real publishing.
4. Choose only the permissions the tool needs. Reading, writing, publishing, image uploads, and category management are separate permissions.
5. Select Create key, then copy the value immediately. It is shown once.

Paste the key into the authorization or credential field in your automation tool. Keep it in that tool's protected secret storage.

Use the automation endpoints under your normal Fetchply domain at /api/blog/v1. The OpenAPI description is available at /api/blog/openapi.json.

Rotate or revoke a key

Choose Rotate when a key may have been copied somewhere unsafe or as part of a regular security review. Copy the replacement immediately. The old value keeps working briefly so an active workflow can switch without interruption.

Choose Revoke when a workflow is retired or a key must stop working immediately. Revocation cannot be undone; create a new key if the connection is needed later.

Retries and duplicate submissions

For create, update, and publish actions, configure your tool to send the same idempotency value when retrying the same request. A safe retry returns the original result rather than creating the action twice. Reusing that value for different content is rejected.

Troubleshooting

The key is rejected

Confirm the complete key was copied, begins with the value shown when it was created, and has not expired or been revoked. Rotated keys may stop working after the handover period; replace them with the newest value.

The tool says permission is missing

The key does not include the permission required by that action. Ask a blog owner or administrator to create a more narrowly named key with the missing permission. Do not replace it with an unrestricted key unless every permission is necessary.

The connection is blocked by its address

The key may be limited to approved network addresses. Run the workflow from an approved address or ask an owner or administrator to review the key's address restrictions.

The tool reports too many requests

Wait for the retry time shown in the response, then retry with the same idempotency value. Reduce how many articles or images the workflow sends at once.

A duplicate submission is reported

The same idempotency value was used for different content. Use a new value for a genuinely new action. Keep the existing value only when retrying the exact same action.