Vendor billing accuracy
Per vendor, how many of your own-key (BYOK) calls were billed as the vendor's published rule says, how many were charged for a miss, double-charged on a retry or at the wrong price, and the credits and dollars at stake. Same filters as logs_list.
Authorization
bearer In: header
Query Parameters
Start of the window (default: 24 hours ago)
date-timeEnd of the window (default: now)
date-timeLowest HTTP status (inclusive)
100 <= value <= 599Highest HTTP status (inclusive)
100 <= value <= 599column:value pairs to leave out
Vendor billing verdicts; mismatch = charged_for_miss, double_charged_retry or price_mismatch
0 <= value0 <= value0 <= value0 <= valueSearch call, parent or run id, endpoint or error code (substring)
^[A-Za-z0-9_.-]{1,128}$^[A-Za-z0-9_.:/@-]{1,200}$Response Body
application/json
application/json
curl -X GET "https://example.com/v1/logs/billing"{ "object": "billing_summary", "from": "2019-08-24T14:15:22Z", "to": "2019-08-24T14:15:22Z", "by_provider": [ { "provider": "string", "calls": 0, "managed": 0, "checked": 0, "ok": 0, "mismatches": 0, "charged_for_miss": 0, "double_charged_retry": 0, "price_mismatch": 0, "unverifiable": 0, "impact_credits": 0, "impact_micro": 0 } ]}Rename or update a log view PUT
Rename a view or change its query, columns or sharing. You can change your own views; owners and admins can also change shared ones.
Call log facets GET
Counts per value (outcome, status, provider, capability, endpoint, key, client…) and latency/cost ranges for the same filters as logs_list.