---
canonical_url: "https://docs.composio.dev/toolkits/bluebarry"
markdown_url: "https://docs.composio.dev/toolkits/bluebarry.md"
product: "platform"
version: null
last_updated: null
---

# Bluebarry

Bluebarry is a customer data and product-advice platform for analyzing and synchronizing shopper identities and profiles.

- **Category:** analytics
- **Auth:** API_KEY
- **Composio-managed OAuth available?** N/A
- **Tools:** 2
- **Triggers:** 0
- **Slug:** `BLUEBARRY`
- **Version:** 00000000_00

## Tools

### List Identities

**Slug:** `BLUEBARRY_LIST_IDENTITIES`

Return shopper identity records. With limit, page by increasing offset; without limit, follow next_cursor when present. Filter mergedIntoId eq null for surviving identities. Incremental sync must overlap updatedDate windows and upsert by id.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum identities to return (1-5000). When set, continue by increasing offset by the number of returned items; Bluebarry does not provide a next_cursor for this explicit pagination mode. |
| `offset` | integer | No | Number of identities to skip when limit is set. Use a stable order_by, increase offset by the number of returned items, and stop when fewer than limit are returned. Do not combine with next_cursor. |
| `order_by` | string | No | Comma-separated OData sort expression. Use updatedDate asc,id asc for stable offset pagination. Sorting does not replace the overlap window required for incremental sync. |
| `next_cursor` | string | No | Opaque cursor from server-managed pagination when limit was omitted. Pass it alone to continue that query; do not combine it with offset. |
| `include_count` | boolean | No | Whether to include the total number of matching identities as total_count. |
| `select_fields` | string | No | Comma-separated identity fields to return, such as id,email,updatedDate,mergedIntoId. Unknown fields cause an error. |
| `filter_expression` | string | No | OData filter expression, such as mergedIntoId eq null or updatedDate ge 2026-06-01T10:10:00Z. For incremental sync, re-read an overlap window and upsert by stable id. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Profiles

**Slug:** `BLUEBARRY_LIST_PROFILES`

Return raw, unmerged profile rows. With limit, page by increasing offset; without limit, follow next_cursor when present. Use this for per-session or per-user detail because one shopper can appear in multiple rows.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `limit` | integer | No | Maximum raw profiles to return (1-5000). When set, continue by increasing offset by the number of returned items; Bluebarry does not provide a next_cursor for this explicit pagination mode. |
| `offset` | integer | No | Number of raw profiles to skip when limit is set. Use a stable order_by, increase offset by the number of returned items, and stop when fewer than limit are returned. Do not combine with next_cursor. |
| `order_by` | string | No | Comma-separated OData sort expression. Use updatedDate asc,id asc for stable offset pagination. |
| `next_cursor` | string | No | Opaque cursor from server-managed pagination when limit was omitted. Pass it alone to continue that query; do not combine it with offset. |
| `include_count` | boolean | No | Whether to include the total number of matching raw profiles as total_count. |
| `select_fields` | string | No | Comma-separated profile fields to return, such as id,email,updatedDate,identityId,sessionId. Unknown fields cause an error. |
| `filter_expression` | string | No | OData filter expression for raw profiles, such as updatedDate ge 2026-06-01T10:10:00Z. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |