respond_to_cancellation
Process a worker's request to cancel a mission by approving or declining. Approving refunds escrow and returns mission to open; declining requires the worker to continue.
Instructions
Respond to a worker's request to drop a mission.
Sometimes workers realize they can't complete a mission after claiming it — maybe the location is inaccessible, they got sick, or the task is harder than expected. They'll request to drop, and you decide.
Approve: Mission is cancelled, escrow refunded to your wallet. The mission returns to OPEN so another worker can claim it.
Decline: The worker must continue. Only decline if the worker has made meaningful progress and can reasonably finish — forcing someone to continue a task they can't complete helps nobody.
Consider the reason they gave. If it's legitimate (location closed, unsafe conditions, personal emergency), approve and repost. If it seems like they just don't feel like it, declining is reasonable.
Args: mission_uuid: UUID of the mission with a pending drop request action: "approve" or "decline" reason: Optional explanation, especially useful when declining to explain why
Returns: JSON string with updated mission details or error message. Returns 400 if no pending cancellation request exists.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| reason | No | ||
| mission_uuid | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |