## Terms and Definitions Throughout this document and the Velo platform the following terms are used: * **Payor.** An entity (typically a corporation) which wishes to pay funds to one or more payees via a payout. *…
About the Velo Payments APIs API
Velo Payments APIs API on Apizie: 73 endpoints (Authentication endpoint, Get Funding Audit Delta, Get Funding, Logout, …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://zieapi.vercel.app/v1/ecommerce:velopayments/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | ecommerce:velopayments |
|---|---|
| Status | Your key |
| Endpoints | 73 |
| Category | E-commerce |
| Source | velopayments.com |
| Base URL | https://zieapi.vercel.app/v1/ecommerce:velopayments/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Velo Payments APIs API FAQ
How do I call the Velo Payments APIs API?
Create a free Apizie key, then send POST https://zieapi.vercel.app/v1/ecommerce:velopayments/velo-auth with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Velo Payments APIs API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Velo Payments APIs itself also needs your own key from velopayments.com.
Can AI agents use the Velo Payments APIs API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key ecommerce:velopayments.
What is the status of the Velo Payments APIs API?
Needs your own provider key (bring your own key)