> ## Documentation Index
> Fetch the complete documentation index at: https://docs.actionx.top/llms.txt
> Use this file to discover all available pages before exploring further.

# Response format

> Review the ActionX Backend API response structure and its common output formats.

This page helps you read the response in two layers: first the slot, then the concrete content returned inside each slot.

```mermaid theme={null}
flowchart LR
    response["Response"] --> requestId["requestId"]
    response --> slots["slots"]
    slots --> ads["ads"]
    ads --> card["action_card"]
    ads --> suffix["suffix"]
    ads --> entity["entity_link"]
```

## Basic structure

```json theme={null}
{
  "requestId": "req_abc123",
  "slots": [
    {
      "slotId": "main-chat",
      "ads": [
        {
          "id": "ad_xyz789",
          "type": "action_card"
        }
      ]
    }
  ]
}
```

## How to read it

* `requestId`: The trace identifier for this request
* `slots`: One result container for each position you requested
* `ads`: The actual monetization results you need to render or consume

## Common output formats

### Action Card

* Typical elements: title, description, image, brand, CTA, and tracked click link
* Common scenarios: chat recommendation areas, result blocks, and product cards

### Suffix

* Typical elements: lightweight supporting copy and a jump link
* Common scenarios: answer tails and low-friction enhancement placements

### Entity Link

* Typical elements: an enhanced entity link inside the main body text
* Common scenarios: natural in-text enhancement

## Recommendation

Before you start building frontend rendering, make sure `requestId`, `slotId`, and the returned format all work correctly in logs or a debug panel. It will make troubleshooting much faster.