> For the complete documentation index, see [llms.txt](https://ask-clio.gitbook.io/ask-clio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/integrations-add-your-own-apis.md).
# Integrations: Add your own APIs
The Integrations tab lets you specify API endpoints for Clio to consider when deciding how to respond to a user query.
Step 1: Select the "Add API" button to get started.
Step 2: Name the tool and describe how it should be used.
Step 3: Add the API endpoint and request type, as well as any fixed (static) parameters or headers used in the call.
Step 5: Create the tool when you’ve populated all the static fields.
Step 6: Add parameters (Data Inputs) Clio will be responsible for populating. Clio will attempt to fill these based on the conversation.
* The "value" is the desciption provided to the model, so be precise on what should be included.
* If you have added Dynamic Inputs, like your client ID, you can use securely here.
Note: Data Inputs can parameterize either the API call parameters.\
e.g.
Note: Data Inputs can parameterize the URL path itself. In this case you must demarcate parameter name by curly brace\
e.g.
Testing: Test the API call with an input parameter and verify that the tool is set up correctly.
Setting it live: Enable the tool to allow Clio to have access to it.
Don't forget to save any changes!
> **Note on Dynamic Inputs vs User Identity**
>
> Dynamic Inputs are intended for **resource or account identifiers** (for example, a clearing account ID, portfolio ID, or internal resource ID).
>
> Do not use Dynamic Inputs as a replacement for `user.id`.\
> `user.id` should always represent your application’s internal user identifier when creating session tokens.
**Read-only by default**\
By default, all Clio integrations are retrieval-only (GET-based). Clio does not perform user actions or destructive operations (e.g. trades, account modifications) unless explicitly configured by the client.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/integrations-add-your-own-apis.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
