Journey Docs
Partner API ExplorerFulfillments

Approve a fulfillment

Required scopepartner:fulfillments:write
POST
/v1/partner/fulfillments/{fulfillmentId}/approve

Approves a claim waiting on staff sign-off. Approval alone does not fulfill it — mark it fulfilled once the member actually receives the benefit.

Authorization

headerAuthorizationBearer <token>

WorkOS access token (JWT) for a user who is a member of the partner organization. The organization the request is scoped to is taken from the token, not from a header or query parameter.

Only a JWT is accepted in this header. A Journey jny_ API key sent as a bearer token is rejected with 401 Invalid or expired token; send it in X-API-Key instead.

WorkOS organization API keys are not accepted yet.

Path Parameters

fulfillmentId*string

External fulfillment id (UUID).

Formatuuid

Request Body

application/json
  1. body
approvedBy?string
modifiedMeta?
notes?string

Response Body

The approved fulfillment.

application/json
  1. response
error?string
isModification?boolean
status?string
success*boolean
curl -X POST 'https://api-prd.cf.journey.com/v1/partner/fulfillments/497f6eca-6276-4993-bfeb-53cbbbba6f08/approve' \  -H 'Content-Type: application/json' \  -d '{}'
{  "error": "string",  "isModification": true,  "status": "string",  "success": true}