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

BLNG Billing API

REST API that manages BLNG payment and billing — listing Stripe products and prices, creating Stripe checkout sessions and customer-portal sessions, confirming checkout, and submitting enterprise "contact sales" inquiries. Also declares three Stripe webhook receivers for checkout completion and subscription update/delete. The product catalog endpoint answers unauthenticated.

This API exposes 8 operations across 8 paths, organized into 2 resource areas, and defines 5 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against the base URL https://billing.blng.ai.

8 operations 8 paths 5 schemas 1 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://billing.blng.ai
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

BLNG Billing API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (cognitoUserAuth) using the implicit flow, exposing 4 scopes.

  • cognitoUserAuth — Cognito authorization code flow for users

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 1 GET, 7 POST. They span 2 resource areas: Billing, Webhook. Each is listed below with its method, path, parameters, and response codes.

Billing 5
POST
/billing/requestEnterprise
Submit an enterprise "Contact Sales" inquiry
body → 201400401500
GET
/billing/products
Retrieve available products and their prices
→ 200500
POST
/billing/createCheckoutSession
Create Stripe's checkout session (aka as payment link)
body → 200400403500
POST
/billing/createCustomerPortal
Create a link to customer's billing portal
body → 200400403404500
POST
/billing/confirmCheckout/{stripeCheckoutSessionId}
Confirm Stripe Checkout Session
1 param → 200400403404500
Webhook 3
POST
/billing/webhook/checkoutSessionCompleted
Webhook to handle checkout session completed event
body → 200400500
POST
/billing/webhook/customerSubscriptionUpdated
Webhook to handle customer subscription updates
body → 200400500
POST
/billing/webhook/customerSubscriptionDeleted
Webhook to handle customer subscription deletion
body → 200400500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CreateCheckoutSessionRequest (5 properties), StripeSubscription (3 properties), CheckoutSessionCompletedRequest (3 properties), CreateCustomerPortalRequest (2 properties). Each schema is shown below with its type and property counts.

Price
object
1 property
CreateCustomerPortalRequest
object
2 properties
CreateCheckoutSessionRequest
object
5 properties
CheckoutSessionCompletedRequest
object
3 properties
StripeSubscription
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

blng-billing-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of BLNG 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.