# Page Not Found

The URL `technical-specifications/corppass-authorization-api/key-concepts/proof-key-of-code-exchange-pkce` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Proof Key of Code Exchange (PKCE)](https://docs.corppass.gov.sg/technical-specifications/technical-concepts/proof-key-of-code-exchange-pkce.md)
- [Authorization Code with Proof Key of Code Exchange (PKCE) Flow](https://docs.corppass.gov.sg/technical-specifications/corppass-authorization-api-legacy/endpoints/authorization-endpoint/authorization-code-with-proof-key-of-code-exchange-pkce-flow.md)
- [Token Endpoint](https://docs.corppass.gov.sg/technical-specifications/corppass-authorization-api-legacy/endpoints/token-endpoint.md)
- [Well-known Endpoints](https://docs.corppass.gov.sg/technical-specifications/corppass-authorization-api-legacy/endpoints/well-known-endpoints.md)
- [Authorization Info Endpoint](https://docs.corppass.gov.sg/technical-specifications/corppass-authorization-api-legacy/endpoints/authorization-info-endpoint.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.corppass.gov.sg/technical-specifications/technical-concepts/proof-key-of-code-exchange-pkce.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.corppass.gov.sg/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.corppass.gov.sg/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., `/technical-specifications/technical-concepts/proof-key-of-code-exchange-pkce.md`).

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