---
title: "Publish a draft now"
method: POST
path: "/v1/drafts/{id}/publish"
tags: ["Drafts"]
---

# Publish a draft now

`POST /v1/drafts/{id}/publish`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/drafts/{id}/publish`
- Auth: HTTP bearer

Publishes the Draft now, under create post's rules and safety limits. Success deletes the Draft and its media, writes a publish record and returns the post id, no webhook. A known failure keeps the content; a scheduled time already passed is cleared. The responses say more.

## Path parameters

- `id` string, required

## Response `201`

Published. The Draft and its media are deleted and a publish record is written. No webhook is sent: this response is the result.

- object
  - `object` 'post_created', required: Response type discriminator.
  - `id` string, nullable, required: The published post's id.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `401`: Missing or invalid API key.
- `403`: Forbidden. NO_ACTIVE_SEAT: the account is not attached to an active seat.
- `404`: No Draft with this id among yours (RESOURCE_NOT_FOUND).
- `409`: DRAFT_PUBLISHING: a publish of this Draft is in flight. Read it again in a few seconds.
- `422`: ACCOUNT_REQUIRED: the Draft has no account. DRAFT_NOT_PUBLISHABLE: a content gap, the message names the field (for example text: empty). The Draft is unchanged.
- `429`: An account-safety limit or a platform rate limit refused the publish. The Draft's content is unchanged; a scheduled time still ahead stays scheduled, one already passed is cleared.
- `502`: The platform refused or failed the publish; the error says whether a retry can help. A known failure leaves the Draft's content unchanged (a scheduled time still ahead stays scheduled, one already passed is cleared); an unknown outcome fails it (outcome_unknown).
- `504`: PLATFORM_ERROR: the platform did not answer in time, so the post may have been published. The Draft is failed (outcome_unknown): check the account's posts before publishing again.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)