# List sales channels

Returns all sales channels available to the merchant.

See the Pagination section in the API overview above for details on how pagination works.

Endpoint: GET /sales_channels
Version: 2.0.0
Security: BearerAuth

## Query parameters:

  - `limit` (integer)
    Number of items to return per page (for pagination)

## Response 200 fields (application/json):

  - `data` (array)

  - `data.active` (boolean, required)
    Whether the sales channel is actively syncing data with Hive

  - `data.created_at` (string, required)
    When the sales channel was created

  - `data.domain` (string, required)
    The domain of the sales channel

  - `data.id` (integer, required)
    Hive's unique sales channel identifier

  - `data.is_b2b` (boolean, required)
    Whether the sales channel is a B2B sales channel (orders imported as B2B by default)

  - `data.name` (string, required)
    The name of the sales channel

  - `data.reason_for_not_working` (string,null)
    The reason for the sales channel not working

  - `data.type` (string, required)
    The type of the sales channel

  - `data.updated_at` (string, required)
    When the sales channel was last updated

  - `data.working` (boolean, required)
    Whether the sales channel integration is working properly. If false, the reason_for_not_working field will be populated.

  - `pagination` (object)

  - `pagination.first_page_url` (string)
    URL to fetch the first page of results

  - `pagination.limit` (integer)
    Number of items returned per page

  - `pagination.next_page_url` (string,null)
    URL to fetch the next page of results. If null, there are no more results.

## Response 401 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code

## Response 403 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code

## Response 429 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code