Skip to main content
POST
Create an embedded view URL

Authorizations

Authorization
string
header
required

Your workspace API key, sent as Authorization: Bearer blu_.... Workspace admins can find it in the Blujay app under API.

An API key has full access to your workspace and works on every endpoint. There is no test mode: every key sends real messages and changes real data, so keep it secret and use it only from your server.

Each API key can make 600 read requests and 120 write requests per minute, plus 60 attachment requests per minute. Over a limit you get 429 RATE_LIMIT_EXCEEDED with Retry-After.

Reseller partner keys. A partner key acts for one of the partner's customers when the request names it in the Blujay-Workspace header (the customer's workspace_ ID). Without the header it reaches only /v1/partner/* and /v1/me. Each customer gets the limits above for each partner key, and all of a partner's requests together get ten times those limits; a 429 says which in error.details[0].scope (partner_customer or partner). A messaging key can read anything for a customer and change chats, messages, contacts, attachments and vCards; everything else needs an admin key (403 PARTNER_ROLE_FORBIDDEN). Paused or closing customers can be read but not changed (409 CUSTOMER_PAUSED or CUSTOMER_CLOSING). Any other workspace ID in the header returns 404 NOT_FOUND; using the header with any other credential returns 400 WORKSPACE_HEADER_NOT_ALLOWED.

Headers

Blujay-Workspace
string

Reseller partner keys only. The workspace_ ID of one of your customers; the request runs as that customer.

Pattern: ^workspace_[A-Za-z0-9_-]+$
Example:

"workspace_abc123"

Body

application/json

thread mode needs exactly one of phone_number or chat_id; inbox mode takes neither.

team_member_id
string
required

An active teammate of the customer, from POST /v1/team-members. The view acts as this teammate.

Required string length: 1 - 200
mode
enum<string>
required

thread shows one conversation; inbox shows the customer's whole inbox with the assignee filter.

Available options:
thread,
inbox
parent_origin
string
required

The exact origin of the page that will frame the view; one of your registered framing origins.

Required string length: 1 - 255
Example:

"https://app.yourproduct.com"

phone_number
string

Thread mode only. A US number, with or without a contact yet.

Required string length: 1 - 64
Example:

"+14805550101"

chat_id
string

Thread mode only. A direct or group chat of the customer.

Required string length: 1 - 200

Response

The view URL was created.

Wraps every successful response. The result is in data.

status
enum<string>
required
Available options:
success
trace_id
string
required
Pattern: ^trc_[A-Za-z0-9_-]+$
Example:

"trc_8f2a1c0e4b7d"

timestamp
string<date-time>
required
Example:

"2026-10-14T17:01:00.000Z"

data
object
required
client_request_id
string

Your X-Request-ID header value, echoed back when you send one. Not included on the send responses (POST /v1/chats and POST /v1/chats/{chat_id}/messages); keep your own mapping from your request ID to the returned message ID there.