#The AgentDisplayMessageAttachment is a file attached to a message object

AgentDisplayMessageAttachment is a file attached to a message

mimeType

string

name

string

GET/v1/agent/conversationRequires auth

#Get agent conversation

Get the display-ready chat history for a specific context.

#Parameters

query parameters

contextType

stringquery

dashboard id — the dashboard does not exist yet while the user and the assistant are still agreeing on what it should show. Once it exists, editing it happens under AGENT_CONTEXT_TYPE_ANALYTICS_DASHBOARD instead. id is the EVENT id, not the link id: two visits to the same link are two different subjects, and sharing a thread between them lets one visitor's details bleed into answers about another. the WORKSPACE id: this thread is not about any one link, dashboard or design, and every capability the resource-scoped agents have is available from it. One conversation per workspace, so it survives navigation.

Allowed values

AGENT_CONTEXT_TYPE_LINK_ANALYTICS

Building a link's analytics dashboard. context_id is the LINK id, not a

AGENT_CONTEXT_TYPE_LEAD_SCORE

A conversation about one visit and the lead score it produced. The context

AGENT_CONTEXT_TYPE_WORKSPACE

The workspace-wide assistant, with no resource selected. The context id is

contextId

stringquery

#Response

200

Everything worked as expected.

messages

array<object>

#Error response

400-599

All endpoints may return an unexpected error payload when a request cannot be processed.

error

objectRequired

Wrapped error response.

Example request (cURL)

curl -X GET "https://api.linkbreakers.com/v1/agent/conversation?contextType={contextType}&contextId={contextId}" \
  -H "Authorization: Bearer YOUR_TOKEN"

Typical response

{
  "messages": [
    {
      "attachments": [
        {}
      ],
      "id": "string",
      "sender": "string",
      "text": "string",
      "timestamp": "2026-08-23T01:59:52.773Z"
    }
  ]
}

Base URL: https://api.linkbreakers.com

POST/v1/agent/messageRequires auth

#Send agent message

Send a message to the agent. The context type determines which specialized sub-agent handles the request.

#Parameters

This endpoint does not accept any parameters.

#Request body

contextId

string

ID of the resource being edited (dashboard ID, workflow ID, link ID)

contextMetadata

string

Optional pre-existing data from the UI (e.g. wizard form state) injected as context

contextType

string (enum)

dashboard id — the dashboard does not exist yet while the user and the assistant are still agreeing on what it should show. Once it exists, editing it happens under AGENT_CONTEXT_TYPE_ANALYTICS_DASHBOARD instead. id is the EVENT id, not the link id: two visits to the same link are two different subjects, and sharing a thread between them lets one visitor's details bleed into answers about another. the WORKSPACE id: this thread is not about any one link, dashboard or design, and every capability the resource-scoped agents have is available from it. One conversation per workspace, so it survives navigation.

Allowed values

AGENT_CONTEXT_TYPE_UNSPECIFIED

AGENT_CONTEXT_TYPE_ANALYTICS_DASHBOARD

AGENT_CONTEXT_TYPE_WORKFLOW

AGENT_CONTEXT_TYPE_LINK

AGENT_CONTEXT_TYPE_QRCODE_DESIGN

AGENT_CONTEXT_TYPE_PAGE_THEME

AGENT_CONTEXT_TYPE_LINK_ANALYTICS

Building a link's analytics dashboard. context_id is the LINK id, not a

AGENT_CONTEXT_TYPE_LEAD_SCORE

A conversation about one visit and the lead score it produced. The context

AGENT_CONTEXT_TYPE_WORKSPACE

The workspace-wide assistant, with no resource selected. The context id is

message

string

The user's message

#Response

200

Everything worked as expected.

appliedActions

array<string>

contextUpdated

boolean

True if the agent modified the resource (frontend should refresh)

responseText

string

uiActions

array<object>

#Error response

400-599

All endpoints may return an unexpected error payload when a request cannot be processed.

error

objectRequired

Wrapped error response.

Example request (cURL)

curl -X POST "https://api.linkbreakers.com/v1/agent/message" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"contextId":"string","contextMetadata":"string","contextType":"AGENT_CONTEXT_TYPE_UNSPECIFIED","message":"string"}'

Sample payload (application/json)

{
  "contextId": "string",
  "contextMetadata": "string",
  "contextType": "AGENT_CONTEXT_TYPE_UNSPECIFIED",
  "message": "string"
}

Typical response

{
  "appliedActions": [
    "string"
  ],
  "contextUpdated": false,
  "responseText": "string",
  "uiActions": [
    {
      "label": "string",
      "options": [
        {}
      ],
      "type": "string",
      "value": "string"
    }
  ]
}

Base URL: https://api.linkbreakers.com

POST/v1/agent/uploadRequires auth

#Upload file for agent chat

Upload a file to attach to the next agent message. Returns a temporary file ID. Files expire after 5 minutes. Max 20MB.

#Parameters

This endpoint does not accept any parameters.

#Request body

content

string

File content (base64-encoded in JSON)

mimeType

string

MIME type (e.g. "image/png", "application/pdf")

name

string

Original filename

#Response

200

Everything worked as expected.

fileId

string

Temporary file ID to include in agent message attachments

mimeType

string

MIME type (echoed back)

name

string

Original filename (echoed back)

#Error response

400-599

All endpoints may return an unexpected error payload when a request cannot be processed.

error

objectRequired

Wrapped error response.

Example request (cURL)

curl -X POST "https://api.linkbreakers.com/v1/agent/upload" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"content":"string","mimeType":"string","name":"string"}'

Sample payload (application/json)

{
  "content": "string",
  "mimeType": "string",
  "name": "string"
}

Typical response

{
  "fileId": "string",
  "mimeType": "string",
  "name": "string"
}

Base URL: https://api.linkbreakers.com

DELETE/v1/agent/conversationRequires auth

#Clear agent conversation

Clear the conversation history for a specific context.

#Parameters

query parameters

contextType

stringquery

dashboard id — the dashboard does not exist yet while the user and the assistant are still agreeing on what it should show. Once it exists, editing it happens under AGENT_CONTEXT_TYPE_ANALYTICS_DASHBOARD instead. id is the EVENT id, not the link id: two visits to the same link are two different subjects, and sharing a thread between them lets one visitor's details bleed into answers about another. the WORKSPACE id: this thread is not about any one link, dashboard or design, and every capability the resource-scoped agents have is available from it. One conversation per workspace, so it survives navigation.

Allowed values

AGENT_CONTEXT_TYPE_LINK_ANALYTICS

Building a link's analytics dashboard. context_id is the LINK id, not a

AGENT_CONTEXT_TYPE_LEAD_SCORE

A conversation about one visit and the lead score it produced. The context

AGENT_CONTEXT_TYPE_WORKSPACE

The workspace-wide assistant, with no resource selected. The context id is

contextId

stringquery

#Response

200

Everything worked as expected.

No structured schema available for this section.

#Error response

400-599

All endpoints may return an unexpected error payload when a request cannot be processed.

error

objectRequired

Wrapped error response.

Example request (cURL)

curl -X DELETE "https://api.linkbreakers.com/v1/agent/conversation?contextType={contextType}&contextId={contextId}" \
  -H "Authorization: Bearer YOUR_TOKEN"

Typical response

{}

Base URL: https://api.linkbreakers.com