---
title: "Custom unsubscribe handling"
method: POST
path: "/unsubscribe/{delivery_id}"
tags: ["Track Customers"]
---

# Custom unsubscribe handling

`POST /unsubscribe/{delivery_id}`

This endpoint lets you set a global unsubscribed status outside of the subscription pathways native to Customer.io. If you use [custom unsubscribe links](/journeys/people/multiple-subscription-types), you can host a custom unsubscribe page and use this API to send unsubscribe data, associated with a particular delivery, to Customer.io.

**NOTE**: This endpoint **requires** a `Content-type: application/json` header. This endpoint **does not require** an `Authorization` header.

Your request sets a person's `unsubscribed` attribute to `true`, attributes their unsubscribe request to the individual email/delivery that they unsubscribed from, and lets you segment your audience based on `email_unsubscribed` events when you use a custom subscription center.

If you use a custom subscription center (managing subscriptions to various types of messages with custom attributes), this request *does not* set a custom attribute. You must perform a [separate request](/integrations/api/track/tag/track-customers/identify/) to update a person's custom subscription attributes.

## Request body

- object
  - `unsubscribe` boolean — If true, a person's `unsubscribed` attribute is set to true and the unsubscription is attributed to the delivery.

## Response `200`

A successful request returns an empty object response.

## Other responses

- `400` — The `delivery_id` format is incorrect or the request is malformed.

---

[API](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference.md) · [All operations](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/customer/customer-io-journeys-api-reference/revisions/4b391af7cb06/schema)