> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/solutions-developers/api-and-information-repository/rest-apis/use-cases-and-examples/how-to-perform-other-use-cases.md).
# How to Perform Other Use Cases
If your desired use case isn’t covered in this documentation, you can identify the relevant API calls by following these general steps:
{% stepper %}
{% step %}
### Log in to your IMS
Ensure you're authenticated with a user who has the necessary permissions to perform the action you're targeting.
{% endstep %}
{% step %}
### Open your browser's Developer Tools
Use the **Network** tab to monitor all outgoing API requests and incoming responses.
{% endstep %}
{% step %}
### Perform the desired action in the IMS interface
For example, navigate to a process, update an item, or trigger a specific workflow. Whatever matches your use case.
{% endstep %}
{% step %}
### Inspect the API calls
Review the network requests related to the action. Note:
* The **API endpoint** being called
* The **HTTP method** used (e.g., GET, POST, PUT, DELETE)
* The **request body or parameters**
* The **response payload**
{% endstep %}
{% step %}
### Optionally, find the corresponding endpoint in Swagger
Open the Swagger documentation and locate the endpoint to confirm request structure and usage details.
{% endstep %}
{% step %}
### Implement the request in your integration
Use your preferred method (CURL, Java, Python, etc.) to replicate the call with the appropriate authentication and parameters.
{% endstep %}
{% endstepper %}
***
## See Also
---
# 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://interfacing.gitbook.io/interfacing-help-files/solutions-developers/api-and-information-repository/rest-apis/use-cases-and-examples/how-to-perform-other-use-cases.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.
