# Page Not Found

The URL `reports/completed-donations/finding-ticket-and-guest-information` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Finding Ticket & Guest Information](https://docs.paybee.io/home/guides/reports-and-analytics/completed-transactions/finding-ticket-and-guest-information.md)
- [In-Person Event Creation](https://docs.paybee.io/home/events/in-person-events/in-person-event-creation.md)
- [Managing Tickets and Guests](https://docs.paybee.io/home/resources/ticketing-and-registration-guide/tickets-and-guests.md)
- [Introducing the New Campaign Creation & Configuration Experience](https://docs.paybee.io/home/resources/general-campaign-settings/introducing-the-new-campaign-creation-and-configuration-experience.md)
- [Understanding Ticketing On PayBee](https://docs.paybee.io/home/resources/ticketing-and-registration-guide/understanding-ticketing-on-paybee.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 documentation index with the `ask` parameter:

```
GET https://docs.paybee.io/home/guides/reports-and-analytics/completed-transactions/finding-ticket-and-guest-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.paybee.io/home/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.paybee.io/home/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., `/home/guides/reports-and-analytics/completed-transactions/finding-ticket-and-guest-information.md`).

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