# Page Not Found

The URL `tools/tools-chinese/api-v7-sdk-v21-one-store-inapp-zhi-fu-shi-yong-zhi-nan-ji-xia-zai/inapp-zhi-fu-ce-shi-ji-an-quan-xing` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Interfaces_](https://onestore-dev.gitbook.io/dev/tools/alc/alc-v2-reference/interfaces_.md)
- [PNS(Payment Notification Service) 이용하기](https://onestore-dev.gitbook.io/dev/tools/billing/old-version/v19/pns-payment-notification-service.md)
- [PNS(Payment Notification Service)활용](https://onestore-dev.gitbook.io/dev/tools/billing/old-version/v17/pns-payment-notification-service.md)
- [V2 AppLicenseChecker](https://onestore-dev.gitbook.io/dev/tools/alc/alc-v2-reference/annotation/v2-applicensechecker.md)
- [외부결제 연동 규격 ](https://onestore-dev.gitbook.io/dev/tools/billing/old-version/billing_3rd-party.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/tools/alc/alc-v2-reference/interfaces_.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/tools/alc/alc-v2-reference/interfaces_.md`).

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