# Page Not Found

The URL `integrations-and-api-development/integration-best-practices/api-key-authentication-for-the-partner-api` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [API Key Authentication for the Partner API](https://docs.360dialog.com/partner/onboarding/integration-best-practices/api-key-authentication-for-the-partner-api.md)
- [Architecture and Security](https://docs.360dialog.com/partner/onboarding/integration-best-practices/architecture-and-security.md)
- [Sizing Your Environment Based on Expected Throughput](https://docs.360dialog.com/partner/onboarding/integration-best-practices/sizing-your-environment-based-on-expected-throughput.md)
- [Design a Resilient Message Sending Service](https://docs.360dialog.com/partner/onboarding/integration-best-practices/design-a-resilient-message-sending-service.md)
- [Zero-Tap Authentication Templates](https://docs.360dialog.com/partner/messaging/template-messages/authentication-templates/zero-tap-authentication-templates.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/partner/onboarding/integration-best-practices/api-key-authentication-for-the-partner-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.360dialog.com/partner/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/partner/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., `/partner/onboarding/integration-best-practices/api-key-authentication-for-the-partner-api.md`).

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