> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plato.ae/llms.txt
> Use this file to discover all available pages before exploring further.

# Internal Routes

> Routes that exist in Plato but are not public integration contracts.

Some Plato routes are visible in the codebase or browser network panel, but they are not supported public APIs.

Do not build customer integrations on these routes unless Plato Support explicitly tells you to.

## Internal Or Provider-Owned Routes

| Route family                | Why it is not a public integration contract                   |
| --------------------------- | ------------------------------------------------------------- |
| `/api/auth/...`             | Used for sign-in, sessions, and auth callbacks.               |
| `/api/webhook/...`          | Used by payment, messaging, delivery, or provider webhooks.   |
| `/api/cron/...`             | Used by scheduled platform jobs.                              |
| `/api/og/...`               | Used to render social preview and email images.               |
| `/api/pdf/...`              | Used by Plato to render PDFs from public document pages.      |
| `/api/pay`                  | Used as a payment provider callback/redirect handler.         |
| `/api/quickbooks/oauth/...` | Used by the QuickBooks app authorization flow.                |
| Console browser tRPC calls  | Used by the Plato Console UI and can change with the product. |

## Supported Alternatives

Use these documented APIs instead:

* [CMS API](/api-reference/cms/overview) for custom content.
* [Connect360 API](/api-reference/connect360/overview) for attachments and AI-assisted replies.
* [Menu Products](/api-reference/restaurant/menu-products) for restaurant catalog data.
* [Orders Feed](/api-reference/restaurant/orders-feed) for order export.
* [Forms](/api-reference/forms/get-form) for form rendering and responses.

## If You Need Something Else

If your integration needs a capability that is not documented, contact Plato Support with:

* The business goal.
* The records you need to read or write.
* Expected request volume.
* Whether the integration is server-side or browser-side.

Plato can confirm the right supported path or help plan a new endpoint.