Platform

Overview

How It Works

Beneficiary Identity

Policy Corridors

Deterministic Finality

Architecture

Security Model

Governance

Integration

Solutions

Corridors Overview

Institutional Overview

Pricing

All Scenarios

Humanitarian Impact Fund

Assurance

Technical Assurance

Verify Receipt

Receipt Example

Developers

Documentation

APIs & Bridges

Architecture Docs

Glossary

BID API

Company

About

Team

Partners

Roadmap

Investors

Contact

Blog

All Documentation

Schedule Consultation
Protocol

JIL API Overview

Definition

JIL Sovereign exposes multiple APIs for institutional integration. The Settlement API handles settlement instruction submission and finality receipt retrieval. The Wallet API manages account operations, transfers, and key management. The BID API provides biometric identity verification. The ISO 20022 Gateway translates between JIL's native format and the international financial messaging standard used by banks worldwide.

Why It Matters

API-first architecture is critical for institutional adoption. Financial institutions do not use web UIs for core operations - they integrate via APIs into existing treasury management systems, order management systems, and compliance platforms. A comprehensive, well-documented API surface reduces integration time from months to weeks.

How JIL Sovereign Addresses This

JIL's APIs follow REST conventions with Zod schema validation, Pino structured logging, and JWT authentication. The Settlement API produces deterministic finality receipts for every operation. The ISO 20022 Gateway enables banks to interact with JIL using their existing SWIFT-compatible messaging infrastructure, dramatically lowering the integration barrier.

Frequently Asked Questions

What APIs does JIL provide?

JIL provides Settlement API, Wallet API, BID API, ISO 20022 Gateway, BEC Settlement API, NACHA Interface, and Global Payment Interfaces - covering the full spectrum of institutional settlement operations.

What format do JIL APIs use?

JIL APIs follow REST conventions with JSON request/response bodies, JWT authentication, Zod schema validation, and structured Pino logging. The ISO 20022 Gateway additionally supports XML messaging.