> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/prerequisites.md). # Prerequisites The following requirements must be fulfilled before performing API Automation in Avo Assure: * **API Endpoint URL**: A valid endpoint URL for each API service that needs to be tested. * **Authentication Details**: Required credentials such as API keys, tokens, or login details for APIs that mandate authentication. * **HTTP Method**: Ensure you are familiar with standard HTTP methods such as GET, POST, PUT, and DELETE. * **Test Data Storage**: Ensure the required test data files are uploaded in a Segregated Avo Storage location so that you can be accessed during execution, if it is configured in the Avo Storage * **Form-Data File Upload Limit**: When you use the form-data body format, you can upload up to 50 files. Each file can have a maximum size of 20 MB, so the total file upload capacity is 1000 MB. * **Supported Form-Data File Upload formats**: txt, .csv, .log, .pdf, .doc, .docx, .xls, .xlsx, .json, .xml, .jpg, .jpeg, .png, .gif, .bmp, .svg, .jks, .zip --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.avoautomation.com/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/prerequisites.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.