Integration
Connect CryptAPI to Transport for The Netherlands
When something happens in CryptAPI, your agent does the next thing in Transport for The Netherlands. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CryptAPI and Transport for The Netherlands to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with CryptAPI and Transport for The Netherlands
Triggers and actions 1 trigger · 14 actions
Trigger
Payment received (instant)Fires when a payment address created via Create payment address receives funds; CryptAPI calls the callback URL supplied at creation time with the payment details.
- Convert price
Convert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.
- Create payment address
Generate a new cryptocurrency payment address for a given ticker (e.g. btc, eth, trc20/usdt) that a customer can send funds to, with a callback URL for payment notifications.
- Estimate blockchain fees
Estimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.
- Generate payment QR code
Generate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.
- Get payment address logs
Get the callback/payment activity log for a previously created payment address, for a given ticker.
- Get ticker info
Get details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.
- List supported cryptocurrencies
List all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.
Action
Find passtimes by lineGet the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.
- Find passtimes by stop area
Get the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.
- Find passtimes by timing point
Get the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.
- List journeys
List the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.
- List lines
List all transit lines known to the OVAPI, with data owner code, line planning number, direction, and optionally line name/public number/transport type/destination.
- List stop areas
List all stop areas (groups of nearby timing points sharing one traveler-facing stop name) known to the OVAPI, with position, name, and town.
- List timing points
List all timing point codes (bus stops, tram/train stops, and virtual points) known to the OVAPI within its current uptime.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.