canonical: https://jentic.com/apis/getblueshift.com/blueshift # Getblueshift Blueshift API Blueshift is a cross-channel marketing platform, and its API lets you drive that platform programmatically. Send customer events and bulk event batches to trigger journeys, create and update customer profiles, and manage custom user lists and segments. On the campaign side you can create campaigns, update their schedule, launch or pause them, and execute them for chosen users, plus read campaign details and performance. Catalog endpoints manage the product data used in recommendations, and privacy endpoints let you forget, unforget, or delete customers to meet data-subject requests. The service runs in separate US and EU regions, each with its own base host. ## For AI agents Drive the Blueshift marketing platform: send customer events, manage customer profiles and lists, create and launch campaigns, manage catalogs and segments, and handle privacy requests. ## Scope Covers events, customers, lists, segments, campaigns, catalogs, and privacy actions through the API. Account setup, channel provider configuration, and reporting dashboards live in the Blueshift app, not this API. ## Capabilities - Send single and bulk customer events to trigger marketing journeys - Create and update customer profiles individually or in bulk - Build and edit custom user lists and add or remove members - Create campaigns, then launch, pause, or reschedule them - Execute a campaign for specific users on demand - Manage product catalogs used for recommendations - Handle privacy requests by forgetting or deleting customers ## Use cases ### AI Agent That Triggers Lifecycle Messaging An agent reacting to product activity sends the matching events to Blueshift so the right journey fires. Through Jentic it posts a customer event, updates the profile if needed, and can launch a campaign for a targeted audience. The agent discovers the event and campaign operations by intent, so it drives messaging without a developer wiring HTTP calls or handling two separate credential sets. Example prompt: Post a signup event for a customer, update the profile with the source, and launch the onboarding campaign for that user ### Customer Data Sync into Blueshift A data pipeline keeps Blueshift profiles in sync with the system of record. It creates and updates customers, sends bulk events for historical activity, and maintains custom user lists that power segments. Because bulk endpoints accept batches, the sync stays efficient without a call per record. Example prompt: Send a bulk customers update, post historical events in batches, and refresh a custom user list with the current audience ### Campaign Orchestration and Reporting A marketing ops tool manages the campaign lifecycle from code. It creates a campaign, sets its schedule, launches or pauses it, and reads campaign details and performance to report back. This lets teams run campaigns through automation and dashboards rather than only the Blueshift UI. Example prompt: Create a campaign, schedule it, launch it, and later read its detail endpoint to report delivery and engagement ### Privacy and Data-Subject Requests A compliance workflow processes deletion and suppression requests. When a request arrives it calls the forget or delete customer endpoints so the person's data is handled per policy, and can unforget if a request is reversed. Routing these through automation gives a consistent, logged path for data-subject requests. Example prompt: On a verified deletion request, call the forget customer endpoint for the matching profile and record the action for the audit trail ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/v1/event` | Send a single customer event | | POST | `/api/v1/customers` | Create or update a customer profile | | GET | `/api/v1/customers/{uuid}` | Read a customer profile by id | | POST | `/api/v1/campaigns/{campaign_type}` | Create a campaign of a given type | | PATCH | `/api/v1/campaigns/{campaign_uuid}/launch` | Launch a campaign | | GET | `/api/v1/segments/list` | List available segments | | POST | `/api/v1/custom_user_lists/create` | Create a custom user list | ## Key resources - **Customers** — Create, update, merge, and delete customer profiles, individually or in bulk - **Events** — Single and bulk event ingestion that triggers journeys, with debug and history - **Custom user lists** — Create lists and add, remove, or overwrite their members - **Segments** — List segments and read the users matching a segment - **Campaigns** — Create, schedule, launch, pause, and execute campaigns and read their detail - **Catalogs** — Manage the product catalog data used for recommendations ## Why Jentic - **Setup:** Using the Blueshift API by hand means juggling two basic-auth credential sets, choosing the correct US or EU host, and knowing which endpoints send events versus manage campaigns. Through Jentic you install once, import the API from the Directory, and your agent calls the right operation with the right credential. - **Permission scoping:** Blueshift includes write and destructive operations, so scoping matters. You allow only the operations a task needs, keeping campaign launch, pause, and the forget or delete customer endpoints out of the allowed set unless you intend them. Rules run on your own instance and every call the agent makes is logged. - **Credential handling:** Your Blueshift event and user API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time, so neither enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a customer event' or 'launch a campaign', and Jentic returns the matching Blueshift operation with its input schema so the agent calls the right endpoint without reading reference docs. ## Related APIs - **Braze API** — Cross-channel customer engagement with messaging and journeys - **Klaviyo API** — Marketing automation focused on email and SMS for commerce - **Mailchimp Marketing API** — Email campaigns, audiences, and templates ## FAQ ### What authentication does the Blueshift API use? Per its OpenAPI spec it uses HTTP basic authentication with two separate credential sets: an event API credential for sending events and a user API credential for the customer, campaign, and catalog endpoints. Through Jentic each credential is stored encrypted on your own instance and injected at call time, so neither appears in the agent's prompt or logs. ### Does the Blueshift API have separate US and EU endpoints? Yes. The spec lists two regional hosts, api.getblueshift.com for the US and api.eu.getblueshift.com for the EU. Point your integration at the region where your Blueshift account lives so data stays in the correct location. ### How do I send a customer event to the Blueshift API? Call POST `/api/v1/event` with the event payload, or POST `/api/v1/bulkevents` to send a batch. Events trigger the journeys configured in Blueshift. Through Jentic you search for the intent 'send a customer event' and the agent gets the operation and its input schema. ### Can I create and launch campaigns through the Blueshift API? Yes. POST `/api/v1/campaigns/{campaign_type}` creates a campaign, and PATCH endpoints under a campaign let you update its schedule, launch it, or pause it. You can also execute a campaign for chosen users and read its detail to report on delivery. ### What are the rate limits for the Blueshift API? The OpenAPI spec does not define numeric rate limits; they depend on your Blueshift plan. Use the bulk event and customer endpoints for high volume and check https://getblueshift.com for current guidance. ### Can I control what my agent is allowed to do with the Blueshift API through Jentic? Yes, and it matters here because the API includes destructive operations. You can allow read and event-sending operations while withholding campaign launch and the forget or delete customer endpoints, so an agent cannot pause a live campaign or erase a profile unless you permit it. Every call runs through your own instance and is logged. ### Is there a Blueshift MCP server? You don't need a separate MCP server to give your agent the Blueshift API. Jentic connects it directly from the API Directory: import the API and your agent sends events and manages campaigns on demand without loading another server's tool definitions into its context.