Retrieve a customer-meter aggregate
Returns a single customer-meter aggregate for the specified customer + meter pair. Returns 404 only if the meter itself does not exist on the merchant — if the meter exists but the customer has zero events, the response returns an aggregate with total_quantity: 0, event_count: 0, last_event_at: null.
/customer-meters/{customer_id}/{meter_id}Returns a single customer-meter aggregate for the specified customer + meter pair. Returns 404 only if the meter itself does not exist on the merchant — if the meter exists but the customer has zero events, the response returns an aggregate with total_quantity: 0, event_count: 0, last_event_at: null.
Related endpoints
GET /customer-meters— List a customer's meter usage
Common errors
401 authentication_error— missing, invalid, expired, or revoked credential. Codes:authentication_failed,invalid_api_key,expired_api_key,api_key_revoked,session_invalid,merchant_required. Carries aWWW-Authenticate: Bearerchallenge.404 resource_missing— the referenced resource does not exist or is not visible to your key.
Your RevKeen merchant API key. Create and manage keys in Dashboard → Settings → Developer. Use rk_sandbox_* for staging/test and rk_live_* for production. The same key may be sent as Authorization: Bearer <key> if that suits your HTTP client better. A missing, invalid, expired, or revoked key returns 401 with a WWW-Authenticate: Bearer challenge; a valid key without the required scope returns 403.
In: header
Path Parameters
Customer UUID
uuidMeter UUID
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://api.revkeen.com/v2/customer-meters/11111111-1111-4111-8111-111111111111/11111111-1111-4111-8111-111111111111" \
-H "x-api-key: $REVKEEN_API_KEY"Synthetic documentation data, validated against the response schema; not a live API result.
{ "data": { "object": "customer_meter", "customer_id": "c2a1e7d4-5b3f-4a8e-9d21-6f0b3e4c7a11", "meter_id": "7c8d9e0f-1a2b-4630-8d4e-5f6a7b8c9d01", "meter_name": "API calls", "meter_event_name": "api_call", "aggregation": "count", "unit_name": "calls", "total_quantity": 4820, "event_count": 4820, "last_event_at": "2026-04-18T09:15:00.000Z" }}