---
title: "Delete recurring charge link"
method: DELETE
path: "/v1/recurring-charge-links/{recurring_charge_link_id}"
tags: ["Recurring charge links"]
---

# Delete recurring charge link

`DELETE /v1/recurring-charge-links/{recurring_charge_link_id}`

Cancels the link between a recurring charge plan and an account. Results in the cancellation of all `PENDING` charges for that link. Already canceled links are unaffected.
This endpoint generates a [Recurring charge plan unlinked from account](https://developers.pismo.io/events/docs/balance-recurring-charge-plan-unlinked-from-account-1) event.

**NOTE:** This endpoint requires an account token — an access token encoded with an account ID. Tokens can expire quickly, which can result in a **401 Unauthorized** message.

## Path parameters

- `recurring_charge_link_id` integer, required

## Headers

- `x-cid` string

## Response `200`

OK - Indicates that the server accepted the request and canceled the link.

- RecurringChargeLink — Link between a plan and an account
  - `recurring_charge_link_id` integer — ID of recurring charge link
  - `account_id` integer — Account ID
  - `recurring_charge_plan_id` integer — ID of recurring charge plan
  - `previous_recurring_charge_link_id` integer — ID of previous recurring charge link
  - `org_id` string — Organization ID
  - `created_at` string, date-time — Datetime program calendar strategy was created. Format = YYYY-MM-DDTHH:MM:SS:MM.
  - `cancelled_at` string — Date/time (GMT-3) that link was canceled
  - `end_date` string, date-time — End date for link (GMT-3). When the final charge for a link is made, `end_date` gets populated.
  - `description` string — A description of the scheduled charge that's linked to the account. Use `counter` to specify where the cycle count should be placed. Example: "Annuity {counter}" generates "Annuity 2/12" for the second of twelve annutities. If `counter` is not present, the counter is placed at the end of the description. If no description is configured, the description of the transaction type is used, and the counter is not shown.
  - `tracking_id` string — Customer created tracking ID. Must consist of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and colons (:), with a length from 1 to 128. The Pismo platform uses this field to implement idempotency and prevent duplicates.
  - `creation_cid` string — CID for the creation event
  - `cancellation_cid` string — CID for the cancellation event

## Other responses

- `400` — Bad request
- `409` — The specified resource status conflicts with the current request.
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)