> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/integrate/apis/asm-api-quick-reference-guide/search-for-existing-calls.md).
# Search for Existing Calls
## ASM API Quick Reference Guide
### Searching for Existing Calls
1. In Postman, select 'New' in the top left-hand corner.
2. Select HTTP from the dialogue window and give the request the name of **Get Call List**
3. Set the method to Get and the URL will be as follows, you have two options:
Option 1: use the system variable for your base system url: `{{SystemURLTest}}/alemba.api/api/v2/call`
Option 2: write the full base url: `https:////alemba.api/api/v2/call`
4. Click the Authorization tab.
5. Set **Type** as **No Auth**
6. Click **Headers** and add the following lines
Key
Value
Content-Type
Application/json
Authorization
Bearer {{Login_Token}}
{% hint style="danger" %}
1. **{{Login\_Token}}** is the name of the environment variable we created earlier. This can be replaced with the actual access\_token value obtained, e.g. Bearer awerff32h347hb4tgb34
2. The space between Bearer and the {{Login\_Token}}/access\_token is intentional and REQUIRED
{% endhint %}
3. Verify the Headers tab appears as follows
8. Send the request to get a list of calls. You will get a “results” array as per below. An array is a list of objects in JSON
OPTIONAL: You can now make a note of a call number from the result and update the CallRef variable by
1. Access Environments on left hand menu
2. Select your Environment
3. Fill a Current Value for Call Ref, as per below:
4. Click save in the top right hand corner of your screen, to save the new variable
---
# 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://docs.alemba.com/asm-hermes/integrate/apis/asm-api-quick-reference-guide/search-for-existing-calls.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.