POST
/
v1
/
c
/
usage
curl --request POST \
  --url http://127.0.0.1:8080/v1/c/usage \
  --header 'Content-Type: application/json' \
  --header 'wb-key: <api-key>' \
  --data '{
  "customer_id": "Cust_c40bea18-c0c9-44b1-bd0c-43f5283e1670",
  "feature_slug": "<string>",
  "is_absolute": true,
  "metadata": {},
  "timestamp": "2023-11-07T05:31:56Z",
  "units": "<string>"
}'

This simplified, single-event usage reporting endpoint is suitable for logging individual events during testing. For production use, refer to the more powerful bulk endpoint designed to handle batches of multiple events.

Authorizations

​
wb-key
string
header
required

Body

application/json

Structure to report Usage for Usage-based features in a Contract Currently the only reporting strategy supported is additive, meaning that all reported usage units are summed for the billing period. This requires additional care from the reporter to ensure that no double-reporting takes place

Response

200

Recorded

POST
/
v1
/
c
/
usage
curl --request POST \
  --url http://127.0.0.1:8080/v1/c/usage \
  --header 'Content-Type: application/json' \
  --header 'wb-key: <api-key>' \
  --data '{
  "customer_id": "Cust_c40bea18-c0c9-44b1-bd0c-43f5283e1670",
  "feature_slug": "<string>",
  "is_absolute": true,
  "metadata": {},
  "timestamp": "2023-11-07T05:31:56Z",
  "units": "<string>"
}'

This simplified, single-event usage reporting endpoint is suitable for logging individual events during testing. For production use, refer to the more powerful bulk endpoint designed to handle batches of multiple events.

Authorizations

​
wb-key
string
header
required

Body

application/json

Structure to report Usage for Usage-based features in a Contract Currently the only reporting strategy supported is additive, meaning that all reported usage units are summed for the billing period. This requires additional care from the reporter to ensure that no double-reporting takes place

Response

200

Recorded