> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference.md).

# Integrations and Technical Reference

Use this section to build integrations and extend Birds Document Warehouse. Tenant administration, Dynamics 365 configuration, and Approval Dashboard setup are documented in [Setup and Configuration](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration.md).

## Integration interfaces

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>MCP Server</strong></td><td>Connect AI assistants to Document Warehouse capabilities.</td><td><a href="https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/mcp-server.md">MCP Server</a></td></tr><tr><td><strong>API Guide</strong></td><td>Authentication, document queries, tags, and Postman examples.</td><td><a href="https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/api-guide.md">API Guide</a></td></tr><tr><td><strong>Power Platform &#x26; Logic Apps</strong></td><td>Connect Document Warehouse operations to automation flows.</td><td><a href="https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/power-platform-and-logic-apps.md">Power Platform &amp; Logic Apps</a></td></tr></tbody></table>

The live [Swagger documentation](https://raptor.9altitudes.com/apigateway/swagger) describes available endpoints and request formats.

## Development reference

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Embedding Raptor</strong></td><td>Embed Document Warehouse in another application.</td><td><a href="https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/embedding-raptor.md">Embedding Raptor</a></td></tr><tr><td><strong>SharePoint Storage Provider</strong></td><td>Storage-provider development reference.</td><td><a href="https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/sharepoint-storage-provider.md">SharePoint Storage Provider</a></td></tr><tr><td><strong>D365 Finance &#x26; Operations</strong></td><td>Technical extension points for document, input, output, and process management.</td><td><a href="https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/d365-finance-and-operations.md">D365 Finance &amp; Operations</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
