Yoco
Keep Yoco in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
33 ways to read, 1 way to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Yoco, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create payment linkApproval by rule
- List active capital advancesRead
Example flow
- Yoco · List active capital advancesDone
- Yoco · Create payment linkNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Yoco.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Yoco
- Yoco's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Yoco test account before you go live.
For developers
Technical detail
Yoco API v1: payments, refunds, orders, payouts and payout entries, payment links, catalogue, locations, card machines, staff, webhooks and capital (read); creates payment links.
Yoco API docs- Source actions
- 33
- Destination actions
- 1
- Data types
- 19
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Business1
- Get authorised businessSource
Read the ID and name of the Yoco business the token is authorised for.
Capital advances1
- List active capital advancesSource
Active Yoco Capital advances with principal, payable and paid amounts.
Capital offers1
- List active capital offersSource
Active Yoco Capital offers with their maximum principal and expiry.
Card machines2
- Get card machineSource
Read one card machine by ID.
- List card machinesSourceIncremental
Read card machines, optionally changed since a date.
Item brands2
- Get item brandSource
Read one item brand by ID.
- List item brandsSourceIncremental
Read item brands, optionally changed since a date.
Item categories2
- Get item categorySource
Read one item category by ID.
- List item categoriesSourceIncremental
Read item categories, optionally changed since a date.
Items2
- Get itemSource
Read one item by ID.
- List catalogue itemsSourceIncremental
Read catalogue items, optionally changed since a date.
Locations2
- Get locationSource
Read one location by ID.
- List locationsSource
Read locations.
Modifier groups2
- Get modifier groupSource
Read one modifier group by ID.
- List modifier groupsSource
Read modifier groups.
Orders2
- Get orderSource
Read one order by ID.
- List ordersSourceIncremental
Read orders, optionally changed since a date.
Payment links3
- Create payment linkDestinationNot retried automaticallyApproval before production
Create a Yoco payment link for an amount. No money moves until the customer pays on the link.
- Get payment linkSource
Read one payment link by ID.
- List payment linksSourceIncremental
Read payment links, optionally changed since a date.
Payments2
- Get paymentSource
Read one payment by ID.
- List paymentsSourceIncremental
Read payments, optionally changed since a date.
Payout entries1
- List payout entriesSource
Payments, refunds, fees and adjustments settled in one payout, for bank reconciliation.
Payouts2
- Get payoutSource
Read one payout by ID.
- List payoutsSourceIncremental
Read payouts, optionally changed since a date.
Refunds2
- Get refundSource
Read one refund by ID.
- List refundsSourceIncremental
Read refunds, optionally changed since a date.
Staff2
- Get staff memberSource
Read one staff member by ID.
- List staff membersSourceIncremental
Read staff members, optionally changed since a date.
Taxes2
- Get taxSource
Read one tax by ID.
- List taxesSource
Read taxes.
Webhook event types1
- List webhook event typesSource
Event types a webhook subscription can listen to.
Webhook subscriptions2
- Get webhook subscriptionSource
Read one webhook subscription by ID.
- List webhook subscriptionsSource
Read webhook subscriptions.
Access and limits
- Authentication
- Yoco OAuth access token or personal API key
- Plans and access
- A Yoco business with a personal API key, or an OAuth application authorised by the business, with the read scopes for each entity. OAuth applications must use an OAuth access token for business data; API keys of OAuth applications only reach application endpoints such as webhooks. Each entity needs its scope (business/orders:read, business/payouts:read, business/catalogue:read, business/locations:read, business/devices:read, business/staff:read).
- Test environment
- Yoco provides a sandbox at api.yocosandbox.com for test businesses.
- Rate limits
- Yoco does not publish fixed limits; it returns HTTP 429 with Retry-After, which Nexra honours with bounded retries.
- Pagination
- Cursor pagination: cursor and limit (max 100); next_cursor is null on the last page.
- Provider events
- Yoco webhook subscriptions (payment.created, payment.refunded, order and item events) are managed through the API or developer portal; subscriptions can be read here. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Intentional exclusions: deleting payment links, creating, updating, testing, rotating or deleting webhook subscriptions, Web POS devices and payments (a Web POS payment charges a card), and the separate Checkout API (checkout creation and refunds).
- Created and updated filters cover at most 31 days per request; page through windows for longer history.
- Disputes and chargebacks: Yoco's API has no dispute or chargeback endpoint. Dispute deductions appear only as payout entries of type dispute (List payout entries for a payout), so reconcile chargebacks from payout entries.
- Yoco does not document an idempotency key for payment link creation, so an uncertain create is never repeated.
- Payment, refund, order, payout and payment link lists accept several statuses (repeated status parameters); the staff list takes one.
- Access tokens are supplied by the business; Nexra does not run the Yoco OAuth consent flow or refresh tokens.
Developer reference
- Create the Yoco credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Yoco, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/yoco and the Connections API.