> 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/element-repository-interface-and-functional-flow/about-the-import-apis-definition.md).
# About the Import APIs Definition
The Import APIs Definition feature allows you to automatically generate multiple APIs in the Element Repository from a provided API specification. Instead of manually configuring each request, Avo Assure analyzes the imported definition and creates the corresponding endpoints, significantly reducing setup time and ensuring consistency across large API collections.
This capability is particularly useful when working with services that expose multiple endpoints such as REST or SOAP based systems where rapid, bulk creation of APIs helps to accelerate API automation and testing.
You can import an APIs definition using the following options:
* **File**: Import APIs definition file directly from the local system. Only JSON file format is supported.
* **URL**: Import the APIs definition from a hosted location by specifying the definition URL.
## About the File Option
On the **Element Repository** page (Home > Select Project > Design Studio > Element Repository > Select Create Folder icon/Parent Folder (Ellipsis icon) > Import APIs Definition > File), you can do the following:
1. Import API Definition using File Option
* Allows you to upload a local Swagger or OpenAPI - Version 2.x / 3.x JSON definition file from their system.
* After the API definition file is uploaded, Avo Assure parses the file and automatically creates API elements in the repository based on the endpoints defined in the specification.
* This eliminates the need to configure each request manually and ensures the imported structure matches the original API contract.
## About the URL Option
You can use the URL option to import an API definition directly from a hosted link.
On the **Element Repository** page (Home > Select Project > Design Studio > Element Repository > Select Create Folder icon/Parent Folder (Ellipsis icon) > Import APIs Definition > URL), you can do the following:
1. Import API Definition using URL Option
* Allows you to upload a local Swagger or OpenAPI - Version 2.x / 3.x JSON definition file from their system.
* This method enables you to fetch the API specification using the definition URL provided in the **Source Label** text box.
* The Protocol dropdown identifies the service type, which can be automatically defined or manually selected as **WSDL** for SOAP APIs or **Swagger** for REST APIs.
* After the definition URL and protocol are configured, Avo Assure retrieves the API specification from the specified source and automatically generates the API elements in the Element Repository.
---
# 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.avoautomation.com/avo-assure/avo-assure-supported-technologies-for-automation/api-automation/element-repository-interface-and-functional-flow/about-the-import-apis-definition.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.