> ## 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.

# Backend API overview

> Understand the unified request entry point, authentication model, and request structure of the ActionX Backend API.

The Backend API is best when you want to centralize ActionX requests on your server and then pass results to your frontend or other systems.

```mermaid theme={null}
flowchart LR
    backend["Your backend"] --> request["POST /api/v1/ads/request"]
    request --> ads["ads-server"]
    ads --> slots["Slot-based response"]
```

## Unified endpoint

```text theme={null}
POST /api/v1/ads/request
```

## What this endpoint does

* Accepts query, response, user context, and slots
* Enters the unified ActionX decisioning flow
* Returns a result structure that fits the requested slot format

## Authentication

```bash theme={null}
Authorization: Bearer ak_your_api_key
```

You can also use `X-API-Key`.

## Minimal request structure

```json theme={null}
{
  "conversationContext": {
    "query": "Recommend a lightweight office laptop",
    "response": "Here are a few options for work and travel."
  },
  "userContext": {
    "sessionId": "session-001",
    "userId": "user-001"
  },
  "slots": [
    {
      "slotId": "main-slot",
      "format": "action_card",
      "count": 3
    }
  ]
}
```

## Continue reading

<Columns cols={2}>
  <Card title="Request parameters" href="/backend-api/request-parameters">
    Continue into `userContext`, `slots`, and the most common fields.
  </Card>

  <Card title="Response format" href="/backend-api/response-format">
    Continue into slots, ads, and the common output structures.
  </Card>
</Columns>