For the complete documentation index, see llms.txt. This page is also available as Markdown.

Introduction

Colibri packages have independent versions. See [compatibility and releases](getting-started/compatibility.md) for the stability and versioning policy.

Colibri

Colibri is a TypeScript toolkit for Stellar applications. Use a focused client for a common workflow, a transaction pipeline when you need to attach plugins, or an individual process when you need to control orchestration.

These guides explain how and why to use the APIs. The API and error reference links every package's generated symbol documentation and lists every declared error code by context.

Choose your task

I want to…
Start here

Install a package and submit a payment

Read or invoke a Soroban contract

Generate a typed contract client

Build a React application

Choose fees, signers, and authorization

Adjust Soroban budgets and resource fees

Read current ledger state

Follow events or historical ledgers

Authenticate a wallet or contract account

Rebuild and compare a contract's Wasm

Render an account or contract identicon

Run a disposable local ledger

Packages

Install only the packages your application needs. Events, account/address helpers, ledger readers, and transaction orchestration belong to Core; the other packages provide focused capabilities.

Package
Scope

Accounts, assets, contracts, signing, processes, pipelines, ledger data, and events

Typed clients, validated values and event definitions from a contract ABI

Providers, wallet connections, queries and explicit transaction hooks

Live/archive ingestion with callbacks and checkpoints

SEP-10 and SEP-45 client authentication

SEP-58 and caller-supplied reproducible build verification, API and CLI

SEP-33 SVG, PNG and image data, with extended C-address support

Fee sponsorship for transaction pipelines

Reusable sponsored transaction-source accounts

Opt-in receiving-account memo checks

Docker-backed Stellar Quickstart lifecycle

How to read the guides

Start with a complete tutorial, then follow the scoped guides for configuration, failure handling, or customization. Short fragments illustrate one step; they are not independent scripts unless explicitly labeled. Placeholder secrets, contract IDs, and example domains must be supplied by your application.

The architecture guide explains the shared process → step → pipeline → client layering. The error-handling guide explains stable codes and safe diagnostics.

Resources

Last updated