# Create Coverage Set
The first action to take on coverage sets is to create a new coverage set. This can be done for one or more determining attributes. The call is set up as a POST call.
Create coverage set API call
The body of the call contains the project name and version and credentials in the ‘context’ section. In the entity section, you provide the name of the coverage set you are creating (it must end with ‘\_coverage’) and the determining attribute name(s)/version(s) you want to include.
```
{
"context": {
"user": "mbj_test",
"password": "xxxx",
"project": {
"name": "imp_payments_demo",
"version": "1.0"
}
},
"entity": {
"name": "api_demo_coverage",
"determiningAttributes": [
{"name": "acct_type", "version": "1.0"},
{"name": "has_app", "version": "1.0"},
{"name": "has_online", "version": "1.0"},
{"name": "balance", "version": "1.0"}
]
}
}
```
When this is run, a successful return message will show the return code (200) as well as the information on the coverage set created by this call.
Create coverage set return message
When the coverage set is viewed in the TDO UI, you can see the determining attributes linked to this set.
Coverage set contents in TDO
---
# 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/coverage-set-apis/create-coverage-set.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.