https://docs.jiko.io/products/partner-api/changelog Changes to the Jiko Partner API. en-us Wed, 21 Oct 2026 00:00:00 GMT https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-21 Wed, 21 Oct 2026 00:00:00 GMT

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 2027-01-21. Update your integration to accept both values now.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-20 Tue, 20 Oct 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-09 Fri, 09 Oct 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-08 Thu, 08 Oct 2026 00:00:00 GMT

Incoming ACH transactions now include remittance_information.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-07 Wed, 07 Oct 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-06 Tue, 06 Oct 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-05 Mon, 05 Oct 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-10-02 Fri, 02 Oct 2026 00:00:00 GMT

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

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-09-30 Wed, 30 Sep 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-09-10 Thu, 10 Sep 2026 00:00:00 GMT

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

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-09-02 Wed, 02 Sep 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-09-01 Tue, 01 Sep 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-08-13 Thu, 13 Aug 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-07-23 Thu, 23 Jul 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-06-09 Tue, 09 Jun 2026 00:00:00 GMT

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).

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-06-03 Wed, 03 Jun 2026 00:00:00 GMT

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).

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-05-08 Fri, 08 May 2026 00:00:00 GMT

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

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-05-07 Thu, 07 May 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-05-05 Tue, 05 May 2026 00:00:00 GMT

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.

]]> https://docs.jiko.io/products/partner-api/changelog https://docs.jiko.io/products/partner-api/changelog#2026-04-22 Wed, 22 Apr 2026 00:00:00 GMT

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.

]]>