> 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/retrieve-an-object.md).

# Retrieve an Object

The `GET /items/{nodeId}` endpoint retrieves a specific object stored in EPC. It supports various use cases such as:

* Duplicating IMS data to a third-party platform
* Displaying individual IMS objects in an external system or dashboard
* Creating targeted widgets or views for internal portals

***

## Quick Start

* **Base Endpoint URL**: <https://YOURIMS.interfacing.com/api/v1/items/{nodeId}>
* **Authentication**: Obtain a valid token (see [Authentication & Token Management](/interfacing-help-files/solutions-developers/api-and-information-repository/rest-apis.md#authentication-and-token-management))
* **Swagger Documentation**: <https://YOURIMS.interfacing.com/api/v1/swagger/#/Common/getItem>

***

## Request Example

```bash
curl --request GET --url 'http://myepc.interfacing.com/api/v1/items/1450CEF9-89A3-4B48-98F7-09735BECD54B?draft=true' -b /tmp/cookie.tmp
```

***

## Response Example

```java
public <T extends NodeElement> Mono<T> findElement(@NotNull String nodeId, Class<T> clazz) {
        return bpcClient.get()
                .uri(uriBuilder -> uriBuilder.path("/items/{nodeId}").queryParams(defaultQueryParams).queryParam("detail", true).build(nodeId))
                .retrieve()
                .bodyToMono(new ParameterizedTypeReference<>() {
                });
    }
```

***

## Retrieving a Specific Object by Type

Replace `{objectId}` (e.g., `/capabilityId`, `/controlId`, `/documentId`) in the endpoint URL below with the actual object's ID number, which you can find <mark style="color:red;">WHERE?</mark>

| Object Type             | Swagger URL                                                                  | Endpoint URL                                                                         |
| ----------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Capability              | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Capability/findCapability> | <https://YOURIMS.interfacing.com/api/v1/capabiltity/capabilities/capabilityId>       |
| Collaboration Post      | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Collaboration/findPost>    | <https://YOURIMS.interfacing.com/api/v1/collaboration/posts/postId>                  |
| Control                 | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Control/findControl>       | <https://YOURIMS.interfacing.com/api/v1/control/controls/controlId>                  |
| Document                | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Document/findDocument>     | <https://YOURIMS.interfacing.com/api/v1/document/documents/documentId>               |
| Term (Glossary)         | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Glossary/findTerm>         | <https://YOURIMS.interfacing.com/api/v1/glossary/tems/termId>                        |
| Attribute (Master Data) | <https://YOURIMS.interfacing.com/api/v1/swagger/#/MasterData/findAttribute>  | <https://YOURIMS.interfacing.com/api/v1/masterData/attributes/attributeId>           |
| Entity (Master Data)    | <https://YOURIMS.interfacing.com/api/v1/swagger/#/MasterData/findEntity>     | <https://YOURIMS.interfacing.com/api/v1/masterData/entities/entityId>                |
| Asset (Organization)    | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Organization/findAsset>    | <https://YOURIMS.interfacing.com/api/v1/organization/assets/assetId>                 |
| Resource (Organization) | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Organization/findResource> | <https://YOURIMS.interfacing.com/api/v1/swagger/#/organization/resources/resourceId> |
| Role (Organization)     | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Organization/findRole>     | <https://YOURIMS.interfacing.com/api/v1/swagger/#/organization/roles/roleId>         |
| Indicator (Performance) | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Performance/findIndicator> | <https://YOURIMS.interfacing.com/api/v1/performances/indicators/indicatorId>         |
| Process                 | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Process/findProcess>       | <https://YOURIMS.interfacing.com/api/v1/process/processes/processId>                 |
| Risk                    | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Risk/findRisk>             | <https://YOURIMS.interfacing.com/api/v1/risk/risks/riskId>                           |
| Rule                    | <https://YOURIMS.interfacing.com/api/v1/swagger/#/Rule/findRule>             | <https://YOURIMS.interfacing.com/api/v1/rule/rules/ruleId>                           |

***

## What is this feature in IMS?

**IMS objects** are the individual items stored within the IMS web application. These include folders and various content types such as roles, terms, documents, rules, and more.&#x20;

All objects are organized in the <mark style="color:red;">**Library**</mark>, each under a specific **parent root** based on its type, such as the Glossary root for terms or the Organization root for roles.

Objects can be retrieved either **individually by their ID** or as part of a [**list**](/interfacing-help-files/solutions-developers/api-and-information-repository/rest-apis/use-cases-and-examples/retrieve-a-list-of-objects.md), allowing users and integrated systems to efficiently access and work with large sets of data.

***

## See Also

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Authentication &#x26; Token Management</td><td><a href="/interfacing-help-files/solutions-developers/api-and-information-repository/rest-apis.md#authentication-and-token-management">REST APIs</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FLfvkwix26vW3CnepEMTv%2FIMS-V16-NAV-Home-Icons-5.png?alt=media&amp;token=4244c676-38ac-4218-8552-680a3ac1dcdc">IMS-V16-NAV-Home-Icons-5.png</a></td></tr><tr><td>API Reference (Swagger)</td><td><a href="/interfacing-help-files/solutions-developers/api-and-information-repository/rest-apis/api-reference-swagger.md">API Reference (Swagger)</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FuIm0jP36LBJWUKIgHGxl%2FIMS-V16-NAV-Library-Icons-41.png?alt=media&amp;token=a91c1498-c99a-4013-b6bd-5877df0a71bb">IMS-V16-NAV-Library-Icons-41.png</a></td></tr><tr><td>How to Perform Other Use Cases</td><td><a href="/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</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F5Aeu2y0v898h8TlT2GMk%2FIMS-V16-Intro-7.png?alt=media&amp;token=4c09eacd-abdd-44d1-b318-8d6dbb4a11b1">IMS-V16-Intro-7.png</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 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/retrieve-an-object.md?ask=<question>&goal=<endgoal>
```

`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.