> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/liveintent/api.md).

# API

{% hint style="warning" %}
This section is intended for developers utilizing our APIs to add channels.
{% endhint %}

Below you will find the keys to generate secret payloads for adding or updating a channel via the [Script API](https://docs.edgetag.io/api/api/script).

Refer to the [onboarding](/channels/liveintent/onboarding.md) for detailed information on the purpose and usage of each input.

### LIVE\_INTENT\_IGNORE\_LOADED <a href="#liveintentignoreloaded" id="liveintentignoreloaded"></a>

Used to store your preference if you want to ignore the load check for Live Intent SDK and fire Purchase Event anyways.&#x20;

**Possible values**\
1 or 0

**Type**\
CHECKBOX

**Optional**\
true

### LIVE\_INTENT\_APP\_ID <a href="#liveintentappid" id="liveintentappid"></a>

Use for storing the App ID that identifies your LiveIntent application for Purchase event tracking. This ID is provided by your designated LiveIntent representative.

**Example value**

```
b-11x6
```

**Type**\
IDENTIFIER

**Optional**\
false

### LIVE\_INTENT\_ACCESS\_TOKEN <a href="#liveintentaccesstoken" id="liveintentaccesstoken"></a>

Use for storing the Access Token that authenticates EdgeTag's server when sending events to LiveIntent. This token is generated by LiveIntent for secure API communication.

**Example value**

```
GPKKF%#Zh7@U_zz%-e{$/2uPrfBC4=i6
```

**Type**\
PASSWORD

**Optional**\
false

### LIVE\_INTENT\_PIXEL\_ID <a href="#liveintentpixelid" id="liveintentpixelid"></a>

Use for storing the Pixel ID that identifies your specific tracking pixel within the LiveIntent platform for conversion tracking purposes

**Example value**

```
36452
```

**Type**\
TEXT

**Optional**\
false


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/liveintent/api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.