Toku is a Chile‑based fintech platform that provides B2B payment and collection solutions powered by intelligent AI agents. The platform automates invoicing, executes payments, reconciles transactions, and reduces delinquency, enabling businesses to increase cash flow and streamline financial operations. Backed by Gradient Ventures, Toku serves enterprises across Latin America.
Toku publishes 37 API contracts indexed on the APIs.io network, including Adjustment Documents API, Auth API, Beneficiaries API, and 34 more. Tagged areas include FinTech, Payments, B2B, Automation, and Chile.
The Toku catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
Toku’s developer surface includes getting-started guide, authentication, documentation, API reference, support, engineering blog, pricing, and 23 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Payments regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/toku/"><img src="https://apis.io/badge/toku/card.svg" alt="Toku on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
El objeto `Adjustment Document` es una nota de crédito o factura de proveedor que la organización puede aplicar como saldo a favor al momento del cobro. Si está ligado a una Inv...
Alta y mantención de los Beneficiaries: las personas o empresas que reciben un pago. Un Beneficiary agrupa los datos de identidad y una o más Beneficiary Accounts.
Consulta y mantención de las Beneficiary Accounts: las cuentas bancarias asociadas a un Beneficiary, junto con su verificación bancaria y su flujo de aprobación.
Emissão de boleto bancário no Brasil e acompanhamento do seu ciclo de vida: registro no banco, consulta do PDF, baixa quando o pagamento é confirmado e cancelamento. Nesta seção...
Ciclo de vida de una Checkout Session: creación, consulta, actualización de su vencimiento y expiración. Incluye las operaciones que consume el portal de pago de Toku y las que ...
API server-to-server con la que la organización consulta qué consintió una persona, para decidir qué pedirle antes de anunciar. Se autentica igual que los intents: la llama su b...
Endpoints que sostienen el Customer Portal de Toku: el portal web donde un Customer revisa sus Invoices y Subscriptions, inscribe medios de pago y paga. La mayoría de estas oper...
Cobrança de Subscriptions por Débito Automático no Brasil: cadastro das contas bancárias que o pagador autorizou no banco, geração dos arquivos de remessa enviados ao banco e pr...
Facturación electrónica en México. Cubre las dos mitades del flujo: los datos de facturación que se guardan sobre un Customer o un Invoice, y la emisión de los billing documents...
Integración con Forum: configuración de la ventana de envío de cada organización, despacho de los Webhooks que informan los pagos y generación de los reportes diarios que los re...
API server-to-server con la que la organización anuncia cada consentimiento que va a pedir, antes de renderizar su formulario. La llama su backend con la api-key de Toku, y el g...
Una `Invoice` contiene la información de una deuda. Para crearla se necesita el identificador público del `Customer` al que pertenece, que se obtiene al crearlo en Toku y tiene ...
Administración de los Payment Methods de una Account: creación, consulta, edición, eliminación y carga masiva, además de la invalidación de los medios de pago que dejaron de est...
Consulta y gestión de Payouts: listado, detalle, aprobación, rechazo, edición de monto, comprobantes, actualización de estado y etapas de creación y ejecución en lote.
Ingesta de Account Payables para crear un Payout Request —enviándolas por API o depositando archivos CSV en el SFTP de la organización— y avance de las filas resultantes hacia e...
Operações de cobrança Pix integradas diretamente com os PSPs brasileiros: criação da cobrança, cadastro da chave Pix, cancelamento e recebimento das notificações de pagamento en...
Cobrança recorrente por Pix Automático no Brasil: cadastro da recorrência no banco do pagador, cobrança das Invoices de cada ciclo, retentativas e cancelamento. Nesta seção, as ...
Registro y administración de los terminales POS de la cuenta. Un terminal es el dispositivo físico donde se cobra, y queda asociado al adquirente con el que se registró: ese adq...
Comprobantes de una operación y documentos tributarios asociados. Agrupa la generación del comprobante, su descarga mediante URL firmada, la configuración con que se despliega y...
Devoluciones de dinero sobre un pago ya realizado. Toku registra cada devolución como una Transaction propia de tipo `REVERSED`, ligada al pago original, y la aplica sobre las I...
Motor de reportes por entidad: consulta de columnas y hojas disponibles, generación del reporte completo y procesamiento por partes de los reportes grandes.
Endpoints que reciben datos de tarjeta, ya sea para cobrar una vez, para inscribir la tarjeta como medio de pago recurrente o para guardarla como PaymentInstrument sin cobrarla....
Cobro y registro de Transactions sobre Invoices. Una Transaction agrupa el monto cobrado, el medio de pago usado y los Invoices que salda, e incluye tanto los cobros que procesa...
Verificación de titularidad de cuentas bancarias mexicanas (CLABE). Se confirma que una cuenta existe y que pertenece a la persona declarada realizando una micro transferencia p...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: toku
name: Toku
description: Toku is a Chile‑based fintech platform that provides B2B payment and collection solutions powered by intelligent
AI agents. The platform automates invoicing, executes payments, reconciles transactions, and reduces delinquency, enabling
businesses to increase cash flow and streamline financial operations. Backed by Gradient Ventures, Toku serves enterprises
across Latin America.
image: https://trytoku.com/og/home.jpg
url: https://artifacts.apis.io/toku/apis.yml
x-type: company
x-source: harvest:vc-portfolio
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-29 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-29'
modified: '2026-10-29'
tags:
- FinTech
- Payments
- B2B
- Automation
- Chile
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: AgenticAccess
url: agentic-access/toku-agentic-access.yml
- type: Spectral
url: rules/toku-rules.yml
- type: JSONLD
url: json-ld/toku-context.jsonld
- type: Vocabulary
url: vocabulary/toku-vocabulary.yml
- type: AgentSkill
url: skills/_index.yml
- type: DataModel
url: data-model/toku-data-model.yml
- type: Idempotency
url: conventions/toku-conventions.yml
- type: Conventions
url: conventions/toku-conventions.yml
- type: Compliance
url: https://trust.trytoku.com/
- type: ErrorCatalog
url: errors/toku-problem-types.yml
- type: Conformance
url: conformance/toku-conformance.yml
- type: LLMsTxt
url: llms/toku-llms.txt
- type: MCPServer
url: mcp/toku-mcp.yml
- type: WellKnown
url: well-known/toku-well-known.yml
- type: Hosts
url: hosts/toku-hosts.yml
- type: Vendors
url: vendors/toku-vendors.yml
- type: GettingStarted
url: https://docs.trytoku.com/docs/getting-started
- type: Authentication
url: authentication/toku-authentication.yml
- type: TrustCenter
url: security/toku-trust-center.yml
- type: DomainSecurity
url: security/toku-domain-security.yml
- type: Website
url: https://trytoku.com/
- type: Documentation
url: https://docs.trytoku.com/
- type: DeveloperPortal
url: https://docs.trytoku.com/
- type: APIReference
url: https://docs.trytoku.com/
- type: Support
url: https://trytoku.com/support
- type: Blog
url: https://trytoku.com/blog
- type: Pricing
url: https://trytoku.com/pricing
- type: TermsOfService
url: https://trytoku.com/terms
- type: PrivacyPolicy
url: https://trytoku.com/privacy
- type: SignUp
url: https://trytoku.com/signup
apis:
- aid: toku:toku-adjustment-documents-api
name: Toku Adjustment Documents API
description: El objeto `Adjustment Document` es una nota de crédito o factura de proveedor que la organización puede aplicar
como saldo a favor al momento del cobro. Si está ligado a una Invoice (`id_origin_invoice`), solo se puede aplicar al
pagar esa Invoice.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Adjustment Documents
properties:
- type: OpenAPI
url: openapi/toku-adjustment-documents-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-auth-api
name: Toku Auth API
description: Emisión y validación de tokens de acceso, resolución de API keys, verificación de reCAPTCHA y políticas de
acceso por Organization.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Auth
properties:
- type: OpenAPI
url: openapi/toku-auth-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-beneficiaries-api
name: Toku Beneficiaries API
description: 'Alta y mantención de los Beneficiaries: las personas o empresas que reciben un pago. Un Beneficiary agrupa
los datos de identidad y una o más Beneficiary Accounts.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Beneficiaries
properties:
- type: OpenAPI
url: openapi/toku-beneficiaries-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-beneficiary-accounts-api
name: Toku Beneficiary Accounts API
description: 'Consulta y mantención de las Beneficiary Accounts: las cuentas bancarias asociadas a un Beneficiary, junto
con su verificación bancaria y su flujo de aprobación.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Beneficiary Accounts
properties:
- type: OpenAPI
url: openapi/toku-beneficiary-accounts-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-boleto-api
name: Toku Boleto API
description: 'Emissão de boleto bancário no Brasil e acompanhamento do seu ciclo de vida: registro no banco, consulta do
PDF, baixa quando o pagamento é confirmado e cancelamento.
Nesta seção, as operações disponíveis para integradores são a inicialização de uma cobrança a partir de Invoices, o cadastro
da carteira e a obtenção do PDF. As demais são operações internas que a Toku invoca a partir dos seus próprios processos
(filas, tarefas agendadas e webhooks dos bancos).'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Boleto
properties:
- type: OpenAPI
url: openapi/toku-boleto-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-checkout-session-api
name: Toku Checkout Session API
description: 'Ciclo de vida de una Checkout Session: creación, consulta, actualización de su vencimiento y expiración. Incluye
las operaciones que consume el portal de pago de Toku y las que ejecutan procesos internos de forma asíncrona.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Checkout Session
properties:
- type: OpenAPI
url: openapi/toku-checkout-session-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-consulta-de-consentimientos-api
name: Toku Consulta de consentimientos API
description: 'API server-to-server con la que la organización consulta qué consintió una persona, para decidir qué pedirle
antes de anunciar. Se autentica igual que los intents: la llama su backend con la api-key de Toku, el gateway le entrega
al servicio la organización en el header `organization-consumer`, y una request sin él responde `403`. Cada organización
ve sólo lo que ella registró.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Consulta de consentimientos
properties:
- type: OpenAPI
url: openapi/toku-consulta-de-consentimientos-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-customer-collection-accounts-api
name: Toku Customer Collection Accounts API
description: Cuentas bancarias que un Customer deja registradas para que se le cobre por PAC o domiciliación bancaria.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Customer Collection Accounts
properties:
- type: OpenAPI
url: openapi/toku-customer-collection-accounts-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-customer-portal-api
name: Toku Customer Portal API
description: 'Endpoints que sostienen el Customer Portal de Toku: el portal web donde un Customer revisa sus Invoices y
Subscriptions, inscribe medios de pago y paga.
La mayoría de estas operaciones las consume el propio portal. Las excepciones son la creación de Customer Portal Sessions
y de Checkout Sessions, que una organización sí integra desde su backend para llevar a un Customer al portal.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Customer Portal
properties:
- type: OpenAPI
url: openapi/toku-customer-portal-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-customers-api
name: Toku Customers API
description: Consulta de la información de un Customer asociada a sus medios de pago, y asociación de un Payment Method
con una Subscription.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Customers
properties:
- type: OpenAPI
url: openapi/toku-customers-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-d-bito-autom-tico-api
name: Toku Débito Automático API
description: 'Cobrança de Subscriptions por Débito Automático no Brasil: cadastro das contas bancárias que o pagador autorizou
no banco, geração dos arquivos de remessa enviados ao banco e processamento dos arquivos de retorno que confirmam ou rejeitam
cada débito.
Nesta seção, a operação disponível para integradores é o cadastro das contas em lote. As demais são operações internas
que a Toku invoca a partir dos seus próprios processos (filas e tarefas agendadas).'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Débito Automático
properties:
- type: OpenAPI
url: openapi/toku-d-bito-autom-tico-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-debt-reconciliation-public-api
name: Toku Debt Reconciliation Public API
description: The Debt Reconciliation Public API from Toku — 1 operation(s) for debt reconciliation public.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Debt Reconciliation Public
properties:
- type: OpenAPI
url: openapi/toku-debt-reconciliation-public-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-efectivo-api
name: Toku Efectivo API
description: The Efectivo API from Toku — 2 operation(s) for efectivo.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Efectivo
properties:
- type: OpenAPI
url: openapi/toku-efectivo-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-electronic-signature-api
name: Toku Electronic Signature API
description: Creación de Documents para firma electrónica, consulta de su estado y descarga del documento firmado.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Electronic Signature
properties:
- type: OpenAPI
url: openapi/toku-electronic-signature-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-facturaci-n-api
name: Toku Facturación API
description: 'Facturación electrónica en México. Cubre las dos mitades del flujo: los datos de facturación que se guardan
sobre un Customer o un Invoice, y la emisión de los billing documents (CFDI) que se derivan de ellos —PPD, PUE, complementos
de pago y notas de crédito— junto con su consulta y cancelación ante el SAT.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Facturación
properties:
- type: OpenAPI
url: openapi/toku-facturaci-n-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-forum-api
name: Toku Forum API
description: 'Integración con Forum: configuración de la ventana de envío de cada organización, despacho de los Webhooks
que informan los pagos y generación de los reportes diarios que los respaldan.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Forum
properties:
- type: OpenAPI
url: openapi/toku-forum-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-intents-de-consentimiento-api
name: Toku Intents de consentimiento API
description: 'API server-to-server con la que la organización anuncia cada consentimiento que va a pedir, antes de renderizar
su formulario. La llama su backend con la api-key de Toku, y el gateway le entrega al servicio la organización en el header
`organization-consumer`; una request sin él responde `403`.
Es lo que habilita el producto: una organización sin credencial no crea intents, y sin intent no hay consentimiento.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Intents de consentimiento
properties:
- type: OpenAPI
url: openapi/toku-intents-de-consentimiento-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-invoices-api
name: Toku Invoices API
description: 'Una `Invoice` contiene la información de una deuda. Para crearla se necesita el identificador público del
`Customer` al que pertenece, que se obtiene al crearlo en Toku y tiene la forma `cus_ejC08yLqOWoFhVx4Fx42E3IR9X50tNx2`.
Además, toda `Invoice` queda asociada a una `Subscription`: se puede indicar por su identificador público si ya existe,
o dejar que Toku la resuelva a partir del `product_id`.
La moneda de una `Invoice` depende de la `Account` de cobro a la que pertenece. Por ejemplo, una `Account` en Chile emite
sus deudas en `CLP` o `CLF`. La moneda también determina cuántos decimales admite el monto.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Invoices
properties:
- type: OpenAPI
url: openapi/toku-invoices-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-llaves-de-encriptaci-n-api
name: Toku Llaves de encriptación API
description: 'Generación de las llaves con las que encriptas los datos de tarjeta antes de enviarlos. Toku
soporta RSA 2048 con PKCS1_OAEP y AES 256 en modo CBC.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://secure.api.trytoku.com
tags:
- Llaves de encriptación
properties:
- type: OpenAPI
url: openapi/toku-llaves-de-encriptaci-n-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-pac-api
name: Toku PAC API
description: 'Medios de pago con cargo automático a una cuenta bancaria en Chile: PAC y los catálogos bancarios asociados.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- PAC
properties:
- type: OpenAPI
url: openapi/toku-pac-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-payment-methods-api
name: Toku Payment Methods API
description: 'Administración de los Payment Methods de una Account: creación, consulta, edición, eliminación y carga masiva,
además de la invalidación de los medios de pago que dejaron de estar vigentes.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Payment Methods
properties:
- type: OpenAPI
url: openapi/toku-payment-methods-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-payout-api
name: Toku Payout API
description: 'Consulta y gestión de Payouts: listado, detalle, aprobación, rechazo, edición de monto, comprobantes, actualización
de estado y etapas de creación y ejecución en lote.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Payout
properties:
- type: OpenAPI
url: openapi/toku-payout-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-payout-request-ingestion-api
name: Toku Payout Request Ingestion API
description: Ingesta de Account Payables para crear un Payout Request —enviándolas por API o depositando archivos CSV en
el SFTP de la organización— y avance de las filas resultantes hacia el servicio de payouts.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Payout Request Ingestion
properties:
- type: OpenAPI
url: openapi/toku-payout-request-ingestion-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-payout-request-items-api
name: Toku Payout Request Items API
description: Seguimiento y cierre de los Payout Request Items, las filas individuales que quedaron registradas al ingestar
un Payout Request.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Payout Request Items
properties:
- type: OpenAPI
url: openapi/toku-payout-request-items-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-pix-api
name: Toku Pix API
description: 'Operações de cobrança Pix integradas diretamente com os PSPs brasileiros: criação da cobrança, cadastro da
chave Pix, cancelamento e recebimento das notificações de pagamento enviadas pelo PSP.
Nesta seção, as operações disponíveis para integradores são a criação de uma cobrança Pix a partir de Invoices e o cadastro
da chave Pix. As demais são operações internas que a Toku invoca a partir dos seus próprios processos (filas, tarefas
agendadas e webhooks dos bancos).'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Pix
properties:
- type: OpenAPI
url: openapi/toku-pix-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-pix-autom-tico-api
name: Toku Pix Automático API
description: 'Cobrança recorrente por Pix Automático no Brasil: cadastro da recorrência no banco do pagador, cobrança das
Invoices de cada ciclo, retentativas e cancelamento.
Nesta seção, as operações disponíveis para integradores são o cadastro do Payment Method via notificação push e a configuração
de cobrança de uma Subscription. As demais são operações internas, chamadas pelos próprios processos da Toku e pelas notificações
dos bancos.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Pix Automático
properties:
- type: OpenAPI
url: openapi/toku-pix-autom-tico-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-pos-terminals-api
name: Toku POS Terminals API
description: 'Registro y administración de los terminales POS de la cuenta. Un terminal es el dispositivo físico donde se
cobra, y queda asociado al adquirente con el que se registró: ese adquirente no se elige en cada cobro, sino que es una
propiedad del dispositivo.'
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- POS Terminals
properties:
- type: OpenAPI
url: openapi/toku-pos-terminals-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
- aid: toku:toku-receipts-api
name: Toku Receipts API
description: Comprobantes de una operación y documentos tributarios asociados. Agrupa la generación del comprobante, su
descarga mediante URL firmada, la configuración con que se despliega y la emisión del documento tributario del país.
humanURL: https://docs.trytoku.com/reference
baseURL: https://api.trytoku.com
tags:
- Receipts
properties:
- type: OpenAPI
url: openapi/toku-receipts-api-openapi.yml
- type: JSONSchema
url: json-schema/toku-public-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-created-checkout-session-response-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/toku-update-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-webhook-endpoint-payload-schema.json
- type: JSONSchema
url: json-schema/toku-checkout-session-request-v2-decryption-schema.json
# --- truncated at 32 KB (41 KB total) ---
# Full source: https://artifacts.apis.io/toku/apis.yml
Toku API — frequently asked questions
Does Toku have an API?
Yes. APIs.io lists 37 APIs from Toku, including Toku Adjustment Documents API, Toku Auth API and Toku Beneficiaries API, and 34 more.
Is there an OpenAPI specification for the Toku API?
Yes. APIs.io indexes 37 OpenAPI specifications for Toku, each linked for download from this page.
How do I authenticate with the Toku API?
Toku uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Toku Authentication.
Does Toku have an MCP server?
Yes. APIs.io lists 1 MCP server for Toku: Remote MCP server at docs.trytoku.com.
Is the Toku API ready for AI agents?
Toku has a Kin Score of 51.3 out of 100 (developing) and an Agent Readiness score of 43.1 (agent-native), scored by API Evangelist on 2026-10-31.
Discovery needs no key. Ratings and market analysis are Pro.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: