---
title: "Get posterly publishing status"
method: GET
path: "/api/v1/status"
tags: ["Identity"]
---

# Get posterly publishing status

`GET /api/v1/status`

## Request

- Base URL: `https://www.poster.ly`
- URL: `https://www.poster.ly/api/v1/status`
- Auth: HTTP bearer

Return posterly own publishing health for agents deciding whether to schedule: overall state from the last 4 hours of publishing success, active incidents, and per-platform state with 7-day success rates and publish counts. Anonymous aggregates only, with no post ids, user data or raw errors. When fewer than 10 posts were counted in the last 4 hours and no incident is active, `state` is `unknown` and `insufficient_data` is true: not enough recent activity to judge. Failures caused by content or account problems are excluded from the rates and reported as `customer_side_failures_7d`. Requires the `accounts:read` scope. Bypasses the API add-on paywall. Figures are cached for about a minute. Returns 503 `status_unavailable` if the status cannot be built.

## Response `200`

Publishing status fetched successfully.

- PosterlyStatusResponse: posterly publishing health as anonymous aggregates. Every figure names its window. Customer-side failures (content or account problems) are excluded from the rates.
  - `state` 'operational' | 'degraded' | 'partial_outage' | 'major_outage' | 'unknown', required: Overall publishing health from the last 4 hours. `unknown` when fewer than 10 posts were counted in 4 hours and no incident is active: not enough recent activity to judge. An active incident outranks insufficient data, which outranks the 95 / 85 / 70 percent thresholds.
  - `state_basis` string, required
  - `insufficient_data` boolean, required: True only when "not enough activity" is the deciding reason (false when an incident overrides it).
  - `counted_4h` integer, required: Posts counted in the success rate over the last 4 hours: published posts plus failures on posterly side or in a platform-wide problem. Failures caused by content or the account are not counted. Always the real number.
  - `as_of` string, date-time, required: When the figures were computed.
  - `incidents` object[], required
    - `platform` string, required
    - `state` 'degraded' | 'partial_outage' | 'major_outage', required
    - `message` string, required
  - `platforms` object[], required
    - `platform` string, required
    - `state` 'operational' | 'degraded' | 'outage' | 'low_volume' | 'no_data', required: low_volume is under 20 publishes in 7 days.
    - `success_rate_7d` number, nullable, required: Percent over 7 days. Null for low_volume and no_data.
    - `publishes_7d` integer, required: Posts counted in the last 7 days (customer-side failures not included).
    - `customer_side_failures_7d` integer, required: Failures in the last 7 days caused by content or the account, such as an expired connection or a content limit.
  - `upcoming_scheduled_posts` integer, required: Posts across posterly that are scheduled and still in the future.
  - `notes` string, required

## Other responses

- `401`: Invalid or missing API key
- `403`: Request is authenticated but not allowed
- `429`: Too many requests
- `503`: Temporarily unavailable. Retry, or fall back to the documented alternative.

---

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