Skip to content
/Reports

Jiko Partner API (Version: fd60d28d)

Introduction

Welcome to the Jiko API Reference! Jiko enables you to integrate money storage and movement, backed by the safety and security of US Treasury Bills. Use the Partner API if you are building an application that embeds Jiko’s services and offers Jiko products to your own customers. The Partner API will then enable your application to interact with Jiko on behalf of your customers.


At the core of our platform is the Jiko Pocket: a pair consisting of a bank account and a brokerage account. When money is deposited into a Pocket, the funds are automatically invested in T-bills. When a payment or withdrawal is made, T-bills are immediately liquidated and used as cash. Customers can have multiple Pockets, and each Pocket is associated with a single T-bill maturity: 4-week, 13-week, 26-week or 52-week.


The API Reference covers everything you need to build a full application leveraging the Jiko platform:


  • Onboarding customers
  • Funding Pockets via ACH or Wire
  • Viewing and managing Pockets (including monthly statements and trade confirmations)
  • Making payments and transfers via ACH, Wire, On-Us (Book) Transfer or Debit Card

When you’re ready to start building, please contact us at partner.support@jiko.io to request sandbox access.

Download OpenAPI description
reference.json
reference.yaml
Languages
Servers
Production server
https://{partner}.partner-api.jikoservices.com
Sandbox server
https://{partner}.sandbox-api.jikoservices.com

Accounts

Use these endpoints to view Account information. Jiko Accounts (also known as Pockets) consist of a bank account and a brokerage account. When funds are deposited into a Pocket, they’re immediately invested in T-bills.


In the API interface, the Account object encapsulates both accounts and can be treated as a single account to deposit to or withdraw from.

Operations

Customers

Use these endpoints to view and manage personal details for a Customer.

Operations

Transactions

Use these endpoints to view Transactions of funds moving in and out of Jiko Accounts, 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.

Operations

Trades

Use these endpoints to view Trades, or transactions related to the buying and selling of T-bills, within the brokerage account component of Jiko Pockets.

Operations

Statements

Use these endpoints to retrieve monthly statements for bank and brokerage accounts.

Operations

Manage Cards

Use these endpoints to view and manage Card information.

Operations

Physical Cards

Use these endpoints to create, view, and manage Physical Debit Cards.

Operations

Virtual Cards

Use these endpoints to create, view, and manage Virtual Debit Cards.

Operations

Businesses

Use these endpoints to initiate, manage, and complete KYB for Businesses. When an application has status: “APPROVED”, a Customer is created for the Business. Customers can have multiple Pockets.

Operations

Individuals

Use these endpoints to initiate, manage, and complete KYC for Individuals. When an application has status: “APPROVED”, a Customer is created for the Individual. Customers can have multiple Pockets.

Operations

Events

Use these endpoints to view Events.

Operations

Health

Use these endpoints to setup automatic health checks for the Partner API.

Operations

Sandbox

Use these endpoints to initiate sandbox functionality.

Operations

Security

Use these endpoints to authenticate requests to the Jiko API.

Operations

Subscriptions

Use these endpoints to create, view, and manage Subscriptions. Subscriptions provide Partners with the ability to subscribe to Events. Once subscribed, Events will be sent to the specified URL.

Operations

Webhooks

Webhooks

Reports

⚠️ Experimental ⚠️ These endpoints are subject to change.

Use these endpoints to interact with Reports.

Operations

List Report RequestsExperimental

Request

Returns a list of report requests

Security
HTTPBearer
Query
customer_idCustomer Id (string) or Customer Id (null)(Customer Id)
Any of:
string(uuid)(Customer Id)
cursorCursor (string) or Cursor (null)(Cursor)
Any of:
string(Cursor)
limitinteger(Limit)[ 0 .. 30 ]
Default 30
typeType (string) or Type (null)(Type)
Any of:
string(Type)
date_fromDate From (string) or Date From (null)(Date From)
Any of:
string(date-time)(Date From)
date_toDate To (string) or Date To (null)(Date To)
Any of:
string(date-time)(Date To)
Headers
x-jiko-idempotencystring(uuid)(X-Jiko-Idempotency)required
x-jiko-signaturestring(X-Jiko-Signature)required
curl -i -X GET \
  'https://your-partner-name.partner-api.jikoservices.com/api/v1/report-requests/?customer_id=497f6eca-6276-4993-bfeb-53cbbbba6f08&cursor=string&limit=30&type=string&date_from=2019-08-24T14%3A15%3A22Z&date_to=2019-08-24T14%3A15%3A22Z' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'x-jiko-idempotency: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
  -H 'x-jiko-signature: string'

