Dojo Events API

The Events API from Dojo — 1 operation(s) for events.

Operations 1

POST /epos/events Submit an event #

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/dojo-events-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.

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

OpenAPI Specification

dojo-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Dojo Events API
  version: '2026-02-27'
  description: '# Introduction


    The Dojo API is a REST API, using HTTP response codes to convey status, including successful responses and errors.'
  termsOfService: https://dojo.tech/legal/
  contact:
    name: Dojo Developer Experience Team
servers:
- url: https://api.dojo.tech
security:
- ApiKeyAuth: []
tags:
- name: Events
paths:
  /epos/events:
    post:
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/EventRequest'
        required: true
      tags:
      - Events
      summary: Submit an event
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EventRequest'
      operationId: postEposEvents
      x-operation-id-source: derived
components:
  schemas:
    OrderEvent:
      required:
      - orderId
      type: object
      properties:
        orderId:
          type: string
    ReservationEvent:
      type: object
      properties:
        reservationId:
          description: The EPOS-internal ID of the updated Reservation.
          type: string
      required:
      - reservationId
    EventRequest:
      description: ''
      required:
      - eventType
      - event
      type: object
      properties:
        eventType:
          $ref: '#/components/schemas/EventType'
        event:
          oneOf:
          - $ref: '#/components/schemas/OrderEvent'
          - $ref: '#/components/schemas/PartyEvent'
          - $ref: '#/components/schemas/ReservationEvent'
    EventType:
      description: OrderUpdated, PartyUpdated, ReservationUpdated
      type: string
    PartyEvent:
      type: object
      properties:
        partyId:
          description: The EPOS-internal ID of the updated Party.
          type: string
      required:
      - partyId
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      name: Authorization
      in: header
x-tagGroups:
- name: Core payments
  tags:
  - Payment intents
  - Refunds
  - Reversal
  - Captures
  - Webhooks
  - Customers
  - Setup intents
- name: In-person payments
  tags:
  - Terminals
  - Terminal sessions
- name: Capabilities
  tags:
  - Capabilities
  - Events