How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Clerk Billing API

Billing-related endpoints for managing statements and payment attempts.

Clerk Billing API is one of 104 APIs that Clerk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Billing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 16 operations across 13 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 2025-11-10.

Requests are made against a single base URL, https://api.clerk.com/v1.

16 operations 13 paths 42 schemas 1 DELETE10 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025-11-10
Base URL
https://api.clerk.com/v1
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Clerk Billing API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (sk__) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Secret key, obtained under "API Keys" in the Clerk Dashboard.

Paths & Operations 16

Across 13 paths, the API surfaces 16 operations — 1 DELETE, 10 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Billing 16

Billing-related endpoints for managing statements and payment attempts.

GET
/users/{user_id}/billing/subscription
Retrieve a User's Billing Subscription
GetUserBillingSubscription 1 param → 200400401403404422500
GET
/users/{user_id}/billing/credits
Retrieve a User's Credit Balance
GetUserBillingCreditBalance 1 param → 200400401403404422500
POST
/users/{user_id}/billing/credits
Adjust a User's Credit Balance
AdjustUserBillingCreditBalance 1 param body → 200400401403404409422500
GET
/organizations/{organization_id}/billing/subscription
Retrieve an Organization's Billing Subscription
GetOrganizationBillingSubscription 1 param → 200400401403404422500
GET
/organizations/{organization_id}/billing/credits
Retrieve an Organization's Credit Balance
GetOrganizationBillingCreditBalance 1 param → 200400401403404422500
POST
/organizations/{organization_id}/billing/credits
Adjust an Organization's Credit Balance
AdjustOrganizationBillingCreditBalance 1 param body → 200400401403404409422500
GET
/billing/plans
List All Billing Plans
GetCommercePlanList 4 params → 200400401422500
GET
/billing/prices
List All Billing Prices
GetBillingPriceList 4 params → 200400401404422500
POST
/billing/prices
Create a Custom Billing Price
CreateBillingPrice body → 200400401404422500
GET
/billing/subscription_items
List All Subscription Items
GetCommerceSubscriptionItemList 8 params → 200400401422500
DELETE
/billing/subscription_items/{subscription_item_id}
Cancel a Subscription Item
CancelCommerceSubscriptionItem 2 params → 200400401403404422500
POST
/billing/subscription_items/{subscription_item_id}/extend_free_trial
Extend Free Trial for a Subscription Item
ExtendBillingSubscriptionItemFreeTrial 1 param body → 200400401403404422500
POST
/billing/subscription_items/{subscription_item_id}/price_transition
Create a Price Transition for a Subscription Item
CreateBillingPriceTransition 1 param body → 200400401403404409422500
GET
/billing/statements
List All Billing Statements
GetBillingStatementList 3 params → 200400401422500
GET
/billing/statements/{statementID}
Retrieve a Billing Statement
GetBillingStatement 1 param → 200400401404422500
GET
/billing/statements/{statementID}/payment_attempts
List Payment Attempts for a Billing Statement
GetBillingStatementPaymentAttempts 4 params → 200400401404422500

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are schemas-CommercePlan (29 properties), schemas-CommerceSubscriptionItem (26 properties), CommerceSubscriptionItem (26 properties), BillingPaymentAttempt (23 properties). Each schema is shown below with its type and property counts.

schemas-FeatureResponse
object
6 properties 6 required
PaginatedBillingStatementResponse
object
2 properties 2 required
schemas-CommercePayerResponse
object
13 properties 9 required
PaginatedBillingPriceResponse
object
2 properties 2 required
CommerceTotalsResponse
object
6 properties 4 required
ExtendFreeTrialRequest
object
1 property 1 required
AdjustCreditBalanceRequest
object
5 properties 3 required
PaginatedBillingPaymentAttemptResponse
object
2 properties 2 required
CommercePerUnitTotalTier
object
3 properties 2 required
CommercePaymentSourceResponse
object
17 properties 12 required
CommerceProrationCreditDetailResponse
object
4 properties 4 required
CommercePaymentMethodResponse
object
17 properties 10 required
CommercePlan
object
19 properties 17 required
CommercePerUnitTotal
object
3 properties 3 required
FeatureResponse
object
6 properties 6 required
ClerkErrors
object
3 properties 1 required
PaginatedCommercePlanResponse
object
2 properties 2 required
CommerceCreditsResponse
object
3 properties 3 required
BillingStatement
object
8 properties 8 required
CommerceSubscriptionItemSeatsResponse
object
2 properties 1 required
CommercePriceTransitionResponse
object
3 properties 3 required
CommercePlanUnitPrice
object
3 properties 3 required
CommerceSubscriptionItem
object
26 properties 13 required
CommerceMoneyResponse
object
4 properties 4 required
CreateBillingPriceRequest
object
5 properties 2 required
schemas-CommerceSubscriptionItem
object
26 properties 13 required
schemas-CommercePlan
object
29 properties 25 required
CommerceSubscriptionItemNextPaymentResponse
object
2 properties
CommerceSubscriptionCreditResponse
object
2 properties
BillingPaymentAttempt
object
23 properties 20 required
BillingPriceResponse
object
13 properties 12 required
CommercePayerCreditResponse
object
2 properties 2 required
CommerceCreditBalanceResponse
object
2 properties 2 required
PriceTransitionRequest
object
2 properties 2 required
PaginatedCommerceSubscriptionItemResponse
object
2 properties 2 required
CommercePayerResponse
object
13 properties 3 required
CommerceSubscription
object
12 properties 10 required
ClerkError
object
4 properties 3 required
CommercePriceTransitionDetails
object
9 properties 7 required
CommercePlanUnitPriceTier
object
3 properties 2 required
CommerceCreditLedgerResponse
object
9 properties 8 required
CommerceSubscriptionNextPayment
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clerk-com-billing-api-openapi.yml Raw ↑

Other APIs Clerk publishes across the network.

Clerk Account Portal API
Clerk Active Sessions API
Clerk Actor Tokens API
Clerk Agent Tasks API
Clerk Allow-list / Block-list API
Clerk API Keys API
Clerk Application Transfers API
Clerk Applications API
Clerk Backup Codes API
Clerk Beta Features API
Clerk Checkouts API
Clerk Clear Site Data API
Where this information came from

This is an independent, third-party profile of Clerk Billing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.