Partner API Changelog

📡 Subscribe to this changelog via RSS — copy the feed URL into your reader, or run /feed subscribe with it in Slack. Opening it in a browser just shows the raw feed.

• Added Get On-Chain Transfer for fetching a single on-chain transfer by its id, incoming or outgoing. A transfer that is not yours returns 404. Like Create On-Chain Transfer, it is experimental and must be enabled for your account.
• On-chain transfers now include transaction_hash, the hash of the USDC transfer on the blockchain. For an outgoing transfer it is null until the USDC has been sent.
• On-chain transfers now include direction (INCOMING or OUTGOING) and counterparty_wallet_address, the wallet an incoming transfer was sent from. It is null for older incoming transfers, where the sending wallet was not recorded. counterparty_id is now null for incoming transfers.
• ON_CHAIN transactions returned by Get Transaction, List Pocket Transactions and List Customer Transactions now include on_chain_transfer_id, the id of the on-chain transfer they belong to. For an outgoing (DEBIT) transaction, pass it to Get On-Chain Transfer to read the transfer's current transaction_hash.

• The reference now lists the 401, 403 and 404 responses on every endpoint that can return them. 401 means the access token is missing, invalid or expired, 403 that x-jiko-signature does not match the request, and 404 that a resource in the path does not exist. The error schema now includes fields, which input validation errors already return.
• Added Create Pocket (v3), whose body is selected by type. A JIKO_STORE Pocket takes deposit_strategy_id and an optional reinvestment_strategy_id, as before. A JIKO_PAY Pocket takes pocket_name only, since it is always invested in 4-week T-bills; a strategy field on it is rejected with 422. Create Pocket (v2) is unchanged, except that its response for a JIKO_PAY Pocket now reports the 4-week strategies the Pocket opens with rather than echoing the request.

• ACH originations the receiving bank returned now include return_details: the return_code the bank sent (for example R03), its standard Nacha return_reason, and returned_at, when Jiko processed the return. It is set on Get ACH Origination and List ACH Originations, and null on every origination that was not returned, including one rejected before sending or at approval. A returned origination's status stays REJECTED. The transfers.ach.out.rejected webhook carries the same return_details when the origination was returned, including a return that arrives after transfers.ach.out.success. For any other rejection the webhook omits it, and List Events shows it as null.
• all_time_earnings in the Pocket portfolio is now marked deprecated in the schema of List Pockets, Get Pocket and the other Pocket responses. Use Get Earnings for a single Pocket, or Get Customer Earnings for all of a customer's Pockets in one call, instead. The field is still returned for now, and will be removed after 2026-12-04.
• Get Customer Earnings is no longer experimental.
• ACH return transactions, the money that moves back when the receiving bank returns an ACH origination, now include return_details: the return_code the bank sent (for example R01) and its standard Nacha return_reason. They also carry ach_transfer_id, the ID of the returned origination, which Get ACH Origination fetches. return_details is null on every other ACH transaction. ACH returns created before this change carry return_details but no ach_transfer_id. This applies to the v1 and v2 transactions endpoints.

• Added a sandbox endpoint for testing incoming wires, Simulate Wire Receiving. It simulates another bank sending a wire to one of your portals, addressed with the portal's routing_number and account_number. Shortly after, the wire posts on its own: the balance rises and you receive transfers.wire.in.success. A wire to a portal that is closed or does not allow wires does not post. Only available in sandbox.

• Subscriptions can now subscribe to statements.available, sent when a customer's monthly statements for a period have been generated and can be downloaded. The payload carries the customer_id and the period in key, for example 2026-09. Fetch the statements with List Customer Statements. The event is delivered at least once per customer and period, so handle repeats idempotently. It is also returned by List Events, and you can simulate it in sandbox with Trigger Webhook.

• Outgoing wires created in sandbox with Create Wire are now reviewed and processed on their own, so you can test the full flow without waiting on Jiko. Shortly after you create one, it moves from PENDING to SUCCESS and you receive transfers.wire.out.success. Nothing is sent to the beneficiary's bank. Production wires are unchanged.
• Incoming ACH events, transfers.ach.in.success and transfers.ach.in.rejected, now include ach_transfer_id, the ID of the ACH receiving the event is about. Fetch the receiving with Get ACH Receiving. Events sent before this change do not have it, including when returned by List Events.

