---
title: "Get a credit record"
method: GET
path: "/credits/{credit_id}"
tags: ["Credits"]
---

# Get a credit record

`GET /credits/{credit_id}`

Get information about a specific credit transaction.

Returns the full detail of a single credit record, including its amount, credit type, currency, associated customer and partner, creation timestamp, and note.

To query all credits for a customer, use [GET /credits](https://carecloud.readme.io/reference/getcredits). To see the full history of operations on a customer's credits, use [GET /credit-history](https://carecloud.readme.io/reference/getcredithistory).

## Path parameters

- `credit_id` string, required

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` Credit — A customer credit.
    - `credit_id` string — The unique ID of the credit record.
    - `customer_id` string, required — The unique ID of the customer. [GET /customers](https://carecloud.readme.io/reference/getcustomers)
    - `assigned_credits` number, float — The number of earned credits in the record.
    - `available_credits` number, float — The number of available credits from the record.
    - `credit_type_id` string, required — The unique ID of the credit type. [GET /credit-types](https://carecloud.readme.io/reference/getcredittypes)
    - `partner_id` string, required — The unique ID of the partner company. [GET /partners](https://carecloud.readme.io/reference/getpartners)
    - `valid_to` string — Timestamp until which the credit record is valid. Accepts the format `YYYY-MM-DD HH:MM:SS` or ISO-8601 format (`YYYY-MM-DDTHH:MM:SS`). All times must be in the local timezone.
    - `currency_id` string — The unique ID of the currency. [GET /currencies](https://carecloud.readme.io/reference/getcurrencies)
    - `state` 0 | 1 | 2 — State of the credit record. *Possible values are: 0 - deleted / 1 - active / 2 - non active*

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/revisions/329c06dbf8d9/schema)