> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/brand-api-reference/reference/submissions.md). # Submissions The *Submissions* endpoint allows you to check on the statuses of any records you pass to impact.com via API (using the [Conversions endpoint](/brand-api-reference/reference/conversions/conversions.md)) or FTP. The *Submissions* endpoint will tell you if your submissions were received and will provide metadata (like `BatchIds`) about what was received. Information about records, like conversions, modifications, and disposition codes, can all be retrieved and viewed using this endpoint. The *Submissions* endpoint will also tell you if errors were discovered in the files you send to impact.com. If sending data via API, the error(s) will appear in the [API submission object](/brand-api-reference/reference/submissions/models.md). If sending data via FTP, you will need to use the [FTP submission error endpoint](/brand-api-reference/reference/submissions/ftp-submissions.md) to retrieve information about the exact errors discovered in an FTP batch file. impact.com **highly** recommends you keep backups of your submissions in case a submission was not able to be completed. --- # 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://integrations.impact.com/brand-api-reference/reference/submissions.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.