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

30MHz Billing History API

The billing-history API from 30MHz — 6 operation(s) for billing-history.

30MHz Billing History API is one of 127 APIs that 30MHz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 6 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.30mhz.com/api.

8 operations 6 paths 2 schemas 1 DELETE4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.30mhz.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

30MHz Billing History API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 8

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

billing-history 8
GET
/billing-history/organization/{organizationId}/year/{year}/month/{month}
Return billing history
getBillingHistoryByOrganizationIdAndMonth 3 params → 200403
DELETE
/billing-history/organization/{organizationId}/year/{year}/month/{month}
Remove billing history for a specific organization and month, including the…
deleteBillingHistoryByOrganizationAndMonth 3 params → 200403404
GET
/billing-history/organization/{organizationId}
Return billing history
getBillingHistoryByOrganizationId 1 param → 200403
POST
/billing-history/organization/{organizationId}/forecast
Return billing history forecast for current month
getBillingHistoryForecastForCurrentMonth 1 param body → 200403
GET
/billing-history/all-organizations/year/{year}/month/{month}
Return billing history for a specific month for all organisations that are…
getBillingHistoryOrganisationsByMonth 2 params → 200403
GET
/billing-history/all-organizations
Return billing history for all organisations that are billable
getBillingHistoryOrganisationsCurrentMonth → 200403
POST
/billing-history/all-organizations
Generate billing history records for every billable organization for the past…
createSqsBillingHistoryRequest body → 200403
POST
/billing-history
Create billing history entry for an organization
createSqsBillingHistoryRequestForOrganization body → 200403404400

Schemas 2

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

BillingHistoryForecastRequest
object
1 property
BillingHistoryRequest
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

30mhz-billing-history-api-openapi.yml Raw ↑

Other APIs 30MHz publishes across the network.

30MHz Admin API
30MHz Agent API
30MHz App API
30MHz App Cultiwatch API
30MHz App Installation Update API
30MHz App Irrigation API
30MHz App Update API
30MHz Assembly API
30MHz Assembly Update API
30MHz Authorization API
30MHz Billing History Details API
30MHz Billing History Details Update API
Where this information came from

This is an independent, third-party profile of 30MHz Billing History 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.