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

Fluence Billing API

Billing and payment related endpoints

Fluence Billing API is one of 12 APIs that Fluence 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, an API reference, and authentication docs.

This API exposes 10 operations across 9 paths, and defines 34 schemas. It is described by OpenAPI 3.1.0, at version 0.10.0.

Requests are made against the base URL https://api.fluence.dev.

10 operations 9 paths 34 schemas 1 DELETE7 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.10.0
Base URL
https://api.fluence.dev
Authentication
HTTP Bearer, API Key
Contact
Cloudless Labs
License
AGPL-3
Resource Areas
1

Authentication & Security 2

Fluence Billing API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (access_jwt_token). An API key is passed in the header as X-API-KEY (api_key). By default, every request must be authenticated.

  • access_jwt_token — JWT token issued by Fluence

Paths & Operations 10

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

Billing 10

Billing and payment related endpoints

GET
/v1/billing/charges/aggregated
Aggregated charges over a date range. startDate is inclusive, endDate is inclusive (charges through the end of the endDate day are included). Optional groupBy/period control the aggregation dimension…
get_aggregated_charges 7 params → 200400401403422500
GET
/v1/billing/charges/total
get_total_charges 4 params → 200400401403422500
POST
/v1/billing/top_up
Create top-up request body → 200400401403422500
GET
/v1/billing/top_up/pending
Get pending top-up → 200400401403422500
GET
/v2/billing/get_history
get_top_up_history_v2 9 params → 200400401403422500
GET
/v2/payment-methods
discover_payment_methods_v2 → 200400401403422500
GET
/v2/top-ups
list_top_ups_v2 6 params → 200400401403422500
POST
/v2/top-ups
create_top_up_v2 body → 201400401403409422500502
GET
/v2/top-ups/pending
get_pending_top_up_v2 → 200400401403422500
DELETE
/v2/top-ups/{intent_id}
cancel_top_up_v2 1 param → 204400401403404409422500

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are TopUpDto (14 properties), TotalChargesEntry (13 properties), PaymentMethodDto (11 properties), TopUpV2Dto (9 properties). Each schema is shown below with its type and property counts.

ResourceTypeDto
string
TopUpDto
object
14 properties 9 required
VmConfigurationSlug
string
ErrorCode
string
Stable, machine-readable error code carried by every non-2xx response. Clients should branch on code rather than parsing the human-readable error string. Statu…
Currency
string
CreateTopUpV2Response
object
5 properties 5 required
TopUpStatusDTO
string
ResponseOutputFormat
string
TopUpRequest
object
2 properties 1 required
PaymentMethodDto
object
11 properties 10 required
IntentId
string
ChargeGroupByDto
string
Resource dimension to aggregate charges by. Defaults to the full (user, resourceId, resourceType) tuple when omitted.
ErrorBody
object
2 properties 2 required
TopUpSortFieldDto
string
Field to order billing history by. amount sorts by the top-up amount; createdAt (the default) is newest-first. Distinct from SortFieldDto because the billing l…
IpAddressType
string
TopUpId
string
PaginatedResponse_TopUpV2Dto
object
2 properties 2 required
PaginatedResponse_TopUpDto
object
2 properties 2 required
SortOrderDto
string
UserId
string
StorageType
string
TotalChargesResponse
object
1 property 1 required
TopUpV2Dto
object
v2-native top-up read DTO. Amounts are integer cents (matching the create input and storage — no legacy 10^8 base units); status is the provider-neutral [TopUp…
9 properties 6 required
PaymentMethodKind
string
PaginationInfo
object
5 properties 5 required
CreateTopUpV2Request
object
3 properties 1 required
TotalChargesEntry
object
13 properties 3 required
PendingTopUpV2Response
object
1 property
TopUpPresentation
Typed presentation handed to the client in the v2 top-up response. Stored in the provider session as JSON (ProviderSession.presentation); adapters write the ta…
ProviderSessionId
string
ChargePeriodDto
string
Time bucket to split aggregated charges into. When omitted, charges are not split by time.
PendingTopUpResponse
object
1 property
ResourceId
string
TopUpV2Status
string
Lifecycle status exposed by the v2 top-up read DTO. It is IntentStatus plus Failed: terminal legacy (copperx) failures have no IntentStatus image, and collapsi…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fluence-billing-api-openapi.yml Raw ↑

Other APIs Fluence publishes across the network.

Fluence Hardware API
Fluence Prices API
Fluence PublicIP API
Fluence SecurityGroup API
Fluence Service API
Fluence SSH keys API
Fluence Storage API
Fluence Subnets API
Fluence Users API
Fluence VMs API
Fluence VPCs API
Where this information came from

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