Carbium Swap API

Carbium Swap API is the public trading surface for teams that need Solana quotes, routing, and executable transactions without building their own router first.

The current public docs expose two practical integration lanes:

• Q1 on GET /api/v2/quote for the current executable-quote flow
• older v1 quote and swap reference paths for provider-specific and legacy request families

Part of the Carbium Solana infrastructure stack.

Choose your starting point

If you need to...	Start here	Why
Get authenticated and make your first request	Get your API key	Covers the developer portal and the X-API-KEY auth header
Build around the current executable quote flow	Q1	Documents GET https://api.carbium.io/api/v2/quote and the txn payload path
Choose between Q1 and older v1 paths	Swap API Request Families	Maps src_mint vs fromMint, quote-only vs transaction-build paths, and bundle handoff boundaries
Execute the returned transaction end to end	Executing Swaps	Covers sign, submit, and confirm after the quote succeeds
Understand supported route sources	Supported DEXs and Routing Sources	Maps documented provider IDs, route misses, Q1, All Quote, and provider-pinned paths
Troubleshoot failures before signing	Swap API Errors Reference	Covers missing auth, route misses, and empty txn responses
Build a wallet integration	Carbium for Wallet Developers	Keeps the API key backend-side and the signing boundary in the wallet
Build a bot or backend executor	Carbium for Trading Bots	Splits reader, decision, and execution responsibilities cleanly
Check quotas before production rollout	Pricing, Limits and Quotas	Maps plan fit and request ceilings to app shape

What the public docs show today

Surface	What it currently owns	Best fit
GET /api/v2/quote	Quote output, route plan, and executable txn when user_account is present	New integrations using the current Q1 flow
GET /api/v1/quote and GET /api/v1/quote/all	Provider-specific quote and comparison requests using fromMint, toMint, amount, and slippage	Legacy or provider-pinned integrations
GET /api/v1/swap	Execution flags like gasless, mevSafe, and priorityMicroLamports on the older swap surface	Teams maintaining the older request family or comparing behaviors

That split matters because the parameter names are not interchangeable across those families.

📘 Pick one request family per integration path. If you use Q1, stick to src_mint, dst_mint, amount_in, and slippage_bps. If you use the older v1 references, keep the fromMint / toMint / amount style together.

How most teams should integrate

For most new builds, the shortest stable path is:

1. generate a Swap API key in the Carbium developer portal at api.carbium.io
2. request a quote from GET https://api.carbium.io/api/v2/quote
3. include user_account when you need an executable transaction back
4. sign on the correct boundary for your app
5. submit and confirm through Carbium RPC

That keeps the product story simple:

• Q1 owns quote and transaction construction
• your app owns signing
• RPC owns submission and confirmation

If your app needs no-SOL onboarding, keep Gasless Swaps as a separate product decision instead of assuming every route should be gasless by default.

Keep each docs lane narrow

This page is the API landing page, not the full implementation guide. Use the deeper pages when the question changes:

• use Q1 for the current request and response shape
• use Swap API Request Families when you need to choose between Q1 and the older v1 request paths
• use Executing Swaps for signing and RPC submission
• use Supported DEXs and Routing Sources for documented provider IDs, route-source behavior, and no-route interpretation
• use Swap API Errors Reference for pre-sign failures
• use Carbium for Wallet Developers or Carbium for Trading Bots for app architecture decisions

That separation keeps the Carbium API section easier to scan and prevents every page from repeating the same code path.

🔶 Ready to build with Carbium Swap API? Start with the setup flow at carbium.io and get your key at api.carbium.io.