From db9397659d16037fa7b8a1895a0a8f752f81955a Mon Sep 17 00:00:00 2001 From: tlotemporal Date: Wed, 17 Jun 2026 12:40:12 -0700 Subject: [PATCH] Update billing-api.mdx Updates to billing API documentation for 6/24 GA. Remvoed Public preview link and added N+1 account support language --- docs/cloud/billing-and-usage/billing-api.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/cloud/billing-and-usage/billing-api.mdx b/docs/cloud/billing-and-usage/billing-api.mdx index f58f494ec7..b3e5b3ce7d 100644 --- a/docs/cloud/billing-and-usage/billing-api.mdx +++ b/docs/cloud/billing-and-usage/billing-api.mdx @@ -15,9 +15,6 @@ tags: import { ReleaseNoteHeader } from '@site/src/components'; - The Temporal Cloud Billing API provides Namespace-level cost attribution through on-demand billing reports. Reports are delivered in CSV format and can be accessed via API or downloaded directly for use in FinOps tooling and cost management platforms. @@ -68,6 +65,11 @@ Within a single account: Report generation time varies and is not guaranteed. Factors that affect it include the size of the requested date range and overall platform load. +###Multiple Accounts under One Billable Entity + +To preserve account isolation, Billing API requests originating from a Temporal Account that is linked to others for billing purposes will only receive billing data associated with that Temporal Account. Support/Platform charges will be associated with the First (ie oldest) Temporal Account associated with the billable entity. + + ## Best practices Provide an idempotency key (`async_operation_id`) when retrying requests.