Generated by API Evangelist
Written by API Evangelist tooling for Token.io's API. It is a proposal applied on top of the contract, not a document Token.io publishes.
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Token Bank Configs API
version: 1.0.0
extends: openapi/token-io-bankconfigs-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-09-26'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 4
- target: $.paths['/members/{memberId}/bank-configs'].get
update:
x-apievangelist-phrasing:
intent: List a member's bank connection configs
effect: read
questions:
- Which bank configurations have I stored for my member?
- Can I see all the per-bank credentials and settings configured for a member?
instructions:
- text: List all bank configs for member {member_id}.
slots:
member_id: path.memberId
- text: Show every bank connection configured for member {member_id}.
slots:
member_id: path.memberId
method: generated
generated: '2026-09-26'
- target: $.paths['/members/{memberId}/bank-configs/{bankId}'].get
update:
x-apievangelist-phrasing:
intent: Get a member's config for one bank
effect: read
questions:
- What configuration is stored for a specific bank on my member?
- Can I check the client id and keys set up for one bank?
instructions:
- text: Get the bank config for bank {bank_id} on member {member_id}.
slots:
bank_id: path.bankId
member_id: path.memberId
- text: Show member {member_id}'s settings for bank {bank_id}.
slots:
member_id: path.memberId
bank_id: path.bankId
method: generated
generated: '2026-09-26'
- target: $.paths['/members/{memberId}/bank-configs/{bankId}'].put
update:
x-apievangelist-phrasing:
intent: Store a member's config for one bank
effect: write
questions:
- Can I save my own open banking client credentials for a specific bank?
- Which standards, like UK Open Banking or Berlin Group NextGenPSD2, can a bank config cover?
instructions:
- text: Store a bank config for bank {bank_id} on member {member_id}.
slots:
bank_id: path.bankId
member_id: path.memberId
- text: Save UK Open Banking client id {client_id} for bank {bank_id} on member {member_id}.
slots:
client_id: query.uk_open_banking_standard.bank_config.clientId
bank_id: path.bankId
member_id: path.memberId
method: generated
generated: '2026-09-26'
- target: $.paths['/members/{memberId}/bank-configs/{bankId}'].delete
update:
x-apievangelist-phrasing:
intent: Delete a member's config for one bank
effect: destructive
questions:
- Can I remove the stored configuration for a bank I no longer connect to?
- What happens when a bank config is deleted from my member?
instructions:
- text: Delete the bank config for bank {bank_id} on member {member_id}.
slots:
bank_id: path.bankId
member_id: path.memberId
- text: Remove member {member_id}'s stored settings for bank {bank_id}.
slots:
member_id: path.memberId
bank_id: path.bankId
method: generated
generated: '2026-09-26'
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.