Veeqo

Veeqo API

Veeqo API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-13); not the provider's own document.

Documentation GitHub OpenAPI

Operations 3

GET /current_user GET /current_user #

POST /oauth/token Authentication #

GET /orders GET /orders #

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/veeqo/refs/heads/main/openapi/_ae-authored/veeqo-openapi-generated.yml

Schemas & Data

📊

JSONSchema

https://raw.githubusercontent.com/api-evangelist/veeqo/refs/heads/main/json-schema/veeqo-post-oauth-token-request-schema.json

📊

JSONSchema

https://raw.githubusercontent.com/api-evangelist/veeqo/refs/heads/main/json-schema/veeqo-get-current-user-response-schema.json

📊

JSONSchema

https://raw.githubusercontent.com/api-evangelist/veeqo/refs/heads/main/json-schema/veeqo-post-oauth-token-response-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/veeqo:veeqo-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.1.0
info:
  title: Veeqo API
  version: '2026-10-13'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-13: 3 operation(s) read from 1 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Veeqo has published no machine-readable contract that the pipeline
    could find. Engine: local.'
  x-evidence-tiers:
    code-example: 2
    documentation: 1
    pages-with-code: 1
    pages-read: 1
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-13'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://developers.veeqo.com/getting-started/authentication
servers:
- url: https://api.veeqo.com
paths:
  /current_user:
    get:
      operationId: get_current_user
      tags:
      - Current User
      summary: GET /current_user
      x-source: https://developers.veeqo.com/getting-started/authentication
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetCurrentUserResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl); The API request will return a JSON object with the following properties: { \n \"access_token\" : \"82d7b651f3634a5243c4155f8832f09b30de0c115280d0c2ef62512e6bc5312e\"\
          \ , \n \"token_type\" : \"bearer\" , \n \"created_at\" : 1510741588 \n } From this point, you can save the returned access_token from\
          \ the previous request and use this for any future requests as a bearer token. Here's an example of using the b"
  /oauth/token:
    post:
      operationId: post_oauth_token
      tags:
      - Oauth
      summary: Authentication
      x-source: https://developers.veeqo.com/getting-started/authentication
      parameters:
      - name: Accept
        in: header
        required: true
        schema:
          type: string
        description: application/json
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostOauthTokenRequest'
      responses:
        '201':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostOauthTokenResponse'
      x-evidence:
        kind: documentation
  /orders:
    get:
      operationId: get_orders
      tags:
      - Orders
      summary: GET /orders
      x-source: https://developers.veeqo.com/getting-started/authentication
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl); API keys for private usage \nIf you are a Veeqo seller building a private integration for your own\n business, you may\
          \ use API keys instead of OAuth 2.0.\nThese keys give full API access to your account — treat them like passwords.\n Generating your\
          \ API keys \nPlease contact support at helpme@support.veeqo.com \nor through the support messenger in the Veeqo App before following\
          \ these steps if you"
components:
  schemas:
    GetCurrentUserResponse:
      type: object
      properties:
        access_token:
          type: string
        token_type:
          type: string
        created_at:
          type: integer
    PostOauthTokenRequest:
      type: object
      properties:
        grant_type:
          type: string
        redirect_uri:
          type: string
        client_id:
          type: string
        client_secret:
          type: string
        code:
          type: string
      required:
      - grant_type
      - redirect_uri
      - client_id
      - client_secret
      - code
    PostOauthTokenResponse:
      type: object
      properties:
        access_token:
          type: string
        token_type:
          type: string
        created_at:
          type: integer
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
security:
- apiKey: []
tags:
- name: Current User
- name: Oauth
- name: Orders