Bluecore GET STATUS API

The GET STATUS API from Bluecore — 1 operation(s) for get status.

Operations 1

GET /status/v1/{namespace}/{conversation_id} Get the Status of an Email Delivery Attempt

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/bluecore-get-status-api"
All apis
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

bluecore-get-status-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Bluecore Transactional GET STATUS API
servers:
- url: https://api.bluecore.com/email/
tags:
- name: GET STATUS
paths:
  /status/v1/{namespace}/{conversation_id}:
    get:
      summary: Get the Status of an Email Delivery Attempt
      description: " This section details how to get the status of an email delivery attempt. \n\n**Returns**: Object containing the status and details of the message. (See <span id='response-code-text'>**Responses > 202**</span> below). "
      parameters:
      - in: path
        name: namespace
        description: The partner namespace in Bluecore.
        required: true
        schema:
          type: string
      - in: path
        name: conversation_id
        description: The conversation ID.
        required: true
        schema:
          type: string
      - in: header
        name: Authorization Bearer
        description: The authorization token in the header.
        required: true
        schema:
          type: string
      responses:
        '202':
          description: Successful receipt of the request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConversationResponse'
      tags:
      - GET STATUS
components:
  schemas:
    ConversationResponse:
      type: object
      properties:
        status:
          type: string
          description: 'This is the status of the email message. Possible values: Being Processed, Sent for Delivery, Delivered, or Failed.'
          enum:
          - Being Processed
          - Sent for Delivery
          - Delivered, Failed
          example: Being Processed
        message:
          type: string
          description: 'The details of the failure. Possible values: Bounce, Block, Previously Bounced/Blocked, Email Content Conversation Failed.'
          enum:
          - Bounce
          - Block
          - Previously Bounced/Blocked
          - Email Content Generation Failed
          example: string
x-tagGroups:
- name: GETTING STARTED
  tags:
  - INTRODUCTION
- name: API ACCESS
  tags:
  - AUTHORIZATION
- name: ENDPOINTS
  tags:
  - SEND EMAIL
  - GET STATUS
- name: API REFERENCE
  tags:
  - REQUEST BODY
  - TEMPLATE ATTRIBUTES
  - CUSTOMER ATTRIBUTES
  - VALIDATION
  - API RESPONSE CODES
  - API LIMITS