# Page Not Found

The URL `files/TgFpxEWm5M0ioS6FYZw7` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Getting Started with EWB GSP API](https://docs.cleartax.in/cleartax-docs/e-waybill-gsp-api/getting-started-with-gsp-ewb-api.md)
- [Getting Started with Max ITC API](https://docs.cleartax.in/cleartax-docs/max-itc-api/getting-started-with-max-itc-api.md)
- [Getting Started with EINV GSP API](https://docs.cleartax.in/cleartax-docs/e-invoicing-gsp-api/getting-started-with-einv-gsp-api.md)
- [Migrating from Karvy EWB GSP](https://docs.cleartax.in/cleartax-docs/e-waybill-gsp-api/migrating-from-karvy-ewb-gsp.md)
- [How to get the SSL certificate of a host?](https://docs.cleartax.in/cleartax-docs/general/how-to-get-the-ssl-certificate-of-a-host.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.cleartax.in/cleartax-docs/e-waybill-gsp-api/getting-started-with-gsp-ewb-api.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.cleartax.in/cleartax-docs/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.cleartax.in/cleartax-docs/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., `/cleartax-docs/e-waybill-gsp-api/getting-started-with-gsp-ewb-api.md`).

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