How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bluecore Transactional API (legacy)

The original Bluecore Transactional API on https://api.bluecore.com/email/ - send a transactional or real-time welcome email against a Bluecore campaign, and retrieve the delivery status of a previously triggered send by conversation id. Authenticated by a static customer-specific Bearer API key rather than OAuth. Bluecore's own OpenAPI repository states the company is migrating away from this surface, but the documentation and the specification are both still published with no deprecation notice, no sunset date and no migration guide.

Bluecore Transactional API (legacy) is one of 8 APIs that Bluecore publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transactional, Email, and Legacy. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 2 operations across 2 paths, organized into 2 resource areas, and defines 2 schemas. It is described by OpenAPI 3.0.0.

Requests are made against a single base URL, https://api.bluecore.com/email/.

2 operations 2 paths 2 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
Base URL
https://api.bluecore.com/email/
Resource Areas
2

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. They span 2 resource areas: SEND EMAIL, GET STATUS. Each is listed below with its method, path, parameters, and response codes.

SEND EMAIL 1
POST
/send/v1/{namespace}
Send a Transactional or Real-Time Welcome Email
2 params body → 200
GET STATUS 1
GET
/status/v1/{namespace}/{conversation_id}
Get the Status of an Email Delivery Attempt
3 params → 202

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are body (6 properties), ConversationResponse (2 properties). Each schema is shown below with its type and property counts.

ConversationResponse
object
2 properties
body
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bluecore-transactional-legacy-api-openapi.yml Raw ↑

Other APIs Bluecore publishes across the network.

Bluecore Authn API
Bluecore CampaignsAPIPublic API
Bluecore Direct send API
Bluecore Eligibility API
Bluecore Profile API
Bluecore Transactional API
Bluecore Events API
Where this information came from

This is an independent, third-party profile of Bluecore Transactional API (legacy), published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.