Partner API ExplorerFulfillments
Verify a fulfillment code
Required scope
partner:fulfillments:readPOST
Looks up a claim by the code the member reads out at the desk. Read-only: it does not mark anything fulfilled, so staff can confirm what is owed before acting.
header
AuthorizationBearer <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.
application/json- body
propertyId*numberverificationCode*stringLength
3 <= length <= 100verifiedBy?stringWhat the code resolves to, and whether it can be fulfilled.
application/json- response
canApprove?booleanclaimedAt?stringerror?stringfound*booleanfulfillmentId?stringitemName?stringitemType?stringmemberId?numbermemberName?stringmeta?pointsCharged?numberresponseDeadline?stringsource?stringstatus?stringcurl -X POST 'https://api-prd.cf.journey.com/v1/partner/fulfillments/verify' \ -H 'Content-Type: application/json' \ -d '{ "propertyId": 0, "verificationCode": "string"}'{ "canApprove": true, "claimedAt": "string", "error": "string", "found": true, "fulfillmentId": "string", "itemName": "string", "itemType": "string", "memberId": 0, "memberName": "string", "meta": {}, "pointsCharged": 0, "responseDeadline": "string", "source": "string", "status": "string"}