> 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/tdo-project-builder-user-guide/working-with-source-files/ingest-data.md). # Ingest Data TDO can upload .csv files. To import data files, go to the ‘Data Management’ section of the menu, and select ‘Ingest Data’. This will open a list of all files that have been imported in your project.

Ingest Data page

To import a new file, click on the plus sign in the lower right hand corner of the window. The ‘Upload Data’ window will open. On the top line, you will need to provide a name for your data block in TDO. Since the same file can be imported multiple times, the data block name is the unique name that TDO will use to manage this file. You can give it a new data block name, or you can use an existing data block name. If you use an existing data block name, TDO will find the most recent version and increase the version number accordingly. TDO will also perform a .csv validation on the file. If there are any errors that need to be fixed, these will show as red boxes in the upper right section of the window. If the file passes validation, a green box will show in the upper right corner.

Upload Data window

Some of the most common errors are in the column headers. As stated in the introduction to this guide, all TDO objects must adhere to JSON naming conventions. This means that all column headers must be lower case only, underscore instead of space, no special characters. Column headers must also not contain any leading spaces, and there cannot be any duplicate column names. Data rows are not subject to these rules. Once imported, the file name will be shown at the bottom of the list of uploaded files. Note that on this screen, the actual file name that was imported will be shown.

Imported file name displayed

--- # 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://docs.apica.io/platform-docs/test-data-orchestrator-tdo/user-documentation/tdo-project-builder-user-guide/working-with-source-files/ingest-data.md?ask=&goal= ``` `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.