Bluecore · Arazzo Workflow

Onboard a Bluecore customer and send a transactional message

Version 1.0.0

Authenticate, upsert a Customer Profile, opt them into marketing, send a transactional message with an idempotency key, and read its delivery status.

1 workflow 4 source APIs 1 provider
View Spec View on GitHub CompanyRetailMarketingCustomer Data PlatformPersonalizationEmailSMSMessagingE-CommerceConsentArazzoWorkflows

Provider

bluecore

Workflows

onboardCustomerAndSendTransactional
End-to-end onboarding and first transactional send for a shopper.
5 steps inputs: campaign_id, client_id, client_secret, email, namespace, send_id outputs: statuses
2
upsertCustomer
3
optInMarketing
4
sendTransactional
5
getStatus

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Onboard a Bluecore customer and send a transactional message
  version: 1.0.0
  summary: >-
    Authenticate, upsert a Customer Profile, opt them into marketing, send a transactional
    message with an idempotency key, and read its delivery status.
  x-realizes-capability-ids:
  - BC-420.10
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-420.10
      capability_name: Customer Data Management
      spec: bluecore-profile-api-openapi.yml
      confidence: 0.9
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: authnApi
  url: ../openapi/bluecore-authn-api-openapi.yml
  type: openapi
- name: eligibilityApi
  url: ../openapi/bluecore-eligibility-api-openapi.yml
  type: openapi
- name: profileApi
  url: ../openapi/bluecore-profile-api-openapi.yml
  type: openapi
- name: transactionalApi
  url: ../openapi/bluecore-transactional-api-openapi.yml
  type: openapi
workflows:
- workflowId: onboardCustomerAndSendTransactional
  summary: End-to-end onboarding and first transactional send for a shopper.
  inputs:
    type: object
    required: [client_id, client_secret, namespace, email, campaign_id, send_id]
    properties:
      client_id: {type: string}
      client_secret: {type: string}
      namespace: {type: string, default: bluestore}
      email: {type: string, default: alice@gmail.com}
      campaign_id: {type: string}
      send_id: {type: string, description: Client-generated unique idempotency key.}
  steps:
  - stepId: getToken
    operationId: Authn_GetAccessToken
    requestBody:
      contentType: application/json
      payload:
        client_id: $inputs.client_id
        client_secret: $inputs.client_secret
        audience: https://a.bluecore.com
        grant_type: client_credentials
    outputs:
      access_token: $response.body#/access_token
  - stepId: upsertCustomer
    operationId: Profile_CreateOrUpdate
    parameters:
    - name: namespace
      in: path
      value: $inputs.namespace
    - name: authorization
      in: header
      value: "Bearer $steps.getToken.outputs.access_token"
    requestBody:
      contentType: application/json
      payload:
        id: {email: $inputs.email}
        attributes: {name: Alice}
  - stepId: optInMarketing
    operationId: Eligibility_Update
    parameters:
    - name: namespace
      in: path
      value: $inputs.namespace
    - name: authorization
      in: header
      value: "Bearer $steps.getToken.outputs.access_token"
    requestBody:
      contentType: application/json
      payload:
        id: {email: $inputs.email}
        state: {event: OPTIN, message_type: MARKETING}
  - stepId: sendTransactional
    operationId: Transactional_Send
    parameters:
    - name: namespace
      in: path
      value: $inputs.namespace
    - name: id
      in: path
      value: $inputs.send_id
    - name: authorization
      in: header
      value: "Bearer $steps.getToken.outputs.access_token"
    requestBody:
      contentType: application/json
      payload:
        message:
          identifiers:
          - {email: {email: $inputs.email}}
          campaign_ids: [$inputs.campaign_id]
    outputs:
      campaign_id: $response.body#/data/campaign_id
  - stepId: getStatus
    operationId: Transactional_Get
    parameters:
    - name: namespace
      in: path
      value: $inputs.namespace
    - name: id
      in: path
      value: $inputs.send_id
    - name: authorization
      in: header
      value: "Bearer $steps.getToken.outputs.access_token"
    outputs:
      statuses: $response.body#/data/statuses
  outputs:
    statuses: $steps.getStatus.outputs.statuses

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/bluecore-onboard-and-message.arazzo"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.