---
search:
  tags:
    - Channel points
    - POST
seo:
  description: >-
    Resolves the redemption as FULFILLED on… Reference for the POST
    /channel-points/redemptions/{redemptionId}/fulfill endpoint in the TipPage
    Developer API.
sidebar:
  label: Mark a redemption fulfilled
  badge: POST
title: Mark a redemption fulfilled
type: openapi-operation
---
Resolves the redemption as FULFILLED on Twitch - the viewer's points stay spent and the redemption leaves the Twitch rewards queue. Call this when your automation completed the redeemed action. Requires `channel_points:manage` and a TipPage-managed reward. Idempotent: repeating the call returns `already_resolved: true`.

`POST /channel-points/redemptions/{redemptionId}/fulfill`

**Responses**

- `200` — The redemption was resolved (or already was).
- `401` — Missing or invalid credential (\`missing\_api\_key\` / \`invalid\_api\_key\`, or \`invalid\_token\` for an expired/revoked OAuth access token).
- `403` — The key lacks the required scope (\`missing\_scope\`).
- `404` — Unknown redemption id for this channel.
- `409` — Not resolvable - \`code\` says why: \`reward\_not\_managed\` (reward wasn't created by TipPage), \`already\_resolved\` (resolved the other way), \`song\_request\_active\` (the song-request flow owns it), or \`twitch\_rejected\` (Twitch refused the update).
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.
- `502` — Twitch was unreachable or errored - retry shortly.

Response example, 200:

```json
{
  "success": true,
  "status": "fulfilled",
  "already_resolved": true
}
```
