canonical: https://jentic.com/apis/veeqo.com/veeqo

# Veeqo API

Veeqo inventory and order management API for managing orders, products, customers, warehouses, shipments, and more. The API exposes 50 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create order, list orders. Covers 50 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create order
- List orders
- Get order
- Update order
- Delete order

## Use cases

### E-Commerce Operations

Use the Veeqo API to perform e commerce operations programmatically. The API provides 50 endpoints covering core functionality including create order, list orders, get order.

Example prompt: Call POST /orders to create order

### Automated Allocations Management

Automate allocations operations by combining multiple Veeqo API endpoints. Agents can list orders and then get order in a single workflow.

Example prompt: Call GET /orders to list orders, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Veeqo API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create order', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/orders` | Create order |
| GET | `/orders` | List orders |
| GET | `/orders/{id}` | Get order |
| PUT | `/orders/{id}` | Update order |
| DELETE | `/orders/{id}` | Delete order |
| POST | `/products` | Create product |
| GET | `/products` | List products |
| GET | `/products/{id}` | Get product |

## Key resources

- **Allocations** — Operations for allocations
- **Company** — Operations for company
- **Customers** — Operations for customers
- **Delivery_Methods** — Operations for delivery_methods
- **Orders** — Operations for orders

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/veeqo.com/veeqo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Veeqo API by hand means setting its x-api-key header against api.veeqo.com and coding each order and product operation yourself. Through Jentic you install once, import the Veeqo API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Veeqo puts the order and product ids in the URL path (`/orders/{id}`, `/products/{id}`), so a rule can pin your agent to one order or product. You choose the operations it may call, so destructive ones like deleting an order are not included unless you add them.
- **Credential handling:** Your Veeqo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an order' or 'list products', and Jentic returns the matching Veeqo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Veeqo API use?

The Veeqo API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create order with the Veeqo API?

Yes. Use the POST /orders endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Veeqo API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create order through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create order'. Jentic returns the matching Veeqo API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Veeqo API have?

The Veeqo API exposes 50 endpoints covering allocations, company, customers operations.

### Can I limit what my agent is allowed to do with the Veeqo API?

Yes. Because you self-host Jentic One, your own rules decide which Veeqo operations the agent may call, so you can allow read and create actions like GET /orders and POST /orders while excluding destructive ones such as DELETE `/orders/{id}` unless you add them. Since Veeqo carries the order and product ids in the URL path (`/orders/{id}`, `/products/{id}`), a rule can pin the agent to a single order or product rather than the whole account. The Veeqo API key is held by your own instance and injected only for the operations you have permitted.