Support

Get Carbium support faster: choose the right help path, include useful debugging context, and use the official Discord, FAQ, status, and docs links.

Support

Use this page when you need help with Carbium RPC, Swap API, DEX, Data, SPDR Validator, or docs.

The fastest path is usually:

  1. check the relevant docs page for the product you are using
  2. check live status when the issue looks operational
  3. open a support thread in the official Carbium Discord with the right context

Part of the Carbium Solana infrastructure stack.


Start with the right path

If your issue is about...Start hereWhy
RPC endpoint behavior, status, monitoring, or errorsStatus and MetricsHelps separate provider health, usage, and request-shape problems
Swap API auth, routing, quote, or missing transaction payloadsSwap API Errors ReferenceCovers failures before a signed transaction reaches Solana
API keys, endpoint restrictions, or exposed secretsAPI Key Security Best PracticesGives the rotation and containment checklist
Carbium Data token search, lookup, batch, or logo callsToken API CallsMaps the live public Token Index API endpoints
General product, links, or account routingFAQ and Official LinksKeeps broad questions out of technical incident threads

If the issue still needs human help, use the official Discord link below.

🔶

Join the official Carbium Discord: discord.com/invite/P292DS7qe3


What to include in a support request

Short, specific reports get handled faster than screenshots without context.

Include:

  • product surface: RPC, gRPC, Swap API, DEX, Data, SPDR, or docs
  • endpoint or page URL involved
  • approximate time of failure, including timezone
  • HTTP status, JSON-RPC error, API error body, transaction signature, or bundle id when available
  • request id, wallet address, or mint only when it is safe and relevant
  • what you expected to happen
  • what actually happened
  • whether the issue is reproducible

Do not post private keys, seed phrases, bearer tokens, API keys, session cookies, or unpublished customer data in public channels.


Support-ready examples

RPC or gRPC

Good:

Product: Carbium RPC
Endpoint type: HTTPS RPC
Method: getSignaturesForAddress
Time: 2026-05-15 04:20 UTC
Symptom: intermittent HTTP 429 after deploy
What changed: new portfolio refresh job went live
Already checked: rate-limit page and monitoring dashboard

Avoid:

RPC is broken, please check.

Swap API

Good:

Product: Carbium Swap API
Endpoint: GET /api/v2/quote
Pair: SOL -> USDC
Symptom: quote succeeds, txn is empty
Already checked: user_account is included, amount is in smallest units
Error body: no HTTP error body, only empty txn

Avoid:

Swap does not work.

Carbium Data

Good:

Product: Carbium Data
Endpoint: POST /tokens/batch
Batch size: 500 mints
Symptom: 429 responses from one backend IP
Already checked: Data Rate Limits and local cache behavior

Avoid:

Data API is slow.

Before sharing logs

Sanitize logs before posting them.

Sensitive valueWhat to do
API keysRemove or replace with CARBIUM_API_KEY_REDACTED
Wallet seed phrases or private keysNever share them
Session cookies or auth headersRemove them
Customer wallet listsShare one safe example only if needed
Transaction signaturesUsually safe, but include only the relevant signature

If a secret was exposed, rotate it first. Then open a support request with the timing and affected product surface.


Where live status fits

Use status.carbium.io when an issue looks service-wide:

  • many unrelated requests fail at the same time
  • dashboard or portal access changes suddenly
  • error rates rise without a deployment on your side
  • multiple team members or regions see the same behavior

Use the product docs when the issue is tied to one request, one token pair, one wallet, one API key, one endpoint family, or one integration path.

📘

Support can help faster when the report shows whether the problem is operational, request-shaped, route-specific, wallet-specific, or caused by a recent deploy.