# Get Determining Attribute Details
This can be run two ways – one will return all details for a single determining attribute, and the other will return details on all determining attributes in a project.
For the single attribute details, you need the attribute ID to run the API. So we will look at the ‘all determining attributes’ process first, as that will provide the determining attribute ID.
**Get all Details**
For returning details on all determining attributes, the API call is defined as POST (the same as for creating determining attributes.
URL for determining attribute details
The body of the message is very simple, just listing the credentials and the project.
```
{
"context": {
"user": "mbj_test",
"password": "xxxx",
"project": {
"name": "imp_payments_demo",
"version": "1.0"
}
}
}
```
The response in Postman shows the details for all determining attributes in this project.
Return messge with all attribute details
**Get Single Attribute Details**
We will use the first determining attribute (‘has\_app’) for the single determining attribute call. The ID for this attribute is 645e0000390613152b16ecbb. To set the call for a single determining attribute, it is defined as above, but with the attribute ID appended at the end of the call.
URL for single determining attribute details
The body of the message remains the same as the ‘all attributes’ call.
{
"context": {
"user": "mbj\_test",
"password": "xxxx",
"project": {
"name": "imp\_payments\_demo",
"version": "1.0"
}
}
}
And here you can see that the return message only has the details on the determining attribute we defined in the API.
Return message with single attribute details
---
# Agent Instructions: 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:
```
GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/api-guide/determining-attribute-apis/get-determining-attribute-details.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.