---
title: "Get link between a plan and an account"
method: GET
path: "/v1/recurring-charge-plans/{recurring_charge_plan_id}/accounts/{account_id}"
tags: ["Recurring charge links"]
---

# Get link between a plan and an account

`GET /v1/recurring-charge-plans/{recurring_charge_plan_id}/accounts/{account_id}`

## Request

- Base URL: `https://sandbox.pismolabs.io/recurring-charge`
- URL: `https://sandbox.pismolabs.io/recurring-charge/v1/recurring-charge-plans/{recurring_charge_plan_id}/accounts/{account_id}`
- Auth: HTTP bearer

Gets the link between a plan and an account, given the plan ID and account ID.

**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_plan_id` integer, required
- `account_id` integer, required

## Query parameters

- `page` integer
- `perPage` integer

## Headers

- `x-cid` string

## Response `200`

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

- PagedRecurringChargeLink
  - `current_page` integer: Current page
  - `per_page` integer: Number of items per page
  - `pages` integer: Number of pages
  - `total_items` integer: Total items
  - `is_last_page` boolean: Set to `true` if this is the last page.
  - `items` RecurringChargeLink[]
    - `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 (GMT-3) that asset was registered on Pismo platform
    - `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: Tracking ID
    - `creation_cid` string: CID for the creation event
    - `cancellation_cid` string: CID for the cancellation event

## Other responses

- `400`: Bad Request
- `500`: Internal server error

---

[API](https://skmtc.dev/pismo/apis/revolving-credit-recurring-charges.md) - [All operations](https://skmtc.dev/pismo/apis/revolving-credit-recurring-charges/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/revolving-credit-recurring-charges/revisions/a5fea1d82e51?raw)