> For the complete documentation index, see [llms.txt](https://docs.simplio3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplio3d.com/api-reference/open-api/vectors.md).

# Vectors

#### Managing SVG Files with Simplio3D OpenAPI

Simplio3D OpenAPI provides robust tools for managing vector graphics, such as SVG files, through GET endpoints. This process is analogous to handling Textures, allowing for efficient asset management and seamless integration into your 3D applications.

**Key Endpoints**

* **GET /vectors**: Retrieve a list of all SVG files available in the system. This can be filtered to match specific criteria, improving resource management.
* **GET /vectors/{id}**: Fetch a specific SVG file by its unique identifier. This allows for precise extraction of the required vector asset for your application.

**Benefits**

* **Scalability**: Manage a large number of SVG assets efficiently.
* **Flexibility**: Easily fetch and integrate vectors into 3D scenes.
* **Consistency**: Ensure uniform handling of graphics similar to textures.

For further details, refer to the Simplio3D API documentation to explore additional features and functionalities.


---

# 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.simplio3d.com/api-reference/open-api/vectors.md?ask=<question>&goal=<endgoal>
```

`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.