API
Catalogue, orders and keys by interface
Bring our catalogue into your system, trigger orders and collect the keys. This page shows the way in six steps. Limits, the test environment and boundaries are in the documentation.
This works as soon as the shop opens. Until then you can read everything in peace.
Developer site
OpenAPI
Every call is described in an OpenAPI 3.1 file. Every number on the pages is the number the code enforces.
- BearerOne key per application, stored only as a hash, with expiry and rotation
- JSONMoney in whole cents, dates in ISO 8601, names in snake_case
- 120 a minutereads for a new key, 600 once it is 7 days old
- SignedWebhooks with a signature, optionally signed calls too (RFC 9421)
The API is built and tested, the documentation is online. Keys can be created as soon as the shop opens. Not there yet and only planned: a ready-made software kit, a prepaid balance.
What you can do with it
Sync the catalogue
Load the whole list once, then only what changed since your last sync. A light view shows stock only.
Ready, opens with the sales startTrigger orders
One order per call, with a price ceiling, your own number and a key against double buys.
Ready, opens with the sales startCollect keys
With a right of its own, counted and logged. The first call ends the withdrawal right of that order.
Ready, opens with the sales startReceive webhooks
Signed calls to your server when an order or a product changes. Up to 3 addresses.
Ready, opens with the sales startOffer as a seller
Keep offers, prices and stock from your stock system. This needs selling on Capydra to be open.
Ready, opens with the sales startUse with AI assistants
The same account works through our MCP server. The rules and limits are the same.
Ready, opens with the sales start
Six steps to the first call
- 1
Create an account
You sign in to the shop.
- 2
Create a key
Under "API keys": a name, the role (buyer or seller) and the rights you need. Give as few as you can.
- 3
Confirm the waiver
Two sentences about withdrawal, once. Every order made with the key refers to them.
- 4
Secure the key
It is shown only once. Store it like a password and add the IP addresses of your servers to the list.
- 5
Set a daily limit
The sum of all orders in a day is capped: €250 for a new key, adjustable up to €5,000.
- 6
Send the first call
With the key in the "Authorization" header. The example below reads the first products.
The first call
A key starts with omk_live_. It goes into every call as the bearer value. Money is in whole cents and includes the service fee.
curl "https://capydra.com/api/v1/catalog/products?page=1" \
-H "Authorization: Bearer omk_live_YOUR_KEY"
# only what changed since your last sync
curl "https://capydra.com/api/v1/catalog/products?updatedSince=2026-11-17T00:00:00Z" \
-H "Authorization: Bearer omk_live_YOUR_KEY"Continue in the documentation
The shop is not open yet: calls that change something answer 403 showcase_mode, and answers carry no prices.
Frequently asked questions
What does the API cost?
Access is free. You pay for the orders you trigger. There is no base fee.
Is there a software kit?
Not yet. The documentation has curl examples, and the OpenAPI file loads into the usual tools.
How do I get higher limits?
Write us your plan and your volume. We raise limits for partners where we see the need.
What if my key is stolen?
Revoke it on the key page and make a new one. Until then the daily limit and the IP list cap the damage. Odd calls freeze the key by themselves.
Where do I report an API error?
Through the contact form with the topic API. Name the call and the time.
Ready for the first call?
Read the developer site through, then create a key.
Send a request