Skip to content
API status
Core concepts

API credits

Understand how authenticated Management API requests consume credits.

Koneth organizations prepay API credits. Every request that successfully authenticates with a Management API key consumes the active api.request price.

The price is configured by Koneth and may change. Read current pricing in Koneth Console before estimating integration costs.

What is charged

Section titled “What is charged”

An authenticated request is charged before route validation and execution. This includes requests that later return:

  • 400 for invalid input.
  • 403 for a missing scope or server restriction.
  • 404 for a missing resource.
  • 409 for a conflict.
  • 500 for an unexpected server error.

Unauthenticated requests are not charged because Koneth cannot identify an organization wallet.

Read your balance

Section titled “Read your balance”

Use a key with credits:read:

Terminal window
curl --request GET \
  --url https://api.koneth.com/api/v1/management/credits/balance \
  --header "Authorization: Management $KONETH_API_KEY"

The response includes available, reserved, purchased, and consumed credits. lowBalance becomes true when availableCredits is at or below lowBalanceThreshold.

Control usage

Section titled “Control usage”

Webhook delivery is priced separately using the configured webhook.delivery operation price. Delivery attempts can consume credits even if the receiver fails, and insufficient credits can defer delivery. A webhook’s arrival does not itself make a Management API request, but fetching account details in response consumes the usual API request price. See Webhook delivery and recovery.

Live account monitoring uses the configured websocket.account_second price. Each connection consumes that price for every subscribed account and started second. See Live account metrics.

  • Validate inputs in your application before calling Koneth.
  • Cache stable read results for a short period when appropriate.
  • Poll asynchronous commands with exponential backoff.
  • Do not retry 400, 401, 403, or 404 responses automatically.
  • Retry transient failures with a strict attempt limit.
  • Monitor the wallet and notify operators before it reaches the low-balance threshold.