---
title: "Get all point records"
method: GET
path: "/points"
tags: ["Points"]
---

# Get all point records

`GET /points`

Get a list of all point transactions and their current values.

## Query parameters

- `count` integer
- `offset` integer
- `sort_field` string
- `sort_direction` 'ASC' | 'DESC'
- `customer_id` string
- `point_type_id` string
- `create_point_time_from` string
- `create_point_time_to` string

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` object
    - `points` Point[] — List of the point records.
      - `point_id` string — The unique ID of the point record.
      - `customer_id` string, required — The unique ID of the customer. [GET /customers](https://carecloud.readme.io/reference/getcustomers)
      - `assigned_points` number, float — The number of earned points.
      - `available_points` number, float — The number of points available actually taking into account the eventual points redemption.
      - `point_type_id` string, required — The unique ID of the point type. [GET /point-types](https://carecloud.readme.io/reference/getpointtypes)
      - `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 point 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.
      - `state` 0 | 1 | 2 — State of the point record. *Possible values are: 0 - deleted / 1 - active / 2 - non active*
      - `created_at` string — Timestamp of the point record creation. 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.
      - `note` string — Note for the new point record.
    - `total_items` integer — The number of all found point records.

## 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/versions/329c06dbf8d9/schema)