Usage

A day-by-operation rollup, filterable by external_id.

GEThttps://api.easydata.win/v1/usage

free

What you spent, grouped by day and operation - the two axes anything gets reconciled against.

Filter by external_id to attribute spend to one of your own pipelines. That handle is yours, not ours, which is the point of it.

count is metered ITEMS, which for a paged operation is entries rather than targets.

Request #

Field	Type	Notes
`from`	query	YYYY-MM-DD. Defaults to 30 days ago.
`to`	query	YYYY-MM-DD. Defaults to today.
`external_id`	query	Narrow to one of your pipelines.

Call it #

cURL

curl -X GET "https://api.easydata.win/v1/usage" \
  -H "X-API-Key: $API_KEY"

Response #

JSON

{
  "data": {
    "from": "2026-08-02",
    "to": "2026-09-01",
    "total": 4182.5,
    "days": [
      { "day": "2026-09-01", "operation": "profiles.enrich", "credits": 412, "count": 412 },
      { "day": "2026-09-01", "operation": "sales.search.people", "credits": 250, "count": 5 }
    ]
  },
  "meta": { "requestId": "req_8f2ka91x" }
}

Errors #

Status	Type	When
400	`invalid_request`	The body could not be accepted as sent. `error.field` names what was wrong. A field this reference does not list is one of these: an unknown key is refused rather than accepted and ignored, because a typo that is silently dropped is indistinguishable from one that worked.
401	`invalid_api_key`	Missing, malformed, revoked or expired key. Never metered.

Every failure uses the same envelope, and none of them is metered - see Errors.