> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/marketplace-integrations/hybrid-api/offer-wall-api-integrations.md).

# Offer Wall API

Static Offers

Some channel partners prefer a lightweight integration with Engine’s marketplace that delivers offers without heavy engineering effort. To support this, Engine offers the ability to direct users into an Engine-hosted offer wall.

This integration type is **ideal for partners who are able to send lead data via API without having to build a frontend Offer Wall page themselves**, which allows partners to launch an integration quickly and speed up the timeline to realizing revenue, with a data-backed UX to maximize conversion rates.

This API lets partners send data via API and receive the Partner Page (PP) redirect URL without needing to build a custom front-end UX. Because offer details are returned in the API response, this also gives partners first-party visibility into each lead's offers, allowing you to store that data for monitoring, analytics, and optimization.


---

# 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://even-financial.gitbook.io/developer-center/marketplace-integrations/hybrid-api/offer-wall-api-integrations.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.