Skip to content
DocktDocktDOCKT

Get credit balances and current-month overage

GET
/v1/account/credits
curl --request GET \
  --url https://api.dockt.com/v1/account/credits \
  --header 'Authorization: Bearer <token>' \
  --header 'x-dockt-expected-workspace: wsp_example'

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Header Parameters

Section titled “Header Parameters”
x-dockt-expected-user

Rejects the request with 401 unless the browser session belongs to this auth_user_id. This assertion does not grant authority.

string
>= 1 characters
x-dockt-expected-workspace

Unique Dockt workspace identifier.

Query Parameters

Section titled “Query Parameters”
cursor
string
<= 16000 characters
limit
string

Responses

Section titled “Responses”

200

Section titled “200”

Envelope for a single resource response.

Media typeapplication/json

Envelope for a single resource response.

object
object
required
string
Allowed values: single
data
required

Provider balances and current UTC calendar-month uncovered custom-unit charges. Overage amounts retain each conversion line’s fiat unit. Retrieval time is not an ingestion watermark. Null balance/unit means unavailable, never zero.

object
object
required
string
Allowed values: account_credits
retrieved_at
required

ISO 8601 date-time string.

string format: date-time
allowances
required

Envelope for a paginated collection response.

object
object
required
string
Allowed values: list
data
required
Array<object>
object
id
required
string
/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$/
type
required
string
Allowed values: PREPAID POSTPAID CREDIT
name
required
Any of:
string
remaining
required
Any of:

Exact decimal representation of the provider value. Units are never combined or converted by Dockt.

string
unit
required
Any of:
object
id
required
string
/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$/
name
required
string
priority
required
Any of:
number
applicable_product_ids
required
Array<string>
applicable_product_tags
required
Array<string>
applicable_contract_ids
required
Array<string>
specifiers
required
Array<object>
object
product_id
string
/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$/
product_tags
Array<string>
presentation_group_values
object
key
additional properties
string
pricing_group_values
object
key
additional properties
string
exclude
Array<object>
object
product_tags
Array<string>
schedule
required
Array<object>
object
starting_at
required

ISO 8601 date-time string.

string format: date-time
ending_before
required

ISO 8601 date-time string.

string format: date-time
amount
required

Exact decimal representation of the provider value. Units are never combined or converted by Dockt.

string
has_more
required
boolean
next_cursor
required
Any of:
string
overage_period
required
object
starting_at
required

ISO 8601 date-time string.

string format: date-time
ending_before
required

ISO 8601 date-time string.

string format: date-time
overage
required
Array<object>
object
invoice_id
required
string
/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$/
amount
required

Exact decimal representation of the provider value. Units are never combined or converted by Dockt.

string
unit
required
object
id
required
string
/^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$/
name
required
string
provider_status
required
string
Allowed values: DRAFT FINALIZED
starting_at
required

ISO 8601 date-time string.

string format: date-time
ending_before
required

ISO 8601 date-time string.

string format: date-time
Example
{
  "object": "single",
  "data": {
    "object": "account_credits",
    "retrieved_at": "2026-08-06T09:30:00Z",
    "allowances": {
      "object": "list",
      "data": [
        {
          "type": "PREPAID",
          "schedule": [
            {
              "starting_at": "2026-08-06T09:30:00Z",
              "ending_before": "2026-08-06T09:30:00Z"
            }
          ]
        }
      ]
    },
    "overage_period": {
      "starting_at": "2026-08-06T09:30:00Z",
      "ending_before": "2026-08-06T09:30:00Z"
    },
    "overage": [
      {
        "provider_status": "DRAFT",
        "starting_at": "2026-08-06T09:30:00Z",
        "ending_before": "2026-08-06T09:30:00Z"
      }
    ]
  }
}

400

Section titled “400”

Problem Details response for HTTP 400. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/invalid-request",
  "title": "Bad request",
  "status": 400,
  "detail": "The request did not match the expected schema.",
  "instance": "req_example1042"
}

401

Section titled “401”

Problem Details response for HTTP 401. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/missing-auth",
  "title": "Unauthorized",
  "status": 401,
  "detail": "Send a valid bearer token or browser session.",
  "instance": "req_example1042"
}

403

Section titled “403”

Problem Details response for HTTP 403. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/forbidden",
  "title": "Forbidden",
  "status": 403,
  "detail": "The authenticated principal does not have the required permission.",
  "instance": "req_example1042"
}

404

Section titled “404”

Problem Details response for HTTP 404. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/not-found",
  "title": "Not found",
  "status": 404,
  "detail": "The requested resource was not found in the authenticated scope.",
  "instance": "req_example1042"
}

409

Section titled “409”

Problem Details response for HTTP 409. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/conflict",
  "title": "Conflict",
  "status": 409,
  "detail": "The request conflicts with the current resource state.",
  "instance": "req_example1042"
}

422

Section titled “422”

Problem Details response for HTTP 422. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/validation",
  "title": "Validation failed",
  "status": 422,
  "detail": "Correct the invalid fields and send the request again.",
  "instance": "req_example1042",
  "errors": {
    "issues": [
      {
        "path": [
          "body",
          "inputs",
          "3",
          "value"
        ],
        "message": "Expected a two-letter country code."
      }
    ]
  }
}

429

Section titled “429”

Problem Details response for HTTP 429. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/rate-limit",
  "title": "Too many requests",
  "status": 429,
  "detail": "Wait for the Retry-After interval before retrying.",
  "instance": "req_example1042"
}

500

Section titled “500”

Problem Details response for HTTP 500. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "type": "https://docs.dockt.com/errors/internal",
  "title": "Internal server error",
  "status": 500,
  "detail": "Retry the request safely or contact Dockt support with the request ID.",
  "instance": "req_example1042"
}

503

Section titled “503”

Problem Details response for HTTP 503. The type URI is the stable machine-readable error code.

Media typeapplication/problem+json

Standard error response with a stable status, human-readable detail, and optional validation errors.

object
type
required
string
title
required
string
status
required
number
detail
required
string
instance
required
Any of:

Request identifier that Dockt support can use to trace an API call.

string
errors

Structured request validation issues.

object
issues
required
Array<object>

One request validation issue with a stable field path and human-readable message.

object
path
required
Array
message
required
string
Example
{
  "instance": "req_example1042"
}