• ACH transactions now include ach_transfer_id, the ID of the ACH transfer behind the transaction: the ACH receiving for an incoming ACH transaction, or the ACH origination for an origination. It is null for ACH returns, and for incoming ACH transactions created before October 2026.
• Deprecated ach_id on ACH transactions. Use ach_transfer_id instead. ach_id keeps its current values.

• Deprecated the USDC value of type on the on-chain funding instruction returned by Get Funding Instructions. Its replacement is ON_CHAIN, matching Create On-Chain Transfer; the address and chain fields are unchanged. The endpoint still returns USDC today and will switch to ON_CHAIN no earlier than 2026-11-20. Update your integration to accept both values now.
• Added new endpoints for fetching ACH receivings, the ACH entries received into your customers' pockets:
  • List ACH Receivings for fetching receivings, newest first, optionally filtered by pocket_id, customer_id, portal_id, filter[status] (PENDING, PROCESSED or REJECTED) and direction (CREDIT or DEBIT). Filters combine.
  • Get ACH Receiving for fetching a single receiving, optionally scoped to a customer_id. A receiving that is not yours, or not that customer's, returns 404 TransferNotFoundError.
• Each receiving carries its amount, direction, pocket, portal, status and the originator's entry details: company name and identification, entry description, SEC code, trace number, effective entry and settlement dates, payment related information and individual identification number. A REJECTED receiving carries a rejection_reason, and can later become PROCESSED if it is reprocessed.

• Card transactions now include merchant_code, the merchant category code (MCC) reported by the card network. merchant_type remains the human-readable name of that code.

• Create Counterparty now returns a specific error type when it refuses a crypto_wallet_address counterparty:
  • A wallet_address that is not valid for the chain returns 422 InvalidWalletAddressError.
  • A customer who is not eligible for crypto returns 422 CustomerNotEligibleForCryptoError. Only business customers whose identification number has an issuing country are eligible.
  • A customer that cannot be found returns 404 NotFoundError instead of 422 InputValidationError.
  • A counterparty_name longer than 200 characters is rejected with 422 InputValidationError; previously it failed with a 500.
• Update Counterparty now returns 412 CounterpartyUnlinkNotAllowedError when status is set to UNLINKED on a counterparty that is not LINKED. The detail names the counterparty's current status. Previously this 412 had no type or detail.

• Incoming ACH transactions now include remittance_information.

• Added Create On-Chain Transfer to the API reference. It sends USDC from a pocket to a verified crypto_wallet_address counterparty, and status updates are delivered as transfers.crypto.withdrawal.success and transfers.crypto.withdrawal.rejected events. A request that repeats the transfer_id of a withdrawal that was refused returns status REJECTED. This endpoint is experimental and must be enabled for your account before use; contact your Jiko representative to request it. Requests made without it enabled are rejected with a 403.

• Subscriptions can now subscribe to transfers.crypto.deposit.rejected, sent once when Jiko will not credit a crypto deposit to the receiving Jiko Account, with the same payload as the other crypto transfer events. It is also returned by List Events. transfers.crypto.withdrawal.rejected is now also sent when Jiko stops a withdrawal after processing began, not only when it is refused before the account is debited. Each crypto transfer ends with at most one success or rejected event.
• Create Wire now rejects a description that contains characters the Fedwire Funds Service does not accept. Only printable ASCII (letters, digits, space and standard punctuation) is allowed; an accented letter, a line break or a tab is rejected with a 422 InputValidationError whose fields entry has loc ["body", "description"]. Previously such a description was accepted, and the wire could later be rejected.

• Create Counterparty now rejects wire and international_wire counterparties whose name, address, identifier, routing_number or wire_instructions contain characters the Fedwire Funds Service does not accept. Only printable ASCII (letters, digits, space and standard punctuation) is allowed; an accented letter, a line break or a tab is rejected with a 422 InputValidationError that lists each offending field in fields, for example ["body", "address", "city"]. Previously such values were accepted, and a wire to the counterparty could later be rejected. display_name is not restricted.

• Update Customer accepts a new closure_reason value, DECEASED, when closing a customer account.

• Added POST /token/, an OAuth 2.0 token endpoint (RFC 7523 JWT bearer grant). Register a public key in the partner portal, sign a short-lived JWT assertion with the private key, and exchange it for a bearer token — no password is sent. This is now the recommended way to authenticate; see the updated Authentication guide. POST /api/v1/login/ keeps working, and request signing with x-jiko-signature is unchanged.

