Fetch Credit Usage details — Guide

First-request guide for Fetch Credit Usage details.

API GUIDE

Fetch Credit Usage details

Fetch Credit Usage details

GET/reporting/v1/usageNo request bodyAuthentication required

Overview

Returns a summary of credit usage and entitlements for the specified API category.

Call the endpoint

Send a GET request to /reporting/v1/usage with the required authentication and parameters.

Supply endpoint parameters

Review the parameter table to see which path, query, or header values the endpoint accepts.

Inspect the response

Use the success response shape to validate the fields your integration receives.

Quickstart

Follow these two steps to make a request and recognize a successful response.

STEP 1

Make a request

REQUEST
curl --request GET \
  --url https://uapi.demandbase.com/reporting/v1/usage?apiProduct=b2bApi \
  --header "Authorization: Bearer $DB_API_KEY" \
  --header "Accept: application/json"
STEP 2

Read the response

SUCCESS RESPONSE · HTTP 200
{
  "summary": {
    "scope": "lifetime",
    "totalCreditsAllocated": 50000,
    "totalCreditsConsumed": 115,
    "totalCreditsAvailable": 49885
  }
}

Request anatomy

Build the request from the method, path, parameters, and payload described below.

Parameters

NameLocationTypeRequiredDescription
apiProductquerystringRequiredAPI product name (e.g., b2bApi)

Request body

This endpoint does not define a JSON request body.

Response anatomy

The endpoint returns 200 for the documented success case. Credit usage details fetched successfully.

The response schema does not enumerate fields; inspect the example response and status code.

Rules

  • Use GET with the path /reporting/v1/usage.
  • Required inputs: apiProduct.
  • Authenticate every request with a valid Demandbase access token.
  • This endpoint does not require a JSON request body.

Filters

The published schema exposes the following endpoint inputs. Use the location column to place each value correctly.

NameLocationTypeRequiredDescription
apiProductquerystringRequiredAPI product name (e.g., b2bApi)

Errors

Handle non-success responses explicitly so your integration can report actionable failures.

StatusMeaning
400Bad Request
401Unauthorized because the user is not authenticated.

Next steps

Try the quickstart

Start with the request example, then replace the sample values with your credentials and data.

Return to the API area

Back to credit-usage

Back to top