> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/partner-api-reference/partner-v15/reference/actions.md).

# Actions

The [action](/partner-api-reference/partner-v15/reference/actions/models.md) object represents a conversion event that has been credited to you and is eligible for a payout. The actions object itself contains three main types of information:

1. Details about the conversion event itself (e.g., `OrderId`)
2. Details about the winning click (e.g., `AdId`)
3. Details about the payout calculated by the impact.com system (e.g., `Payout`)

An action may contain 1 or more [items](/partner-api-reference/partner-v15/reference/actions/models.md). Items within an action typically represent individual products that are a part of the conversion event. For instance, if you referred traffic for a retail sale, the items could be each type of product purchased by the customer. If you referred traffic for subscriptions, the item could represent the subscription level a customer signed up for.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.impact.com/partner-api-reference/partner-v15/reference/actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.