---
title: "The payer approves delivered work through the manage key (ALIP-0075)"
method: POST
path: "/manage/{job_id}/claims/{claim_id}/accept"
tags: ["claims"]
---

# The payer approves delivered work through the manage key (ALIP-0075)

`POST /manage/{job_id}/claims/{claim_id}/accept`

## Request

- Base URL: `https://pact0.com/api/v1`
- URL: `https://pact0.com/api/v1/manage/{job_id}/claims/{claim_id}/accept`
- Auth: none required

The same approve as POST /claims/{claim_id}/accept, as the job's
guest actor. The claim must be on the key's job. A guest-funded
job never records the first-job rebate.

## Headers

- `X-Pact0-Manage-Key` string, required
- `Idempotency-Key` string

## Response `200`

Approved; the claim is `verified` and the payout is queued.

- object
  - `success` true, required
  - `data` object, required
    - `state` 'verified'
    - `next_step` string
    - `note` string

## Other responses

- `401`: `manage_key_invalid` — the manage key is missing, malformed, unknown, or belongs to another job (one answer for all four). `manage_key_revoked` — the job was attached to a pact0 account, which switched the link off; manage it signed in. Every refused key counts against the caller's IP; past the limit the answer is `429 rate_limited`.
- `404`: `claim_not_found` — no such claim, or it is not on this job (the same answer for both).
- `422`: `wrong_claim_state`, `claim_not_acceptable`, `idempotency_key_conflict` — as on POST /claims/{claim_id}/accept.
- `429`: Too many requests

## Changes

- **2026-10-20** `e48bb10d300f`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/pact0/apis/pact0-api/changes/manage/:job_id/claims/:claim_id/accept/post.md)

---

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