---
title: "Leave a party"
method: DELETE
path: "/parties/{party_id}/guests/{guest_id}"
tags: ["Parties"]
---

# Leave a party

`DELETE /parties/{party_id}/guests/{guest_id}`

## Request

- Base URL: `https://api.aisle.wedding/v1`
- URL: `https://api.aisle.wedding/v1/parties/{party_id}/guests/{guest_id}`
- Auth: HTTP bearer

Unlinks this member without deleting the guest, the party or their answers. Promotes a replacement lead when needed. A guest outside this party returns 404. Active accommodation payments return 409. Requires write scope and preview access. No request body.

## Response `204`

The guest has left the party.

## Other responses

- `400`: The request itself could not be read, such as a body that is not a JSON object. A field we refuse is validation_failed instead.
- `401`: The API key is missing, malformed, or no longer valid.
- `402`: The operation requires an active Aisle membership for this wedding.
- `403`: The key is valid but not permitted to do this.
- `404`: No such resource inside the key's wedding.
- `409`: The request collided with the current state of the resource.
- `415`: A request body must be sent as application/json.
- `422`: The request was well-formed but a field was not acceptable. Every field at fault is named in error.details.
- `429`: Too many requests. Retry after the time given in Retry-After.
- `500`: Something went wrong on our side.

---

[API](https://skmtc.dev/aisle/apis/aisle-api.md) · [All operations](https://skmtc.dev/aisle/apis/aisle-api/llms.txt) · [OpenAPI document](https://skmtc.dev/aisle/apis/aisle-api/revisions/689a2f2420cc?raw)