Use this endpoint to fetch Agreements specific to your institution and Jiko.
Jiko Customer API (Version: fd60d28d)
Welcome to the Jiko Customer API Reference! Jiko enables you to integrate money storage and movement, backed by the safety and security of US Treasury Bills. Use the Customer API if you are a Jiko customer integrating Jiko directly into your internal systems.
For questions regarding authorization for the Customer API, please visit our OAuth guide
- Production serverhttps://api.business.jiko.io/api/v1/customer/
- Sandbox serverhttps://customer-api.sandbox-api.jikoservices.com/api/v1/customer/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://api.business.jiko.io/api/v1/customer/ \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Successful Response
Apartment, Suite, Box number, etc.
Apartment, Suite, Box number, etc.
State (Postal Abbreviations. Example: "AL", "NJ", "OH")
State (Postal Abbreviations. Example: "AL", "NJ", "OH")
- BUSINESS
- INDIVIDUAL
{ "address": { "street_address": "string", "street_address2": "string", "city": "string", "postal_code": "string", "state": "string", "country": "string" }, "email": "string", "phone_number": "string", "account_status": "OPEN", "type": "BUSINESS", "name": "string", "identification_number": { "identification_number": "string", "issuing_country": "string", "type": "TIN" } }
Request
This endpoint uploads a verification document (e.g., passport, articles of incorporation) directly to the customer's profile.
The document_type is specified in the URL path. The raw file data is sent in the request body with Content-Type and Content-Length headers. It returns the document's new document_id.
It is mainly used to verify customer requests (e.g. Customer change request, close account request, ACH request).
- Production serverhttps://api.business.jiko.io/api/v1/documents/{document_type}/
- Sandbox serverhttps://customer-api.sandbox-api.jikoservices.com/api/v1/documents/{document_type}/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://api.business.jiko.io/api/v1/documents/{document_type}/' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'content-length: 52428799' \
-H 'content-type: string'{ "success": true, "document_id": "b792e8ae-2cb4-4209-85b9-32be4c2fcdd6" }
- Production serverhttps://api.business.jiko.io/api/v1/customer/beneficial-owners/
- Sandbox serverhttps://customer-api.sandbox-api.jikoservices.com/api/v1/customer/beneficial-owners/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://api.business.jiko.io/api/v1/customer/beneficial-owners/ \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "items": [ { … } ] }
Use these endpoints to view Transactions of funds moving in and out of Jiko Pockets, specifically the bank account component (cash deposits and withdrawals). For viewing information regarding the brokerage account component (buying and selling of T-bills), use Trades.
Use these endpoints to view Counterparties. Counterparties represent external accounts when moving funds in or out of a Jiko Account. Jiko will only transfer funds between accounts where the Counterparty has status: “VERIFIED”, meaning ownership of the account has been confirmed.