# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Agent Booking - Customer Journey](https://tripins.saladin.vn/api-document-for-embedded-trip-insurance/agent-booking-customer-journey.md)
- [End User Booking - Customer Journey](https://tripins.saladin.vn/api-document-for-embedded-trip-insurance/end-user-booking-customer-journey.md)
- [Claim Flow](https://tripins.saladin.vn/api-document-for-embedded-trip-insurance/claim-flow.md)
- [API #01 - Calculate Premium v1](https://tripins.saladin.vn/api-document-for-embedded-trip-insurance/api-details/the-older-version-apis/api-01-calculate-premium-v1.md)
- [API Details](https://tripins.saladin.vn/api-document-for-embedded-trip-insurance/api-details.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://tripins.saladin.vn/api-document-for-embedded-trip-insurance/agent-booking-customer-journey.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://tripins.saladin.vn/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://tripins.saladin.vn/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., `/api-document-for-embedded-trip-insurance/agent-booking-customer-journey.md`).

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