Skip to main content
GET
/
api
/
v1
/
custom_pipelines
/
creation-allowance
Get Creation Allowance
import requests

url = "https://www.datalab.to/api/v1/custom_pipelines/creation-allowance"

headers = {"X-API-Key": "<api-key>"}

response = requests.get(url, headers=headers)

print(response.text)
{
  "creations_this_cycle": 123,
  "limit": 123,
  "at_cap": true,
  "will_incur_fee": true,
  "fee_cents": 123,
  "cycle_resets_at": "<string>",
  "overage_unit_fee_cents": 0,
  "plan": "<string>"
}

Authorizations

​
X-API-Key
string
header
required

Cookies

​
wos-session
string
​
datalab_active_team
string

Response

Successful Response

2026 custom-processor CREATION allowance preview for the current team (§5).

The frontend uses this BEFORE creating a NEW processor to show the at-cap block (Free / developer hard cap) or the one-time $5 confirmation (Team). All fields are 0/false while ENABLE_2026_PRICING is off (the feature is inert in production).

​
creations_this_cycle
integer
required

Successful NEW-processor creations counted this billing month

​
limit
integer
required

Included creations per month for the team's plan (or per-team override)

​
at_cap
boolean
required

True when a hard-cap plan has used all its included creations (next creation is blocked with 402)

​
will_incur_fee
boolean
required

True when the next creation would incur the one-time overage fee (Team)

​
fee_cents
integer
required

The one-time fee in cents the next creation would incur (0 when within the allowance or hard-capped)

​
cycle_resets_at
string
required

ISO timestamp when the monthly creation count resets

​
overage_unit_fee_cents
integer
default:0

The plan's per-extra-creation fee in cents regardless of current count (0 for hard-cap plans) — lets the UI state the overage policy up front

​
plan
string | null

The plan whose limits apply (the team's active API plan, else 'free')