# Page Not Found

The URL `affiliates/change-the-affiliate-program-of-an-affiliate` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [9. How do I manage affiliate applications and approvals?](https://docs.afflr.io/frequently-asked-questions/9.-how-do-i-manage-affiliate-applications-and-approvals.md)
- [Affiliate Portal (Customer Account)](https://docs.afflr.io/widgets/affiliate-portal-customer-account.md)
- [12. How will affiliates access their affiliate link or code?](https://docs.afflr.io/frequently-asked-questions/12.-how-will-affiliates-access-their-affiliate-link-or-code.md)
- [6. How to pay the affiliate?](https://docs.afflr.io/frequently-asked-questions/6.-how-to-pay-the-affiliate.md)
- [13. How do you enable the Afflr Sales tag for your affiliate orders?](https://docs.afflr.io/frequently-asked-questions/13.-how-do-you-enable-the-afflr-sales-tag-for-your-affiliate-orders.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

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

```
GET https://docs.afflr.io/frequently-asked-questions/9.-how-do-i-manage-affiliate-applications-and-approvals.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.

### Option 2 — Browse the documentation index

Full index: https://docs.afflr.io/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.afflr.io/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/frequently-asked-questions/9.-how-do-i-manage-affiliate-applications-and-approvals.md`).

You may also use `Accept: text/markdown` header for content negotiation.