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

Habu Billable Configs API

The Billable Configs API from Habu — 2 operation(s) for billable configs.

Habu Billable Configs API is one of 34 APIs that Habu publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version v1.0.0.

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

3 operations 2 paths 7 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0.0
Base URL
https://api.habu.com/v1/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Habu Billable Configs API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (application) using the clientCredentials flow. By default, every request must be authenticated.

Paths & Operations 3

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

Billable Configs 3
GET
/billable-configs
Get billable config
getBillableConfig 3 params → 200400401403404500
POST
/billable-configs
Upsert billable config
upsertBillableConfig body → 200400401403404500
DELETE
/billable-configs/{billableConfigId}
Delete billable config
deleteBillableConfig 1 param → 200400401403404500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are BillableConfig (5 properties), ReturnObject (2 properties), UpsertBillableConfigResponse (2 properties), UpsertBillableConfigRequest (1 property). Each schema is shown below with its type and property counts.

UpsertBillableConfigResponse
object
2 properties
GetBillableConfigResponse
object
1 property
ReturnObject
object
2 properties 2 required
BillableConfig
object
Billable configuration for a source entity
5 properties 2 required
DeleteBillableConfigResponse
object
1 property
UpsertBillableConfigRequest
object
1 property 1 required
BillableSourceType
string
Type of entity a billable config applies to

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

habu-billable-configs-api-openapi.yml Raw ↑

Other APIs Habu publishes across the network.

Habu Cleanroom API
Habu Cleanroom Datasets API
Habu Cleanroom Destinations API
Habu Cleanroom Exports API
Habu Cleanroom Flow Runs API
Habu Cleanroom Flows API
Habu Cleanroom Partners API
Habu Cleanroom Question Datasets API
Habu Cleanroom Question Permissions API
Habu Cleanroom Question Result Shares API
Habu Cleanroom Question Run Schedule API
Habu Cleanroom Question Runs API
Where this information came from

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