# Create Determining Attribute (Value-based)
This API can be used to create one determining attribute. The determining attribute can be sourced from an imported data block or can be standalone (meaning no data block source). The examples below show how the API should be laid out for each option.
**No Data Block Source**
In this API, the ‘entity’ values are passed to create a new determining attribute named “currency\_a”. Since there is no underlying data block, the entity source is not identified.
The API is still defined the same way as for a range-based determining attribute:
Determining attribute API
```
{
"context": {
"user": "mbj_test",
"password": "xxxx",
"project": {
"name": "imp_payments_demo",
"version": "1.0"
}
},
"entity": {
"name": "currency_a",
"dataType": "STRING",
"type": "VALUE",
"values": [
"USD", "GBP", "EUR"
]
}
}
```
The results screen from Postman shows the API was created.
Return message with details
An ID for the determining attribute is provided in the results section. If you are going to update or delete this determining attribute, you will need this ID. (Note that the ID can also be found in the ‘Get all DAs’ API.) This is the attribute in TDO after it has been created by API.
New determining atttribute, no data block source
**Data Block Used as Source**
The data block to be used as the source must already exist in TDO to run this API. It is the same as the API above, except that the entity.source .name and entity.source.version are also included in the API. You will want to link a determining attribute to an underlying data block if you intend to filter the attributes at a later date. This filtering is performed using the entity.criteria field.
The url is the same as for the no data block source API call. The body contains additional information.
{
"context": {
"user": "mbj\_test",
"password": "xxxx",
"project": {
"name": "imp\_payments\_demo",
"version": "1.0"
}
},
"entity": {
"name": "acct\_type",
"dataType": "STRING",
"type": "VALUE",
"values": \[
"Checking", "Savings", "Current"
],
"source": {
"name": "imp\_accounts",
"version": "1.0",
"attribute": "account\_type"
}
}
}
When this API is run, the results screen in Postman shows the following.
Return message with details
As with other successful calls, the ID for the new determining attribute is returned with the message.
In the TDO UI, the new determining attribute displays the linked data block and field (top portion of screen) in addition to the attribute values.
Determining attribute with data block source
---
# 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/create-determining-attribute-value-based.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.