
Privacy Policy
This policy explains what WOK API processes when you use the website, account, checkout and API, why the data is needed and what choices you have.
Effective 27 October 2026
No advertising trackers We do not use advertising trackers and do not sell personal data.
Payment data stays with the provider WOK API does not receive or store full card details.
You stay in control You may request access, correction or deletion through direct support.
1. Operator and scope
WOK API operates the service at woksteamapi.com. This policy applies to the public website, customer account, checkout and requests made with a WOK API key.
Email, account recovery and message preferences
An email address is linked only after you request it in Account and confirm the verification link. We store the linked address, its verification state, message preferences and delivery records to provide account recovery and the emails you choose. An email typed into an order contact field is not treated as a verified address or marketing consent.
Verification, password recovery and account-security notices are service messages. Optional subscription reminders are separate from promotional emails. News, plan offers and win-back messages require an explicit marketing opt-in. You can change preferences, remove your email or unsubscribe from marketing without disabling account-security notices.
Our configured email delivery provider receives the recipient address and message contents to deliver mail. Access links contain short-lived or purpose-limited tokens. Do not forward them. Our email templates do not contain tracking pixels.
2. Account and authentication data
For a local account we process the login and a salted scrypt password hash. The password itself is never stored in plaintext. For Steam sign-in we process SteamID64, public name, avatar and profile URL returned through Steam OpenID and public profile services. For Discord sign-in we process the Discord user ID, username and avatar hash to verify membership in the WOK API server; the OAuth access token is used only during sign-in and is not stored.
3. Orders and payments
For an order we process the selected plan, subscription term, currency, base price, buyer-paid payment fee rate and amount, exact final total, order and payment status, related identifiers and payment method.
4. API and requested data
We process API usage counters, response times and errors needed to operate and protect the service. At your request, the service retrieves and caches Steam profile and inventory data, game item data and FACEIT profile or statistics data.
5. Why data is processed
We process data to create and secure accounts, authenticate users, deliver subscriptions and API keys, complete and reconcile payments, answer support requests, provide requested API results, maintain caches, measure usage, prevent abuse and fraud, diagnose failures and meet legal obligations.
6. Recipients and external services
Data is disclosed only when necessary to operate the requested feature. Recipients may include the selected payment provider, including Platega where applicable, hosting and infrastructure providers, Steam and FACEIT.
7. Storage and security
Customer sessions last no more than 30 days. Abuse-control counters are normally retained for about 7 days. Contract, payment and security records are retained only as long as necessary to provide the service, resolve disputes, prevent fraud and comply with applicable law.
8. Your choices and policy changes
You may request access to your personal data, correction, deletion or withdrawal of consent by contacting support. We may ask for information needed to verify that the request concerns your account. Legal or security obligations may require us to retain limited records.
Cookies and optional site statistics
We keep your cookie choice for 180 days. If you allow site statistics, a random session token is stored in browser session storage. We record categories of public pages, source and language, activity time, scroll depth and selected actions or errors. A session expires after 30 minutes of inactivity or 8 hours in total; raw statistical records are kept for up to 30 days. This is pseudonymous measurement, not a record of form contents, API keys or private account and order pages.
Choose Necessary only to stop optional browser statistics and remove the current statistical session. Reopen Cookie settings in the footer to change your choice. Linking a source to a new account, first API use and first payment requires the separate sign-up choice described below; you can withdraw that account permission in Cookie settings when signed in.
Aggregate server page counters
Separately from optional browser statistics, the server keeps daily totals for successful public HTML page responses by page category, source category and client category (browser-like, known bot or other). Request headers and approved campaign tags are classified without storing their raw values in these counters. These aggregates use no cookies or persistent visitor identifiers, are not linked to accounts, and are kept for up to 90 days. They count responses, not unique people; sources may be missing or inaccurate, and browser-cache or in-page navigation may not reach the server.
To estimate visits without counting every reload as a new visit, the server keeps a temporary keyed code derived from the trusted network address in RAM, using a random secret for that process. The fixed window is 30 minutes, resets at a new UTC day and restarts with the process. Neither the raw address nor this code is saved in the analytics database. The bounded memory cache holds only expiry times and a set of page categories already counted, not an ordered browsing history. No cookies, device fingerprint or account links are used for these estimates.
Only daily aggregate estimates are saved for up to 90 days. Shared addresses can merge different people; address changes and restarts can split a visit. Capacity limits or an unavailable address can leave coverage incomplete. These are approximate network visits, not unique people. Detailed page transitions and last observed pages use the separate optional browser statistics after your consent.
Optional source measurement
Only if you tick the separate optional box at sign-up, WOK stores a short-lived first-party consent token (20 minutes) and then the source, medium and campaign buckets with your account’s registration, first successful API use and first payment times. The account-linked record is deleted after 90 days. It contains no IP, email, SteamID, API key, raw URL, order ID or request data. You can decline and still register, sign in and buy normally. Browser-reported source labels are approximate; milestones are confirmed by the server. No Google tag, advertising cookie or conversion upload is enabled. Only fixed categories of public entry pages and page languages are stored; older or unsupported values are unknown. These categories are reported by the browser and may be inaccurate.
Steam API for your build
Inventories, item prices and player profiles through one API key. Build trading tools, bots and services for players.
1,000 requests per 30 days on Free Developer. No payment required.
/faceit/data/v4/players{
"games": {
"cs2": {
"skill_level": 10,
"faceit_elo": 2100
}
}
}
Example fields. Values are illustrative.
Explore the API referenceFrom a Steam profile to your product
Enter a public Steam profile to see items and prices
2 free lookups per day per IP. No signup.


