> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/api-guide/reporting-apis/data-assembly-summary.md).
# Data Assembly Summary
This call is run as a GET. It uses the same three parameters as the other reporting API’s but uses two additional ones – projectname and projectversion. If these parameters are used, you must use both of them.
This call returns a data assembly summary, including how many rows were generated and how many rows had errors. If the ‘errors’ indicator is ‘\[ ]’ then there were no errors detected during data assembly.
If there were errors, it includes information on the rows that contained errors and the number of errors per row.
This result is for the project ‘mug\_test\_project 1.0’ and returned no errors.
Data Assembly Summary with no errors in automation tool
For a data assembly that included errors, the partial return information is shown below.
Data Assembly Summary with errors shown in automation tool
This assembly contained 12 rows with errors. The error message and resulting data for the first row are also shown (the full error report for this assembly contains the error message for each row in similar detail).
---
# 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:
```
GET https://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/api-guide/reporting-apis/data-assembly-summary.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.