Skip to content
Bottle

Put a count-in back

POST
/cash/unsettle
curl --request POST \
  --url https://example.com/cash/unsettle \
  --header 'Content-Type: application/json' \
  --cookie bottle.session_token=<bottle.session_token> \
  --data '{ "takingIds": [ "019205d1-6e7a-7c3b-9f6e-3a2b1c0d9e8f" ] }'

For a row pressed by mistake, or a driver counted in before the notes actually turned up. The money goes back to being carried by whoever took it. Nothing is deleted: the drop still happened, it is simply not in the safe after all.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
takingIds
required
Array<string>
>= 1 items <= 500 items

Responses

Section titled “Responses”

200

Section titled “200”

Back with the driver

Media typeapplication/json
object
returnedPence
required
integer
drops
required
integer
Examplegenerated
{
  "returnedPence": 1,
  "drops": 1
}

401

Section titled “401”

Not signed in

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}

403

Section titled “403”

Not a member, or without the permission this needs

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}

422

Section titled “422”

Validation failed

Media typeapplication/json
object
error
required
string
Allowed values: validation
message
required
string
issues
required
Array<object>
object
path
required
string
message
required
string
Example
{
  "error": "validation",
  "issues": [
    {
      "path": "email",
      "message": "Invalid email"
    }
  ]
}