AWP | Asiimov (Field-Tested)
$128.40
Recoil Case
$0.35Example values, not current market prices
Your players are already here
Inventory data across eight games
Built for your product
Built for your next Steam project
Connect Steam data to the tools your users already need.
Inventory & portfolio tools
Show what a public inventory contains and what its items are worth, with price sources and freshness included.
Trading & market analytics
Bring item prices into your own comparison tools. Choose a price source and handle missing quotes explicitly.
Bots & player dashboards
Add Steam profiles, inventories and FACEIT rank to community bots and player pages using one API key.
The integration
The data behind your next feature
Use a single HTTP API instead of connecting inventory, pricing and player data separately.
Explore the API reference
/v1/inventoryInventories and item prices
Read items and inventory values for CS2, Rust, TF2, Dota 2, PUBG, s&box, Unturned and PAYDAY 2. Each response shows available prices and unpriced items.
/faceit/data/v4Steam profiles and FACEIT stats
Add player profiles, FACEIT level, ELO and match stats to your app. Use your WOK key; no separate FACEIT key is needed.
/v1/inventoriesBatch requests for player lists
Request up to 20 players and four games in a batch, with a result for each player-game pair. Each requested pair uses one quota unit.
meta.cache_ageKnow how fresh your data is
Read inventory cache age and per-item price sources. Refresh prices from the local catalog without rescanning a fresh stored inventory.
Compare the cost of your workload
Inventory API costs in WOK, SteamWebAPI and SteamApis for the same number of requests
| Service | Monthly cost | Included requests | Requests per minute |
|---|---|---|---|
| WOK- | -per 30 daysOptional auto-renewal | Included requests-per 30 days | Requests per minute- |
| SteamWebAPI- | -per month | Included requests-per month | Requests per minute- |
| SteamApisRequest allowance | -per month | Included requests-per month | Requests per minuteNot published |
How we compare
Standard inventory lookups for one player and one game, without batching or forced refresh. Other endpoints and included data differ by provider.
30 days with requests spread evenly across the day. Published monthly, daily and per-minute limits are taken into account. Allow headroom for traffic peaks.
WOK plans are prepaid by default. For a new 30-day plan, you can choose automatic renewal through Stripe at checkout.
SteamApis: lowest request cost including published overage rates. Overage requires it to be enabled and enough account balance. Its inventory rate limit is not publicly specified. This is a cost estimate; throughput at the selected volume has not been verified.
WOK: a suitable listed plan comes first. Quota packs are added only when no listed plan covers the selected volume. Each pack adds 1M units and 50k/day for $45 until the current quota reset. Packs are one-time purchases and do not increase the per-minute limit. Current per-key ceilings apply. The estimate assumes a new 30-day window.
Published limits per minute: WOK Ultra 1200 / Titan 2000 quota units; SteamWebAPI Inventory High+ 200 requests. Batch calls can use multiple WOK units.
One batch of 20 players across 4 games uses 80 quota units, the maximum of 80 player-game pairs per call.
Official pricingSteamWebAPISteamApis
WOK prices come from the current plan catalogCompetitor prices checked
Your first request
Your first inventory request
Get a key, keep it on your server and request a public inventory. Start with curl, Python or JavaScript, then use the response in your app.
# Keep WOK_API_KEY on the server curl --fail-with-body \ -H "Authorization: Bearer $WOK_API_KEY" \ "https://woksteamapi.com/v1/inventory?steam_id=$STEAM_ID&game=cs2"
Every public endpoint, in one place
Exact parameters, response shapes and status codes from the running service.
Use one WOK API key as Authorization: Bearer on data endpoints. WOK holds the Steam key server-side. Cross-origin browser requests are not supported; keep your WOK key on your server. Health is public.
Install a typed client
Download version 1.3.0 for the methods in this reference.
npm install --offline --ignore-scripts ./woksteamapi-client-1.3.0.tgzpython -m pip install --no-index --no-deps ./wok_api-1.3.0-py3-none-any.whlnpm and PyPI releases are published separately. Verify downloads before installation and keep API keys on your server.
Connect a server or agent in three calls
The same WOK API key works for every included game and player endpoint. WOK holds the Steam Web API key on its servers.
- Get your WOK keyCopy it from your account and store it on your server as
WOK_API_KEY. SendAuthorization: Bearer <WOK_API_KEY>; never send a WOK key to Steam or put it in a URL. - Check the keyCall
GET /v1/key. It reports whether the key is active and how much quota remains without spending a request. - Choose a game and endpointUse
GET /v1/inventory?steam_id=STEAMID64&game=rustfor Rust inventory. Change onlygamefor another named game. Rust achievements and playtime have separate routes below.
curl -H "Authorization: Bearer ${WOK_API_KEY}" "https://woksteamapi.com/v1/key"
curl -H "Authorization: Bearer ${WOK_API_KEY}" "https://woksteamapi.com/v1/inventory?steam_id=${STEAM_ID}&game=rust"
curl -H "Authorization: Bearer ${WOK_API_KEY}" "https://woksteamapi.com/v1/rust/achievements?steam_id=${STEAM_ID}"
Use a 17-digit SteamID64 for Rust stats and friends. Inventory and profile routes also accept profile URLs and vanity names. Read the complete integration guide for response fields, errors and examples.
| Game | game | Steam AppID | Additional routes |
|---|---|---|---|
| Counter-Strike 2 | cs2 | 730 | CS2 inspect with add-on |
| Rust | rust | 252490 | /v1/rust/stats, /v1/rust/achievements, /v1/rust/playtime |
| Dota 2 | dota2 | 570 | Inventory, prices, catalog, history |
| Team Fortress 2 | tf2 | 440 | Inventory, prices, catalog, history |
| PUBG | pubg | 578080 | Inventory, prices, catalog, history |
| s&box | sandbox | 590830 | Inventory, prices, catalog, history |
| Unturned | unturned | 304930 | Inventory, prices, catalog, history |
| PAYDAY 2 | payday2 | 218620 | Inventory, prices, catalog, history |
Choose an integration path
Working examples, supported games and the limits your application should handle.
Steam API pricing
Start with a free key or choose a paid plan. Pay once, or choose automatic renewal through Stripe. Request quotas use 30-day windows.
Prepay 3 months and save 5%, 6 months 10%, or 12 months 15%. Billed once; add-ons are priced separately.
Add only what your integration needs
Buy an add-on for an active subscription. Payment and activation are fully automatic.
Choose an active subscription, pay, and the new capability appears automatically after confirmation.
Questions
WOK systems
Current public health from the same production node that serves API traffic.
HTTP health and application response
Production worker answered this check
A live database read completed
Checks in this browser session
Each mark is a real health response collected while this page is open.
GET /healthzYour WOK access
Subscriptions, orders and API keys under one protected account.
Privacy Policy
This document explains what WOK API stores, why it is needed and how to request access, correction or deletion.
User Agreement
Terms for accounts, API subscriptions, payments, delivery, acceptable use and support.
Contact WOK API
Write directly about payments, account access, API behavior or personal data.
Start building
Your next idea starts with one request
1,000 requests per 30 days on Free Developer. No payment required.
