# Page Not Found

The URL `features/marketing/facebook-comment-pm/how-to-get-facebook-post-id` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [如何獲得 Facebook 貼文編號?](https://docs.omnichat.ai/features/marketing/facebook-instagram-tie-wen-hui-fu-2.0/how-to-get-facebook-post-id.md)
- [Facebook 訂閱定期通知（Facebook only）](https://docs.omnichat.ai/features/marketing/new-chatbot/facebook-ding-yue-ding-qi-tong-zhi-facebook-only.md)
- [Facebook / Instagram 貼文回覆 2.0](https://docs.omnichat.ai/features/marketing/facebook-instagram-tie-wen-hui-fu-2.0.md)
- [常見問題](https://docs.omnichat.ai/features/marketing/facebook-instagram-tie-wen-hui-fu-2.0/chang-jian-wen-ti.md)
- [輪播訊息](https://docs.omnichat.ai/features/marketing/new-chatbot/lun-bo-xun-xi.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.omnichat.ai/features/marketing/facebook-instagram-tie-wen-hui-fu-2.0/how-to-get-facebook-post-id.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.omnichat.ai/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.omnichat.ai/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., `/features/marketing/facebook-instagram-tie-wen-hui-fu-2.0/how-to-get-facebook-post-id.md`).

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