API usage statistics for the current API key.
Returns rate-limit status, request counts, and quota usage.
Release any resources held by the client.
The current transport is stateless, so this is a no-op today, but
partners should still call it (or use await using) so the SDK
can add connection pooling later without breaking them.
Explicit resource management hook — enables
await using client = new Vairified({ ... }) (TypeScript 5.2+).
Compact summary for console output.
ReadonlyapiThe resolved API key this client is using.
ReadonlybaseThe resolved base URL (production, staging, local, or custom).
ReadonlyenvThe resolved environment name.
ReadonlytimeoutRequest timeout in milliseconds.
ReadonlymembersMember operations — get, search, find, ratingUpdates.
ReadonlymatchesMatch submission — submit, testWebhook.
ReadonlyoauthOAuth flow — authorize, exchangeToken, refresh, revoke.
ReadonlyleaderboardLeaderboard queries — list, rank, categories.
ReadonlywebhooksWebhook delivery inspection — deliveries.
Async client for the Vairified Partner API.
The client is organized around sub-resources that mirror the REST structure — members, matches, oauth, leaderboard. Each sub-resource is a thin wrapper around the HTTP transport on this object.
Lifecycle
The client holds no persistent connections itself — it's safe to create one per request if you want. But for typical usage, wrap it in
await usingso resources are cleaned up deterministically:await usingrequires TypeScript 5.2+ and Node 20+. If you can't use it, just callawait client.close()manually when you're done.