# Page Not Found

The URL `tools/tools/v21/references/annotations/purchasedata.recurringstate` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [PurchaseData.RecurringState](https://onestore-dev.gitbook.io/dev/cht/tools/billing/v21/references/annotations/purchasedata.recurringstate.md)
- [PurchaseData.PurchaseState](https://onestore-dev.gitbook.io/dev/cht/tools/billing/v21/references/annotations/purchasedata.purchasestate.md)
- [PurchaseData.AcknowledgeState](https://onestore-dev.gitbook.io/dev/cht/tools/billing/v21/references/annotations/purchasedata.acknowledgestate.md)
- [PurchaseClient.RecurringAction](https://onestore-dev.gitbook.io/dev/cht/tools/billing/v21/references/annotations/purchaseclient.recurringaction.md)
- [PurchaseClient.ConnectionState](https://onestore-dev.gitbook.io/dev/cht/tools/billing/v21/references/annotations/purchaseclient.connectionstate.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://onestore-dev.gitbook.io/dev/cht/tools/billing/v21/references/annotations/purchasedata.recurringstate.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://onestore-dev.gitbook.io/dev/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://onestore-dev.gitbook.io/dev/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., `/dev/cht/tools/billing/v21/references/annotations/purchasedata.recurringstate.md`).

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