dojo.tech valid

Dojo Developer Documentation

Dojo provides payment APIs and SDKs for businesses to accept online and in-person payments, manage transactions, and integrate with EPOS systems.

For agents: Dojo developer docs: payment APIs and SDKs for online and in-person payments, transactions, refunds, webhooks and EPOS integration, with OpenAPI specs.

payment apiopenapipayment intentsepos integrationtransactionswebhooks

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T11:22:28.548Z. Cached copy · Source on dojo.tech

# Dojo Developer Documentation

> Dojo provides payment APIs and SDKs for businesses to accept online and in-person payments, manage transactions, and integrate with EPOS systems.

Key information for LLM agents:

- **Docs base URL**: https://docs.dojo.tech/
- **API Base URL**: https://api.dojo.tech
- **Environment selection**: Sandbox and production both use `https://api.dojo.tech`; the API key determines which environment receives the request.
- **Authentication**: API key via `Authorization: Basic <api_key>` header. `Basic ` is a literal prefix in this scheme; do not base64-encode `api_key:`. Obtain keys from the Dojo Developer Portal at https://developer.dojo.tech
- **Latest Dojo API version**: 2026-02-27 (set via `version` header)

## OpenAPI Specifications

These machine-readable OpenAPI specs can be fetched directly for precise API integration:

- [Dojo API v3 (2026-02-27) — Latest](https://docs.dojo.tech/api/v3/bundled.json): Core payment intents, setup intents, customers, refunds, and webhooks
- [Dojo API v2 (2025-09-10)](https://docs.dojo.tech/api/v2/bundled.json): Previous API version
- [Dojo API v1 (2024-02-05)](https://docs.dojo.tech/api/v1/bundled.json): Legacy API version
- [Payments API](https://docs.dojo.tech/payments/bundled.json): Legacy payments integration
- [Transactions API](https://docs.dojo.tech/transactions/bundled.json): Transaction management and reporting
- [EPOS Data API](https://docs.dojo.tech/epos-data/bundled.json): EPOS system integration (REST)
- [EPOS Data API — WebSocket](https://docs.dojo.tech/epos-data-asyncapi/bundled.yaml): EPOS system integration (AsyncAPI/WebSocket)
- [Tap to Pay on iPhone API](https://docs.dojo.tech/tap-to-pay-on-iphone/bundled.json): Tap to Pay on iPhone integration

## Routing guide

This root file is intentionally compact. Start with the narrowest product-specific file that matches the user's task, and use llms-full.txt only when the request spans multiple product areas.

- [Online Payments](https://docs.dojo.tech/llms-online.txt): Use for hosted checkout, Components, payment links, or virtual terminal flows.
- [Payment Intents](https://docs.dojo.tech/llms-payment-intents.txt): Use for backend payment creation, captures, refunds, cancellations, saved cards, and webhook-driven payment lifecycle logic.
- [Pay at Counter](https://docs.dojo.tech/llms-inperson-pac.txt): Use for `/terminals`, `/terminal-sessions`, and `/terminal-sessions/{terminalSessionId}/signature` plus terminal session orchestration, in-person captures or refunds, signature verification, and pre-authorisation flows.
- [Pay at Table](https://docs.dojo.tech/llms-inperson-pat.txt): Use for the Pay at Table flow: searching payable orders, locking/unlocking, recording payments, and printable bills via the EPOS Data REST and WebSocket APIs.
- [EPOS Integration](https://docs.dojo.tech/llms-epos.txt): Use for EPOS capability registration, Dojo/POS event contracts, and EPOS Data API integration details.
- [Core Concepts](https:
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=dojo.tech · GET /v1/domain/dojo.tech · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for dojo.tech:
1. POST https://agentwebmap.com/v1/sites/dojo.tech/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://dojo.tech/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/dojo.tech/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/dojo.tech).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.