# Page Not Found

The URL `waba-basics/waba-integration/step-to-step-to-move-to-cloud-api/will-be-deprecated-waba-integration-on-premise` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Using Session Initiation Protocol](https://docs.360dialog.com/docs/messaging/calling/how-to-configure-calling-api/using-session-initiation-protocol.md)
- [Receive WhatsApp Payments via Stripe](https://docs.360dialog.com/docs/messaging/payments/payments-singapore-only/receive-whatsapp-payments-via-stripe.md)
- [Migrate a phone number to a new WABA](https://docs.360dialog.com/docs/hub/migrations/migrate-a-phone-number-to-a-new-waba.md)
- [One-Tap Autofill Authentication Templates](https://docs.360dialog.com/docs/resources/authentication-messages/autofill-button-authentication-templates.md)
- [Migrate to alternate BSP](https://docs.360dialog.com/docs/hub/migrations/migrate-to-alternate-bsp.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.360dialog.com/docs/messaging/calling/how-to-configure-calling-api/using-session-initiation-protocol.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.360dialog.com/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.360dialog.com/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., `/docs/messaging/calling/how-to-configure-calling-api/using-session-initiation-protocol.md`).

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