> For the complete documentation index, see [llms.txt](https://sdk-doc.tyrads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk-doc.tyrads.com/flutter/initialization/deeplinking-routes.md).

# Deeplinking Routes

**Min SDK version required: v1.1.4**

The Tyrads SDK supports deeplinking to specific sections of the offerwall. When initializing or interacting with the SDK, you can specify a route to open a particular page. For campaign-specific routes, you'll need to provide the campaignID as well.

| Route Name                                                     | Constant                         | Description                                            |
| -------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------ |
| `offers`                                                       | `TyradsDeepRoutes.OFFERS`        | Main campaigns list (Default)                          |
| `active-offers`                                                | `TyradsDeepRoutes.ACTIVE_OFFERS` | User's activated campaigns                             |
| `offers/`<mark style="color:$warning;">`[campaign-id]`</mark>  | `TyradsDeepRoutes.OFFERS`        | Specific campaign details (Requires `campaignID`)      |
| `support/`<mark style="color:$warning;">`[campaign-id]`</mark> | `TyradsDeepRoutes.SUPPORT`       | Support tickets for a campaign (Requires `campaignID`) |

Available routes and their usage:

* `offers` - opens the Campaigns Page
* `active-offers` - opens the Activated Campaigns Page
* `offers/`<mark style="color:$warning;">`[campaign-id]`</mark> - opens the Campaign Details Page (requires campaignID)
* `support/`<mark style="color:$warning;">`[campaign-id]`</mark> - opens the Campaign Tickets Page (requires campaignID)

```dart
// Note: CAMPAIGNS is the default route when no specific route is provided
await Tyrads.instance.showOffers();

// Explicitly specifying the Campaigns Page
await Tyrads.instance.showOffers(route: "offers");
//or use TyradsDeepRoutes class to avoid typos
await Tyrads.instance.showOffers(route: TyradsDeepRoutes.OFFERS);

// Activated Campaigns Page
await Tyrads.instance.showOffers(route: "active-offers");
// or using TyradsDeepRoutes class like
await Tyrads.instance.showOffers(route: TyradsDeepRoutes.ACTIVE_OFFERS);

// Campaign Details Page (requires campaignID)
await Tyrads.instance.showOffers(route: "offer", campaignID: "your_campaign_id_here");
// or using TyradsDeepRoutes class like
await Tyrads.instance.showOffers(route: TyradsDeepRoutes.OFFER, campaignID: "your_campaign_id_here");

// Campaign Tickets Page (requires campaignID)
await Tyrads.instance.showOffers(route: "support", campaignID: "your_campaign_id_here");
// or using TyradsDeepRoutes class like
await Tyrads.instance.showOffers(route: TyradsDeepRoutes.SUPPORT, campaignID: "your_campaign_id_here");
```


---

# 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://sdk-doc.tyrads.com/flutter/initialization/deeplinking-routes.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.