• Published our versioning and deprecation policy. In short: deprecations are announced in this changelog, deprecated endpoints remain callable for at least three months, and we contact every partner we can see calling an endpoint before it is removed.
• Endpoints deprecated more than six months ago are now hidden from the API reference. They remain fully callable — this is a documentation change only, so no integration breaks today. Hidden in this pass:
  • GET /api/v1/customers/{customer_id}/jiko-accounts/ — use List Pockets for Customer
  • GET /api/v1/jiko-accounts/{account_id}/ — use Get Pocket
  • GET /api/v1/customers/{customer_id}/transactions/ — use List Customer Transactions
  • GET /api/v1/jiko-accounts/{account_id}/transactions/ — use List Pocket Transactions
  • GET /api/v1/jiko-accounts/{account_id}/transactions/{transaction_id}/ — use Get Transaction
  • GET /api/v1/customers/{customer_id}/counterparties/ — use List Counterparties
  • GET /api/v1/customers/{customer_id}/counterparties/{counterparty_id}/ — use Get Counterparty
  • GET /api/v1/jiko-accounts/{account_id}/statements/ — use List Customer Statements

• Subscriptions can now subscribe to crypto transfer events: transfers.crypto.deposit.success, transfers.crypto.withdrawal.success and transfers.crypto.withdrawal.rejected. The payload carries the crypto_transfer_id of the transfer and the jiko_account_id it settled against. These events are also returned by List Events.

• ACH originations can now be created with the CCD Standard Entry Class code, for use when the counterparty is a business rather than a consumer. CCD must be enabled for your account before use; contact your Jiko representative to request it. Requests using it without it being enabled are rejected with a 403. When sec_code is CCD, company_entry_description is required.
• Added a required wire_type field to WIRE transaction activities on the transactions endpoints. It distinguishes an ordinary wire (PAYMENT) from the reversal of a wire booked (REVERSAL) and a wire returned by the counterparty bank (RETURN).
• Added an optional original_wire_id field to WIRE transaction activities. It holds the ID of the wire that was returned, and is only populated for RETURN wires.

• Added a new endpoint to fetch earnings for all of a customer's pockets in a single call. The response contains one entry per pocket plus their exact field-wise aggregate. By default it covers every pocket that is not closed (at most 30 per call); the pocket_id[] filter narrows the request, and is also the way to include a closed pocket explicitly. Like the single-pocket variant, it supports the wtd, mtd, ytd and all-time periods.

• Added an optional display_name field to counterparties. It can be set when creating ach, wire, international_wire, and on_us counterparties, or when updating a counterparty's display_name via the update counterparty endpoint, and is returned on all counterparty responses when listing. Use it to assign a custom name that distinguishes counterparties belonging to the same legal entity.

