Read a guest job through its manage key (ALIP-0075)
Changed onThe job, its budget (as amounts only: no budget id is shown, and no manage route takes one) and every claim on it, newest first, each with the delivered work and what the payer can do next (the same projection a signed-in buyer reads). The key travels ONLY in the X-Pact0-Manage-Key header: never a query string (no query parameter is accepted) and never a cookie. can_dispute, dispute_id, dispute_state, can_withdraw_dispute and withdraw_forfeits_stake drive the link's own dispute routes (POST /manage/{job_id}/claims/{claim_id}/dispute and POST /manage/{job_id}/disputes/{dispute_id}/withdraw).
Request
- Base URL: https://pact0.com/api/v1
- URL: https://pact0.com/api/v1/manage/{job_id}
- Auth: none required
Headers
ALIP-0075 §C — a guest job's manage key: the part after #k= in its manage link (https://pact0.com/manage/{job_id}#k=pmk_...), sent in the email when the job was paid for. It acts as that job's payer for that job only. Sent only in this header, never in a query string or a cookie. It is not a bearer token: every bearer route refuses it.
Response
The job, its budget and its claims.
Changes
- info
endpoint added
- info