Yoco Payments API

Name: Yoco Payments API
Brand: Yoco Payments API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingbearer30 EndpointsREST

For Agents

Programmatically oauth authorization endpoint, get oauth token. Covers 30 operations with bearer authentication.

Install Jentic One Beta

Connect the Yoco Payments API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Yoco Payments API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fyoco.com%2Fyoco" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fyoco.com%2Fyoco" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Yoco Payments API.

OAuth authorization endpoint

Get OAuth token

Logout

List active capital advances

GET STARTED

Start building with Yoco Payments API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Yoco Payments API for, with concrete tasks.

★ Payments Operations

Use the Yoco Payments API to perform payments operations programmatically. The API provides 30 endpoints covering core functionality including oauth authorization endpoint, get oauth token, get user info.

Call GET /authorize to oauth authorization endpoint

Automated Capital Management

Automate capital operations by combining multiple Yoco Payments API endpoints. Agents can get oauth token and then get user info in a single workflow.

Call POST /token to get oauth token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Yoco Payments API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'oauth authorization endpoint', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

30 endpoints — yoco provides payments infrastructure for businesses in africa.

METHOD

PATH

DESCRIPTION

GET

/authorize

OAuth authorization endpoint

POST

/token

Get OAuth token

GET

/userinfo

Get user info

POST

/logout

Logout

GET

/v1/capital/active-advances

List active capital advances

GET

/v1/capital/active-offers

List active capital offers

GET

/v1/locations

List locations

GET

/v1/oauth-2/token-info

Get token info

GET

/authorize

OAuth authorization endpoint

POST

/token

Get OAuth token

GET

/userinfo

Get user info

POST

/logout

Logout

GET

/v1/capital/active-advances

List active capital advances

GET

/v1/capital/active-offers

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Yoco Payments by hand means running its OAuth token exchange against payments.yoco.com, carrying the bearer token on each call, and handling refresh and retries yourself. Through Jentic you install once, import Yoco Payments from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Yoco Payments exposes account-level reads and the token flow rather than a per-resource path handle here, so limit the agent to the operations it needs, such as listing locations or reading active capital offers. You choose that set, so it holds no capability beyond the operations you allow.

Credential isolation

Your Yoco Payments credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list locations' or 'check active capital advances', and Jentic returns the matching Yoco Payments operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Yoco Payments API through Jentic.

What authentication does the Yoco Payments API use?

The Yoco Payments API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I oauth authorization endpoint with the Yoco Payments API?

Yes. Use the GET /authorize endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Yoco Payments API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I oauth authorization endpoint through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'oauth authorization endpoint'. Jentic returns the matching Yoco Payments API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Yoco Payments API have?

The Yoco Payments API exposes 30 endpoints covering capital, checkout, locations operations.

Can I limit what my agent is allowed to do with the Yoco Payments API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which Yoco Payments operations and credentials the agent may use. Yoco Payments exposes account-level reads and the OAuth token flow rather than per-resource handles, so you can allow only the operations the agent needs, such as listing locations or reading active capital offers and advances, while withholding the rest. The agent holds no capability beyond the operations you permit.

Yoco Payments API

Connect the Yoco Payments API to your agent

Capabilities

Start building with Yoco Payments API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs