Skip to content

PCAT-831 - updates to /skus public docs for reseller integration (updating example section and error codes) #3971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
api-clients-generation-pipeline merged 1 commit into from
Sep 4, 2026
+61 −15
Merged

PCAT-831 - updates to /skus public docs for reseller integration (updating example section and error codes) #3971

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 45 additions & 11 deletions .generator/schemas/v2/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86884,8 +86884,17 @@ components:
$ref: '#/components/schemas/ProductCatalogSKUOnDemandOption'
number_of_units_included_in_price:
description: |-
The number of billable usage units included in the price. `0` for SKUs that are not
priced per unit of usage, such as those whose `pricing_type` is `percent`.
The number of billable usage units that one unit of price covers. Divide measured
usage by this value before multiplying by the price. For example, a SKU priced at `18.00` with
`number_of_units_included_in_price` of `1` costs `18.00` per host, while a SKU priced
at `12.00` with `number_of_units_included_in_price` of `10000` costs `12.00` per
10,000 requests. It is a scaling factor on the price, not a free allotment; included
quantities are in `allotments`. The same factor applies to the price of a tier in
`on_demand_tiered` whose `pricing_unit_type` is `unit`. It does not apply to a tier
whose `pricing_unit_type` is `block`: that tier's `price` is charged for the whole
block bounded by `min_usage_quantity` and `max_usage_quantity`, however much of the
block is used. `0` for SKUs that are not priced per unit of usage, such as those
whose `pricing_type` is `percent`.
example: 1
format: int64
type: integer
Expand All @@ -86904,7 +86913,7 @@ components:
$ref: '#/components/schemas/ProductCatalogSKUPricingType'
sku_name:
description: The human-readable name of the SKU.
example: Infra Pro
example: Infra Host (Pro)
type: string
required:
- billing_dimension
Expand Down Expand Up @@ -186462,7 +186471,10 @@ paths:
this endpoint is not paginated.
operationId: ListProductCatalogSKUs
parameters:
- description: The version of the product catalog contract to return. `v1` is the latest.
- description: |-
The version of the product catalog response contract to return. `v1` is the latest.
This is independent of the `/api/v2` path segment, which is the version of the
Datadog API itself.
example: v1
in: query
name: version
Expand All @@ -186472,7 +186484,8 @@ paths:
- description: |-
The date the returned prices, allotments, and pricing tiers are effective as of, in
`YYYY-MM-DD` format. Defaults to the date of the request, and must not be later
than it.
than it. Set it to a date in a past billing period to reconcile that period against
the prices that were in effect then, rather than today.
example: "2026-07-01"
in: query
name: as_of_date
Expand Down Expand Up @@ -186531,15 +186544,11 @@ paths:
on_demand_list_price: "18.00"
on_demand_tiered:
pricing_type: usage
sku_name: Infra Pro
sku_name: Infra Host (Pro)
id: HOSTS-PRO
type: Sku
- attributes:
allotments:
- child_sku_code: SDS
hourly_quantity: 1
monthly_quantity: 1
parent_sku_code: LLM-OBSERVABILITY-MIN-SPEND
allotments: []
billing_dimension: llm_observability_min_spend
billing_units: requests
currency: USD
Expand All @@ -186566,18 +186575,43 @@ paths:
"400":
content:
application/json:
examples:
default:
value:
errors:
- detail: as_of_date must not be later than the date of the request
source:
parameter: as_of_date
status: "400"
title: Bad Request
schema:
$ref: '#/components/schemas/JSONAPIErrorResponse'
description: Bad Request - version is missing or invalid, or as_of_date is malformed or in the future
"403":
content:
application/json:
examples:
default:
value:
errors:
- detail: this endpoint requires the billing_read or usage_read permission
status: "403"
title: Forbidden
schema:
$ref: '#/components/schemas/JSONAPIErrorResponse'
description: Forbidden - the caller has neither the billing_read nor the usage_read permission
"404":
content:
application/json:
examples:
default:
value:
errors:
- detail: the requested product catalog version is not supported
source:
parameter: version
status: "404"
title: Not Found
schema:
$ref: '#/components/schemas/JSONAPIErrorResponse'
description: Not Found - the requested catalog version is not supported
Expand Down
7 changes: 5 additions & 2 deletions src/datadog_api_client/v2/api/product_catalog_api.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,11 +76,14 @@ def list_product_catalog_sk_us(
that code in ascending order. The whole catalog is returned in a single response, so
this endpoint is not paginated.

:param version: The version of the product catalog contract to return. ``v1`` is the latest.
:param version: The version of the product catalog response contract to return. ``v1`` is the latest.
This is independent of the ``/api/v2`` path segment, which is the version of the
Datadog API itself.
:type version: ProductCatalogSKUsAPIVersion
:param as_of_date: The date the returned prices, allotments, and pricing tiers are effective as of, in
``YYYY-MM-DD`` format. Defaults to the date of the request, and must not be later
than it.
than it. Set it to a date in a past billing period to reconcile that period against
the prices that were in effect then, rather than today.
:type as_of_date: datetime, optional
:rtype: ProductCatalogSKUsResponse
"""
Expand Down
13 changes: 11 additions & 2 deletions src/datadog_api_client/v2/model/product_catalog_sku_data_attributes_response.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,8 +89,17 @@ def __init__(
:param default_on_demand_option: The billing frequency applied to on-demand usage of the SKU by default.
:type default_on_demand_option: ProductCatalogSKUOnDemandOption

:param number_of_units_included_in_price: The number of billable usage units included in the price. ``0`` for SKUs that are not
priced per unit of usage, such as those whose ``pricing_type`` is ``percent``.
:param number_of_units_included_in_price: The number of billable usage units that one unit of price covers. Divide measured
usage by this value before multiplying by the price. For example, a SKU priced at ``18.00`` with
``number_of_units_included_in_price`` of ``1`` costs ``18.00`` per host, while a SKU priced
at ``12.00`` with ``number_of_units_included_in_price`` of ``10000`` costs ``12.00`` per
10,000 requests. It is a scaling factor on the price, not a free allotment; included
quantities are in ``allotments``. The same factor applies to the price of a tier in
``on_demand_tiered`` whose ``pricing_unit_type`` is ``unit``. It does not apply to a tier
whose ``pricing_unit_type`` is ``block`` : that tier's ``price`` is charged for the whole
block bounded by ``min_usage_quantity`` and ``max_usage_quantity`` , however much of the
block is used. ``0`` for SKUs that are not priced per unit of usage, such as those
whose ``pricing_type`` is ``percent``.
:type number_of_units_included_in_price: int

:param on_demand_list_price: The public list price of on-demand usage of the SKU, as a decimal string. The number
Expand Down
Loading