GET
/v1/posts/{id}/historyGet post state history
Returns every state transition for a post, which is the fastest way to explain a failure.
Required permission: `posts:read`
Accepts `profileId` to target a specific profile. Omit it to use the key’s home profile.
- Base URL
- https://api.cutedyno.com
- Permission
posts:read- Idempotency
- Not applicable. This request has no side effects worth deduplicating.
- MCP tool
- get_post_history
Request
curl -X GET "https://api.cutedyno.com/v1/posts/POST_ID/history" \
-H "Authorization: Bearer $CUTEDYNO_API_KEY"Path parameters
idstringrequiredPost id.
Response
Returns 200 with the following body.
object[]required
Example
{
"history": [
{
"fromState": "string",
"toState": "string",
"reason": "string",
"createdAt": "string"
}
]
}Errors
Failures use the standard error envelope. Branch on code, never on the message.
| Status | Code | When it happens |
|---|---|---|
| 401 | invalid_api_key | The key does not exist, was revoked, or is malformed. Keys start with cdyn_live_. |
| 404 | not_found | The resource does not exist inside the resolved profile. |
| 429 | rate_limit_exceeded | Too many requests for this key. Honour the Retry-After header before retrying. |
| 500 | internal_error | Something failed on our side. Retry with the same Idempotency-Key; report the requestId if it persists. |