• Added new endpoints for fetching wires:
  • List Wires for fetching wires, optionally filtered by pocket_id (a single pocket) and/or customer_id (all of a customer's pockets).
  • Get Wire for fetching a single wire, optionally scoped to a customer_id.
• The list endpoint supports filtering by direction (INCOMING or OUTGOING).

• Added new optional fields pricing_timestamp and appreciation_per_second to the Portfolio response on the Pockets endpoints. These are populated for pockets backed by accounts with the real_time_yield attribute, and allow consumers to interpolate total_value forward between server-side price updates as total_value + appreciation_per_second × (now - pricing_timestamp).

• Added new endpoint for fetching all customer ACH originations Listing customer ach originations

• Added new endpoint for fetching all customer cards Listing customer cards
• Added pocket_id as part of the Card result, to determine what pocket the card is associated with.
• Added new endpoint for fetching all customer card orders Listing customer card orders
• Added new optional field magstripe_status to Set Card Status. Supported values are ON and OFF (default). The card_status must be set to ONLINE for the magstripe_status update to take effect.

• Introduced V2 of the Portals API, now with support for on-chain crypto deposit addresses alongside the existing virtual bank account portals.
  • Added List Portals API endpoint.
  • Added List Customer Portals API endpoint.
  • Added Get Portal API endpoint.
  • Added Create Portal API endpoint.
  • Added Update Portal API endpoint.
  • Added Get Funding Instructions API endpoint, returning funding instructions for all payment rails supported by a portal.
• Added a new CRYPTO_DEPOSIT_ADDRESS_PORTAL portal type with chain and wallet_address fields, available to query via the type[] filter on the list endpoints.

• Added new optional field transfer_type to Internal Reallocation transfers. Supported values are BANK_TRANSFER (default) and SECURITY_TRANSFER. BANK_TRANSFER sells the CSIP from the origin pocket and buys new CSIP for the destination pocket (T+1 settlement). SECURITY_TRANSFER moves QCIPs directly between pockets instantly.

• Added new field identifier_type to InternationalWireCounterpartyV2 and CreateInternationalWireCounterpartyRequest models to allow for IBAN account numbers when creating and fetching International Wire Counterparties.

• Subscriptions can now subscribe to incoming wire events: transfers.wire.in.success and transfers.wire.in.rejected. The payload carries the wire_id of the wire and the jiko_account_id it settled against, matching the shape of the existing transfers.wire.out.* events. These events are also returned by List Events. No polling is required to observe an inbound wire.

  Added to this changelog on 2026-09-10; the events have been available since the date above.

• Added new optional field identification_number_issuing_country to Retail and Business applications, that refers to the country that issued the identification number. This field will be made mandatory in the future for identification numbers that aren't a US SSN or EIN.

• Added support for filtering by time_settled in Listing pocket transactions, Listing customer transactions and Listing partner transactions.
• Added support for including sweeps in Listing pocket transactions, Listing customer transactions and Listing partner transactions.

• Added a new way of getting a Single Pocket
• Added a new an endpoint to fetch the earnings for a single pocket
• Deprecated the all_time_earnings field of the Pockets/accounts endpoint response models. This field will be removed after 2026-08-01.

• Added a wire_instructions field to the WireCounterpartyV2 and InternationalWireCounterpartyV2 models.

• Added a new liquidation_value_t0 field to the Pocket model.
• Added a new liquidation_value_t1 field to the Pocket model.

• Added support for filtering by multiple types for Listing customer counterparties.

• Added support for creating an international wire counterparty Creating a counterparty.

• Added support for creating an unverified wire counterparty Creating a counterparty.

• Added new transactions endpoints. Endpoint to fetch transactions for a pocket, endpoint to fetch transactions for a customer and an endpoint to fetch transactions for a partner across all customers.
• Added List Customer Portals API endpoint.

• Added a new endpoint to Update a Counterparty
• Added a new payment_rails field to the Portal model.

• Added a new enum value ALL_TIME_EARNINGS to the omit request field for List all pockets, Listing customer pockets and Getting a pocket.
• The all_time_earnings field is now optional the for Portfolio model

• Added support for filtering by wire id and ON-US transfer id to the List Customer Transactions (V1), List Account Transactions (V1) API endpoints.

• Added support for specifying retry policies for webhook subscriptions in case Jiko encounters HTTP errors calling a subscription URL with a webhook. Subscriptions will by default not have a defined retry policy. See Create Subscription for more information.

• Added counterparty field to on_us_transaction detail model for List Customer Transactions (V1), List Account Transactions (V1) and Get Account Transaction (V1) endpoints.

• Added a new fees field to the Pocket model.

• Added a new attributes field to the Pocket model.

• Added support for filtering by status for Listing customer counterparties.

• Added support for On Us counterparties for Listing customer counterparties.
• Added new Peer To Peer option to Create On-Us Transfer API endpoint.
• Added new return type to on-us transfer representing Peer To Peer transfers
• Updated the PATCH Customer endpoint, for the ability to close an approved customer that has no funds in their accounts.

• Added new Business Document Types ORG_CHART and BUSINESS_DESCRIPTION, that may be requested for a Business Application in Manual review via a Document Request.

• Added ach_id, ach_direction and portal_id fields to the ACH transaction details object of the List Customer Transactions (V1), List Account Transactions (V1) and Get Account Transaction (V1) endpoints.
• Added support for filtering cards by card type to the List Account Cards endpoint
• Added support for filtering cards by time created to the List Account Cards endpoint
• Added new field 'creation_time' to List Account Cards endpoint response model
• Added Get Beneficial Owners API endpoint.

• Added support for creating pre approved ACH counterparty Creating a counterparty.

• Added a PreVerifiedVerification option for Creating a counterparty.

• Added Update Customer Data API endpoint.
• Added new async_mode option when creating on-us transfers

• Added tradable_id field to List Customer Trades and List Customer Transactions (V1) API endpoint.
• Added support for filtering by trade date to and from to List Customer Trades and List Customer Transactions (V1) API endpoints.
• Added support for filtering by types, timestamp_from and timestamp_to to the List Customer Transactions (V1), List Account Transactions (V1) API endpoints.

• Added a way for partners to close pockets via the API. You can now close a pocket by supplying a { "status": "CLOSED", "closure_reason": "<ClosureReasonType>" } object to the Update Pocket endpoint.

• Added a description field to the Security model returned by the pockets endpoints.
• Added support for filtering by status and direction to the List ACH Originations API endpoint
• Added support for filtering by portal id and card id to the List Customer Transactions (V1), List Account Transactions (V1) API endpoints.
• Added support for filtering by status and direction to the List ACH Originations API endpoint
• Added support for filtering by card status to the List Account Cards endpoint.
• Added support for full withdrawals when performing on-us transfers by using the new amount field.
• Added support for listing fees deducted when performing on-us transfers.

• Added a new yield_to_maturity and discount_yield fields to the PocketConfiguration model.

• Added a new endpoint to List all pockets
• Added Get Health Check API endpoint.

• Business Application additions:
  • Added Create Application API endpoint.
  • Added Get Application API endpoint.
  • Added Update Application API endpoint.
  • Added Apply API endpoint.
• Related Party Application additions:
  • Added List Related Party API endpoint.
  • Added Create Related Party API endpoint.
  • Added Delete Related Party API endpoint.
  • Added Update Related Party API endpoint.
• Document Upload additions:
  • Added List Document Requests API endpoint.
  • Added Upload Document API endpoint.
• Wire additions:
  • Added Create Wire API endpoint.

• Added a new optional field micro_deposit to V1 ACHCounterparty model that includes an indication of number of verification attempts for ACH Counterparties verified via Micro Deposits
• Added Close Portal API endpoint.
• Added Update Portal API endpoint.

• Added enum value PENDING to the Get Customer Data account_status field, signalling that a customer has no open pocket.

• Added a new endpoint for Updating a Pocket

• Added a new endpoint for Listing customer pockets.
• Added a new endpoint for Getting a pocket.
• Added Get Account Portal API endpoint.

• Added a new endpoint for Creating a pocket.

• Added a new endpoint for Listing pocket configurations (Now called List Trading Strategies).
• The response from uploading documents now includes a document_id field for future reference.

• Added a new endpoint for Creating a counterparty.
• Added a new endpoint for Listing customer counterparties.
• Added a new endpoint for Getting a single counterparty.
• Added Create Portal API endpoint.
• Added a new category type E-SIGN for the Electronic Communications Disclosure Statement and Consent which was previously in the GENERAL category.

• Added a new WIRE_COUNTERPARTY_VERIFICATION document type.
• File size limits raised to 50 MB for files other than ID_FRONT, ID_BACK, SELFIE and PASSPORT when uploading documents to a customer or application.
• Updated documentation for both file upload endpoints.

• Adds a new category field for agreements returned by the List Agreements endpoint. This category field groups all agreements into 3 categories, BANK, BROKERAGE, or GENERAL.

• Added a new sandbox endpoint for simulating webhook calls, Trigger Webhook.

• Added a new yield_to_maturity field to the Trade model.

• Added a new name field to the Portal model.

• Added a sandbox endpoint to fund accounts via ACH portals.

• Added a new disclosure type, FORM_CRS, for Customer Relationship Summary Forms.

• Added wire_fee_transaction and WIRE_FEE transaction type to the List Customer Transactions (V1), List Account Transactions (V1) and Get Account Transaction (V1) endpoints.

• Added Create On-Us Transfer API endpoint.
• Added Get On-Us Transfer API endpoint.

• Added two optional filtering query parameters to the List Customer Statements endpoint:
  • The type[] query parameter makes it possible to filter by different types of statements, e.g. ?type[]=BANK&type[]=BROKERAGE
  • The key query parameter makes it possible to filter by either a specific month or a year, e.g. ?key=2023-01 or ?key=2022
• Marked the List Account Statements (V1) endpoint as deprecated. Please use the List Customer Statements in future integrations.

• Added a new transaction type and corresponding details object, on_us_transaction to the response model in List Customer Transactions (V1).

• Added optional field originally_onboarded_at to request body in Create Application

• New counterparty type WIRE with a wire field, returned in Get Counterparty (V1) and List Counterparties (V1)

• Added List Customer Statements API endpoint.

• Added Get Customer Data API endpoint.

• Added List Customer Trades API endpoint.
• Added List Customer Transactions (V1) API endpoint.

• Added name field to the List Customer Accounts (V1) and Get Customer Account (V1) API endpoints

• Added Get Account Transaction (V1) API endpoint

• Added List ACH Originations API endpoint