Off-peak hours in the Cowork/Code subscription

During certain hours of the week the subscription quota is consumed more slowly — the same request takes a smaller share of the monthly limit. The subscription responses show whether the discount applies right now and when it starts.

The discount applies on its own, there is nothing to switch on. The offPeak block reports what has already been taken into account when the quota was consumed, so an app can offer to move a bulk job into a cheap hour. Off-peak hours are not in effect on this platform yet, so today the block does not arrive here at all.

Examples

curl — personal key

curl https://vibecode.bitrix24.com/v1/cowork/state \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

curl https://vibecode.bitrix24.com/v1/cowork/state \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

const res = await fetch('https://vibecode.bitrix24.com/v1/cowork/state', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})

const state = await res.json()
const off = state.offPeak

if (!off || !off.enabled) {
  console.log('Off-peak hours are not in effect for this subscription')
} else if (off.visible === 'now') {
  const discount = Math.round((1 - off.currentMultiplier) * 100)
  console.log(`Quota is consumed ${discount}% more slowly for another ${off.currentWindowEndsInHours} h`)
} else if (off.visible === 'next' && off.nextAtOrBelow) {
  console.log(`An off-peak hour starts in ${off.nextAtOrBelow.inHours} h`)
}

JavaScript — OAuth application

const res = await fetch('https://vibecode.bitrix24.com/v1/cowork/state', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const state = await res.json()

Response fields

The block arrives in two responses and differs in composition.

Both keys are optional. The capability is switched on account by account, and until it is on, the offPeak and touSavedPct keys are absent from the response body entirely.

Response example

A GET /v1/cowork/state response. It shows the off-peak block and the saved share, the remaining fields are in Cowork/Code subscription state.

{
  "offPeak": {
    "enabled": true,
    "visible": "now",
    "timezone": "UTC",
    "currentMultiplier": 0.5,
    "currentWindowEndsInHours": 6,
    "nextAtOrBelow": { "inHours": 1, "multiplier": 0.5 },
    "perModel": false,
    "modelName": null,
    "grid": [
      [0.75, 0.87, 0.87, 0.87, 0.87, 0.87, 0.87, 0.87, 0.75, 0.75, 0.75, 0.75, 0.62, 0.5, 0.75, 0.87, 1, 1, 0.87, 0.87, 0.87, 0.75, 0.75, 0.75],
      [0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.62, 0.62, 0.62, 0.62, 0.75, 0.75, 0.87, 0.87, 0.75, 0.75, 0.75, 0.75, 0.62, 0.5, 0.5],
      [0.5, 0.5, 0.62, 0.62, 0.75, 0.62, 0.62, 0.62, 0.75, 0.75, 0.87, 1, 1, 0.87, 0.75, 0.87, 0.87, 0.75, 0.75, 0.62, 0.62, 0.62, 0.62, 0.62],
      [0.75, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.62, 0.62, 0.62, 0.75, 0.75, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0.87],
      [1, 1, 1, 1, 1, 0.87, 0.87, 0.87, 0.87, 1, 1, 1, 1, 1, 1, 0.87, 0.75, 0.75, 0.75, 0.87, 1, 1, 1, 1],
      [1, 1, 1, 1, 1, 0.87, 0.87, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0.87, 0.87, 0.75, 0.87],
      [0.75, 0.62, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.5, 0.62, 0.75, 0.75, 0.62, 0.62, 0.75, 0.75, 0.87, 0.87, 1, 1, 1, 1, 0.87]
    ],
    "nowCell": { "dow": 1, "hour": 3 }
  },
  "touSavedPct": 12.4
}

The same moment in a GET /v1/cowork/me response — without the grid and without the saved share:

{
  "offPeak": {
    "enabled": true,
    "visible": "now",
    "timezone": "UTC",
    "currentMultiplier": 0.5,
    "currentWindowEndsInHours": 6,
    "nextAtOrBelow": { "inHours": 1, "multiplier": 0.5 },
    "perModel": false,
    "modelName": null,
    "nowCell": { "dow": 1, "hour": 3 }
  }
}

Error response example

404 — subscription not activated:

{
  "success": false,
  "error": {
    "code": "COWORK_NOT_ACTIVATED",
    "message": "No active Cowork/Code subscription for this user+portal"
  }
}

Errors

The full list of common API errors — Errors.

The hint in the exhausted-quota refusal

When a subscription quota window is exhausted, POST /v1/chat/completions answers 402 with the code cowork_quota_exhausted. The body of that refusal carries an optional error.offPeakHint field — in how many hours the block is lifted and which consumption multiplier will be in effect at that moment. An app reads it to decide whether simply waiting is enough.

{
  "error": {
    "message": "Cowork/Code quota exhausted for the 5h window. Wait until 2026-08-10T15:00:00.000Z or upgrade your tier.",
    "type": "insufficient_quota",
    "code": "cowork_quota_exhausted",
    "window": "5h",
    "resetAt": "2026-08-10T15:00:00.000Z",
    "nextTier": "PRO",
    "offPeakHint": { "inHours": 3, "multiplier": 0.5 }
  }
}

The hint arrives only when the capability is enabled for the Bitrix24 account and the unblock moment falls into a discounted hour. Otherwise the offPeakHint key is absent from the body entirely — it never arrives as null, exactly like the other off-peak fields. Off-peak hours are not in effect on this platform yet, so today the hint does not arrive here at all.

The multiplier is computed exactly at the unblock moment; the nearest off-peak window is not searched for. If that hour carries no discount, no hint arrives either — even when a cheap hour starts a little later.

Known specifics

Check for the presence of the offPeak key, not for its value. Until the capability is on for the account, the key is absent from the response body entirely — it does not arrive as null. A client that reads state.offPeak.enabled without checking offPeak itself will throw on such a response.

Branch the interface on visible, not on a threshold of your own. The threshold above which a discount is worth showing is decided on the platform side and is not exposed. Comparing currentMultiplier against a number baked into the client will diverge from the platform the next time that threshold is tuned.

The multiplier is a consumption coefficient, not the discount size. A value of 0.62 means the call takes 62% of the quota share it would take without a discount, that is, consumption is reduced by 38%. The discount size is computed as 1 - currentMultiplier.

nextAtOrBelow looks for a meaningful discount, not for any price drop. That is how it differs from the nextWindow field in the Off-peak schedule: there it is the nearest strictly cheaper hour, here it is the nearest hour whose discount is deep enough to show.

The block stays silent while the subscription is not active. A paused or cancelled subscription gets enabled: false — the schedule no longer applies to it.

touSavedPct is measured against the monthly allowance, not against consumption. The denominator is the same one the month quota bar is a share of, so the two read side by side: «N% used» and «off-peak hours gave back M%». The value is null only when nothing has been saved yet in the current period.

See also

• Cowork/Code subscription state
• Cowork/Code subscription summary
• Off-peak schedule
• Cowork/Code