Responses

Successful Response

Bodyapplication/json
prev_pagePrev Page (string) or Prev Page (null)(Prev Page)
Any of:
string(Prev Page)
next_pageNext Page (string) or Next Page (null)(Next Page)
Any of:
string(Next Page)
itemsArray of objects(Items)required
items[].​idstring(uuid)(Id)required
items[].​typestring(Type)required
items[].​metadataMetadata (object) or Metadata (null)(Metadata)required
Any of:
object(Metadata)
items[].​created_atstring(date-time)(Created At)required
items[].​reportsArray of objects(Reports)required
items[].​reports[].​idstring(uuid)(Id)required
items[].​reports[].​file_namestring(File Name)required
items[].​reports[].​mime_typestring(Mime Type)required
items[].​reports[].​statusstring(Status)required
Enum"PENDING""AVAILABLE""FAILED"
items[].​reports[].​typestring(Type)required
items[].​reports[].​metadataMetadata (object) or Metadata (null)(Metadata)required
Any of:
object(Metadata)
items[].​reports[].​created_atstring(date-time)(Created At)required
items[].​reports[].​formatReportFormat (object) or null
Any of:
object_typestring(Object Type)
Default "CursorList"
Response
application/json
{
  "prev_page": "cj0xJnA9MjAyMi0xMi0yMSsxNyUzQTIyJTNBMDguNjc5MzQ5JTJCMDAlM0EwMA==",
  "next_page": "cD0yMDIyLTEyLTE5KzE5JTNBNTQlM0EyNy4xODMyNzglMkIwMCUzQTAw",
  "items": [
    { … }
  ],
  "object_type": "CursorList"
}

Create Report RequestExperimental

Request

This endpoint triggers an asynchronous process to create a report request based on the provided parameters. Available report types are:

Type BANK_STATEMENT_REPORT

End-of-day bank statement for the pocket’s bank account, exported in ISO 20022 camt.053 format. Transactions reported in this statement include fund deposits and withdrawals, incoming and outgoing third-party payments (when applicable), fees, automated sweep transactions between the pocket’s bank account and its linked brokerage account.

Note: since Jiko automatically sweeps funds between the bank account and the associated brokerage account in the pocket, the bank account’s end-of-day balance is always 0. To report on balances held with Jiko, we invite you to use:

  • Either the Brokerage statement, to import the value of held T-bills in the cash position of your treasury management system, reported as the closing balance of an account,

  • or the Trade report, to import individual buy and sell transactions into your treasury management system and derive the corresponding position.

Valid output_formats values: CAMT053.

Type BROKERAGE_STATEMENT_REPORT

End-of-day statement for the pocket’s brokerage account, exported in ISO 20022 camt.053 format. With the opening value and closing value of the T-bills held in the pocket on the selected reporting date, represented as the account balance. Values are based on end-of-day market prices, or on the current market price if the report is generated before day-end.

The statement also includes the following records that explain the change between the opening and closing values:

  • Additions: new funds deposited into the brokerage account.

  • Subtractions: funds withdrawn from the brokerage account.

  • Gains/Losses from T-bills held in the account.

  • Fees charged and deducted from the brokerage account.

Valid output_formats values: CAMT053.

Type TRADE_REPORT

List of T-bill buy & sell trades within a user-defined range of trade dates, exported in CSV format. Each trade in the file includes three categories of information:

  • Security master data: CUSIP, issuer, issue date, maturity date.

  • Trading entity parameters: transaction code, custodian details.

  • Trade details: buy/sell indicator, trade date, price, amount, reference.

The date ranges filter has a maximum range of 31 days. Optionally, the date range filter can be configured to be based on either settlement dates, or book dates.

Valid output_formats values: KYRIBA_CSV, CSV.

Type SECURITY_PRICE_REPORT

End-of-day security prices within a user-defined range of dates, exported in CSV format. With:

  • An “SE” field identifying the entry as a security price.

  • The name of the price provider: “JIKO”.

  • The CUSIP of the security.

  • The pricing date.

  • The end-of-day price.

Valid output_formats values: KYRIBA_CSV.

Type POSITION_SUMMARY_REPORT

Provides a snapshot of holdings as of a user-selected date, showing CUSIP-level positions by pocket along with associated cash values. The report includes the following key fields: Pocket, CUSIP, Quantity, Market Price, Market Value, and Historical Cost Value. Customers use this report to export pocket-level valuations to downstream systems and to reconcile imported buy and sell transactions against the quantities reflected in the Position Summary

