---
title: "Get a store group"
method: GET
path: "/store-groups/{store_group_id}"
tags: ["Store groups"]
---

# Get a store group

`GET /store-groups/{store_group_id}`

Get information about a specific store group.

## Path parameters

- `store_group_id` string, required

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` StoreGroup — Store group resource.
    - `store_group_id` string — The unique ID of the store group.
    - `name` string, required — Name of the store group.
    - `last_change` string — Date and time of the last change. *(YYYY-MM-DD HH:MM:SS)*

## 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)