Skip to main content

​
Developer Center

The Vantr Developer Center lives on api.vantr.ai. It is the first-class home for external builders who only need the public API, while app.vantr.ai remains the business web application and vantr.ai remains the marketing site.
Treat the Developer Center as product UI. A developer should be able to sign in, create credentials, read docs, test safely, generate clients, and inspect usage without needing the business app navigation.

​
Host model

​
Developer Center map

Portal

Authenticated workspace for OAuth applications, client secrets, redirect URIs, scopes, request activity, and webhooks.

Docs

Human-readable guides for quickstart, authentication, conventions, errors, scopes, catalog workflows, and operations.

Reference

Generated endpoint reference from the public v2 OpenAPI source of truth.

OpenAPI

Machine-readable contract for typed clients, API explorers, MCP tools, and integration tests.

AI tools

llms.txt, skill.md, MCP search, and agent instructions that point tools at the same supported contract.

Sandbox

Dedicated safe account path for testing lifecycle-sensitive writes before production access.

​
Public API lanes

Organize the API around jobs developers perform:
  • Products and variations: create, update, archive, and organize sellable catalog records.
  • Categories and tags: manage category trees, subcategories, and tenant-defined tags such as Organic or SNAP/EBT.
  • Bills: ingest and retrieve bill data with constrained CRUD rules that protect accounting state.
  • Draft orders: create and modify draft-state orders; paid orders cannot be deleted through the API.
  • Payments: append-only payment creation tied to an order; created payments are one-and-done.
  • Webhooks and usage: inspect request history, usage, and event delivery without leaving the API host.

​
Experience principles

1

Start with a working path

The first viewport should route developers to quickstart, reference, OAuth applications, sandbox, and OpenAPI without marketing detours.
2

Keep docs and console connected

Endpoint pages should link back to the portal for the matching scopes, credentials, request history, and sandbox state.
3

Use OpenAPI as the source of truth

Reference pages, SDK starters, MCP tooling, Postman collections, and contract tests should all flow from the public v2 spec.
4

Document lifecycle rules directly

Bills, orders, and payments need explicit write limits, immutable states, idempotency guidance, and examples for failed state transitions.
5

Make AI support first class

Keep /openapi/v2.json, /llms.txt, /llms-full.txt, /skill.md, and /mcp easy to discover so agents use supported public surfaces.

​
Provider stance

Mintlify can continue to serve as the bridge for current docs and generated reference pages. The long-term product decision is different: Vantr owns the Developer Center experience, and docs tooling supports that experience rather than defining it.