Valid output_formats values: PDF, CSV.

Security
HTTPBearer
Headers
x-jiko-idempotencystring(uuid)(X-Jiko-Idempotency)required
x-jiko-signaturestring(X-Jiko-Signature)required
Bodyapplication/jsonrequired
idstring(uuid)(Id)required
reportBankStatementReport (object) or TradeReport (object) or SecurityPriceReport (object) or BrokerageStatementReport (object) or PositionSummaryReport (object)(Report)required
Any of:
report.​pocket_idsArray of strings(uuid)(Pocket Ids)required
report.​customer_idstring(uuid)(Customer Id)required
report.​datestring(date)(Date)required
report.​typeany(Type)required
Value "BANK_STATEMENT_REPORT"
output_formatsArray of Output Formats (strings) or Output Formats (null)(Output Formats)

If specified, renders only the specified formats. If not specified, renders all the available formats for the given report. The available formats differ depending on the report being requested. For a description of what formats are available per report, please refer to the Create Report Request endpoint description.

Any of:

If specified, renders only the specified formats. If not specified, renders all the available formats for the given report. The available formats differ depending on the report being requested. For a description of what formats are available per report, please refer to the Create Report Request endpoint description.

[ 1 .. 20 ] items 
curl -i -X POST \
  https://your-partner-name.partner-api.jikoservices.com/api/v1/report-requests/ \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'x-jiko-idempotency: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
  -H 'x-jiko-signature: string' \
  -d '{
    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
    "report": {
      "pocket_ids": [
        "497f6eca-6276-4993-bfeb-53cbbbba6f08"
      ],
      "customer_id": "160c0c4b-9966-4dc1-a916-8407eb10d74e",
      "date": "2019-08-24",
      "type": "BANK_STATEMENT_REPORT"
    },
    "output_formats": [
      "string"
    ]
  }'

Responses

Successful Response

Bodyapplication/json
any
Response
application/json
null

Get Report RequestExperimental

Request

Retrieves a single report request by ID

Security
HTTPBearer
Path
report_request_idstring(uuid)(Report Request Id)required
Query
customer_idCustomer Id (string) or Customer Id (null)(Customer Id)
Any of:
string(uuid)(Customer Id)
Headers
x-jiko-idempotencystring(uuid)(X-Jiko-Idempotency)required
x-jiko-signaturestring(X-Jiko-Signature)required
curl -i -X GET \
  'https://your-partner-name.partner-api.jikoservices.com/api/v1/report-requests/{report_request_id}/?customer_id=497f6eca-6276-4993-bfeb-53cbbbba6f08' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'x-jiko-idempotency: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
  -H 'x-jiko-signature: string'

Responses

Successful Response

Bodyapplication/json
idstring(uuid)(Id)required
typestring(Type)required
metadataMetadata (object) or Metadata (null)(Metadata)required
Any of:
object(Metadata)
created_atstring(date-time)(Created At)required
reportsArray of objects(Reports)required
reports[].​idstring(uuid)(Id)required
reports[].​file_namestring(File Name)required
reports[].​mime_typestring(Mime Type)required
reports[].​statusstring(Status)required
Enum"PENDING""AVAILABLE""FAILED"
reports[].​typestring(Type)required
reports[].​metadataMetadata (object) or Metadata (null)(Metadata)required
Any of:
object(Metadata)
reports[].​created_atstring(date-time)(Created At)required
reports[].​formatReportFormat (object) or null
Any of:
Response
application/json
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "type": "BANK_STATEMENT_REPORT",
  "metadata": {
    "date": "2023-02-06"
  },
  "created_at": "2023-01-01T12:00:00Z",
  "reports": [
    { … },
    { … }
  ]
}

ACH

Use these endpoints to create, view, and manage ACH Transfers.

Operations

Counterparties

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.

Operations

On-Us Transfers

Use these endpoints to create and view On-Us (Book) Transfers between Jiko accounts.

Operations

Portals

Use these endpoints to create and view Portals. Portals allow third-party financial institutions to initiate ACH and wire transfers. A Portal consists of a routing and an account number. Multiple Portals can be created for a single Pocket.

Operations

Wires

Use this endpoint to initiate Wire Transfers.

Operations

Pockets

Operations

Trading Strategies

Operations

Transactions V2

Operations

Health

Use these endpoints to setup automatic health checks for the Partner API.

Operations

Counterparties V2

Operations

© 2026 Jiko Technologies, Inc. All rights reserved.