CDK Bot Refunds API
The Refunds API from CDK Bot — 1 operation(s) for refunds.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/cdk-bot:cdk-bot-refunds-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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
openapi: 3.2.0
info:
title: CDK Bot — Digital Products Refunds API
version: 1.0.0
termsOfService: https://api.cdk.bot/terms
contact:
name: CDK Bot
email: info@cdk.bot
url: https://cdk.bot
description: 'Agent-native API for purchasing digital products (game keys, gift cards, and more) via USDC on Base chain.
## Quick Start
**One-shot (wallet-native agents):** `POST /purchase {"game_id":"..."}` with an `X-PAYMENT` header — a signed EIP-3009 "exact" authorization for the accepts[] returned in the 402 — and a facilitator settles it gaslessly, returning the key in one call (no tx_hash/quote_id).
**Two-step (any agent):**
1. **Browse**: `GET /games?q=battlefield` — search products, filter by platform/region/product_type
2. **Get price**: `POST /purchase {"game_id":"..."}` — returns 402 with exact USDC amount, wallet address, and standard x402 accepts[]
3. **Pay & get key**: Send USDC onchain, then `POST /purchase {"game_id":"...","tx_hash":"0x...","quote_id":"..."}` — returns product key
## Key facts
- All prices are in USD (USDC on Base chain)
- Only in-stock products are returned (in_stock: true)
- Payment address: `0x0b321A0F1294431347f98e10a2275F23B11BBfFb`
- No authentication required for browsing or purchasing
- Double-spend protection via unique tx_hash constraint
- Agent discovery: `GET /.well-known/agent.json`
- Liveness check: `GET /health`
## Sandbox Mode
Test the full purchase flow without spending real money:
1. Get free test USDC from Circle Faucet and Sepolia ETH from Alchemy Faucet
2. Add `"chain": "base-sepolia"` to your `POST /purchase` request
3. Pay with test USDC on Base Sepolia — receive a mock key (`SANDBOX-XXXXX-XXXXX-XXXXX`)
Same API, same URL, same flow — just add the chain parameter. See `GET /.well-known/agent.json` for full sandbox docs.'
x-guidance: 'CDK Bot sells game keys, gift cards, and digital products for AI agents. Flow: (1) GET /games?q=<query> to search the catalog. (2) POST /purchase {"game_id":"..."} to get an HTTP 402 with a price-locked USDC quote on Base. (3) Pay one-shot by retrying with an X-PAYMENT header (signed EIP-3009 authorization, gasless), or send USDC onchain and retry with tx_hash + quote_id. (4) The response contains the product key; poll GET /orders/{id} if delivery is pending. Sandbox: add "chain":"base-sepolia" to test without real money.'
servers:
- url: https://api.cdk.bot
tags:
- name: Refunds
paths:
/refund:
post:
tags:
- Refunds
summary: Submit a refund claim
description: Submit a refund claim for a purchased key. Requires wallet address verification. Must be within 30-day dispute window (see dispute_deadline in order response). Delivery failures (not_delivered) are auto-approved instantly. Key-related issues (key_invalid, key_already_redeemed, wrong_product) are set to pending and verified within 24 hours.
requestBody:
content:
application/json:
schema:
type: object
properties:
order_id:
type: string
description: Order ID to refund
wallet_address:
type: string
description: Buyer wallet address — must match the address on the original order
reason:
type: string
enum:
- key_invalid
- key_already_redeemed
- wrong_product
- not_delivered
description: 'Reason for refund: key_invalid (activation error), key_already_redeemed (used before delivery), wrong_product (wrong platform/region/edition), not_delivered (payment confirmed but no key received)'
required:
- order_id
- wallet_address
- reason
responses:
'200':
description: Refund submitted
content:
application/json:
schema:
type: object
properties:
id:
type: string
description: Refund claim ID
order_id:
type: string
reason:
type: string
key_status:
type: string
nullable: true
description: Key verification result (if available)
resolution:
type: string
description: 'Refund lifecycle: "pending" (awaiting review), "approved" (USDC payout pending), "refunded" (USDC sent back to buyer), "denied"'
resolved_at:
type: number
nullable: true
description: Timestamp when admin resolved the refund (Unix ms). Null if still pending.
admin_note:
type: string
nullable: true
description: Admin note explaining the resolution decision
refund_tx_hash:
type: string
nullable: true
description: Onchain tx hash proving USDC was sent back to buyer wallet
refund_amount:
type: number
nullable: true
description: USD amount refunded via USDC
refunded_at:
type: number
nullable: true
description: Timestamp when refund USDC was sent (Unix ms)
created_at:
type: number
required:
- id
- order_id
- reason
- key_status
- resolution
- created_at
'400':
description: Bad request
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code
example: not_found
message:
type: string
description: Human-readable error description
diagnosis:
type: object
properties:
code:
type: string
enum:
- tx_not_found
- tx_failed
- insufficient_confirmations
- wrong_contract
- wrong_recipient
- insufficient_amount
- no_transfer_logs
- no_erc20_logs
description: Machine-readable diagnosis code for payment verification failure
expected_chain:
type: string
description: Chain name we verified on
example: base
expected_chain_id:
type: number
description: Chain ID we verified on
example: 8453
expected_usdc_contract:
type: string
description: USDC contract address we looked for
example: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
expected_recipient:
type: string
description: Payment recipient address we looked for
example: '0x0b321A0F1294431347f98e10a2275F23B11BBfFb'
found:
type: object
properties:
contract:
type: string
description: Token contract found in tx (if different from expected)
recipient:
type: string
description: Recipient found in tx (if different from expected)
amount_usdc:
type: number
description: Amount transferred (if found)
description: What was actually found in the transaction
hint:
type: string
description: Actionable hint for the agent to fix the issue
required:
- code
- expected_chain
- expected_chain_id
- expected_usdc_contract
- expected_recipient
- hint
description: Structured payment diagnosis (only on 422 payment_verification_failed)
fields:
type: array
items:
type: object
properties:
path:
type: string
example: limit
message:
type: string
example: limit must be an integer between 1 and 100
code:
type: string
example: invalid_format
required:
- path
- message
- code
description: Per-field validation errors (only on 400 validation_error)
required:
- error
'403':
description: Forbidden
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code
example: not_found
message:
type: string
description: Human-readable error description
diagnosis:
type: object
properties:
code:
type: string
enum:
- tx_not_found
- tx_failed
- insufficient_confirmations
- wrong_contract
- wrong_recipient
- insufficient_amount
- no_transfer_logs
- no_erc20_logs
description: Machine-readable diagnosis code for payment verification failure
expected_chain:
type: string
description: Chain name we verified on
example: base
expected_chain_id:
type: number
description: Chain ID we verified on
example: 8453
expected_usdc_contract:
type: string
description: USDC contract address we looked for
example: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
expected_recipient:
type: string
description: Payment recipient address we looked for
example: '0x0b321A0F1294431347f98e10a2275F23B11BBfFb'
found:
type: object
properties:
contract:
type: string
description: Token contract found in tx (if different from expected)
recipient:
type: string
description: Recipient found in tx (if different from expected)
amount_usdc:
type: number
description: Amount transferred (if found)
description: What was actually found in the transaction
hint:
type: string
description: Actionable hint for the agent to fix the issue
required:
- code
- expected_chain
- expected_chain_id
- expected_usdc_contract
- expected_recipient
- hint
description: Structured payment diagnosis (only on 422 payment_verification_failed)
fields:
type: array
items:
type: object
properties:
path:
type: string
example: limit
message:
type: string
example: limit must be an integer between 1 and 100
code:
type: string
example: invalid_format
required:
- path
- message
- code
description: Per-field validation errors (only on 400 validation_error)
required:
- error
'404':
description: Order not found
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code
example: not_found
message:
type: string
description: Human-readable error description
diagnosis:
type: object
properties:
code:
type: string
enum:
- tx_not_found
- tx_failed
- insufficient_confirmations
- wrong_contract
- wrong_recipient
- insufficient_amount
- no_transfer_logs
- no_erc20_logs
description: Machine-readable diagnosis code for payment verification failure
expected_chain:
type: string
description: Chain name we verified on
example: base
expected_chain_id:
type: number
description: Chain ID we verified on
example: 8453
expected_usdc_contract:
type: string
description: USDC contract address we looked for
example: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
expected_recipient:
type: string
description: Payment recipient address we looked for
example: '0x0b321A0F1294431347f98e10a2275F23B11BBfFb'
found:
type: object
properties:
contract:
type: string
description: Token contract found in tx (if different from expected)
recipient:
type: string
description: Recipient found in tx (if different from expected)
amount_usdc:
type: number
description: Amount transferred (if found)
description: What was actually found in the transaction
hint:
type: string
description: Actionable hint for the agent to fix the issue
required:
- code
- expected_chain
- expected_chain_id
- expected_usdc_contract
- expected_recipient
- hint
description: Structured payment diagnosis (only on 422 payment_verification_failed)
fields:
type: array
items:
type: object
properties:
path:
type: string
example: limit
message:
type: string
example: limit must be an integer between 1 and 100
code:
type: string
example: invalid_format
required:
- path
- message
- code
description: Per-field validation errors (only on 400 validation_error)
required:
- error
'409':
description: Duplicate refund
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code
example: not_found
message:
type: string
description: Human-readable error description
diagnosis:
type: object
properties:
code:
type: string
enum:
- tx_not_found
- tx_failed
- insufficient_confirmations
- wrong_contract
- wrong_recipient
- insufficient_amount
- no_transfer_logs
- no_erc20_logs
description: Machine-readable diagnosis code for payment verification failure
expected_chain:
type: string
description: Chain name we verified on
example: base
expected_chain_id:
type: number
description: Chain ID we verified on
example: 8453
expected_usdc_contract:
type: string
description: USDC contract address we looked for
example: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
expected_recipient:
type: string
description: Payment recipient address we looked for
example: '0x0b321A0F1294431347f98e10a2275F23B11BBfFb'
found:
type: object
properties:
contract:
type: string
description: Token contract found in tx (if different from expected)
recipient:
type: string
description: Recipient found in tx (if different from expected)
amount_usdc:
type: number
description: Amount transferred (if found)
description: What was actually found in the transaction
hint:
type: string
description: Actionable hint for the agent to fix the issue
required:
- code
- expected_chain
- expected_chain_id
- expected_usdc_contract
- expected_recipient
- hint
description: Structured payment diagnosis (only on 422 payment_verification_failed)
fields:
type: array
items:
type: object
properties:
path:
type: string
example: limit
message:
type: string
example: limit must be an integer between 1 and 100
code:
type: string
example: invalid_format
required:
- path
- message
- code
description: Per-field validation errors (only on 400 validation_error)
required:
- error
security: []
operationId: postRefund
x-operation-id-source: derived