Warera Python Client
A robust, fully-typed, async-first Python client for the WarEra tRPC API (v0.25.0-beta).
import warera
async def main():
user = await warera.user.get_by_id("12345")
prices = await warera.item_trading.get_prices()
gov = await warera.government.get("7")
Features
- Full API coverage — all endpoints across 32 resource namespaces.
- Fully Typed — Pydantic v2 models for every request and response.
- Async-first — built on
httpx.AsyncClient; sync shim included. - Cursor pagination — transparent
auto_items=Truegenerator andcollect_all()time-slicing engine. - Batch requests —
BatchSessionfor multiple procedures in one HTTP round-trip; auto-chunkedget_manyfor ID lists. - Smart batch splitting — any batch larger than the server's hard limit of 50 is automatically split and fired concurrently; no manual chunking needed.
- Adaptive rate limiting — reads
ratelimit-remaining/ratelimit-resetresponse headers and sleeps exactly as long as the server says. - Resilient — automatic retry with exponential backoff on 429 and 5xx errors.
- Optional auth —
X-API-Keygives higher rate limits; works anonymously too.
Installation
pip install warera-client
Requires Python 3.10+.
Quick Start
Async (recommended)
import asyncio
import warera
# The global module automatically reads WARERA_API_KEY from your environment.
# You can also manually set it via: warera.set_api_key("YOUR_KEY")
async def main():
# Simple lookups
user = await warera.user.get_by_id("12345")
country = await warera.country.find_by_name("Ukraine")
gov = await warera.government.get(country.id)
prices = await warera.item_trading.get_prices()
print(user.username, country.name)
print(f"Iron: {prices.get('iron').price}")
# Paginated
page = await warera.user.get_paginated(country_id=country.id, limit=50)
for u in page.items:
print(u.username)
asyncio.run(main())
Sync
import warera.sync
warera.sync.set_api_key("YOUR_KEY")
user = warera.sync.user.get_by_id("12345")
prices = warera.sync.item_trading.get_prices()
Authentication
# Option 1 - pass key directly
client = WareraClient(api_key="abc123")
# Option 2 - environment variable (recommended for scripts/CI)
# export WARERA_API_KEY=abc123
client = WareraClient() # key picked up automatically
# Option 3 - no key (anonymous, lower rate limits)
client = WareraClient()
Rate Limiting
You can inspect the current quota at any time via client.rate_limit_remaining and
client.rate_limit_total (both return None until the first response is received):
async with WareraClient(api_key="YOUR_KEY") as client:
await client.user.get_by_id("1")
print(client.rate_limit_remaining) # e.g. 499
print(client.rate_limit_total) # e.g. 500
All Resource Methods
For a complete, detailed list of all 32 resource namespaces, their signatures, and the returned Pydantic models, please refer to the API Reference Documentation.
Pagination
Every paginated endpoint exposes three calling patterns:
# 1. Single page - manual cursor control
page = await client.battle.get_many(is_active=True, limit=20)
print(page.items) # list[Battle]
print(page.next_cursor) # str | None
print(page.has_more) # bool
# 2. Async generator - yields items one by one across all pages
async for battle in client.battle.get_many(is_active=True, auto_items=True):
print(battle.id)
# 3. Collect all pages into a flat list using the ultra-fast parallel time-slicing engine
all_battles = await client.battle.collect_all()
(Note: The old paginate() wrapper and auto_paginate=True parameter have been fully removed in 0.2.0).
Batch Requests
| What you call | What happens |
|---|---|
client.batch() with ≤ 50 items |
One POST |
client.batch() with > 50 items |
Auto-split into ≤ 50-item chunks, fired concurrently |
client.company.get_many(200_ids) |
4 × 50-item POSTs, results merged in order |
session._http.post_batch(120_procs, ...) |
Auto-split internally, 3 × concurrent POSTs |
You never need to think about the limit - just pass what you need.
Mixed procedures
async with client.batch() as batch:
country_item = batch.add("country.getCountryById", {"countryId": "7"})
gov_item = batch.add("government.getByCountryId", {"countryId": "7"})
prices_item = batch.add("itemTrading.getPrices", {})
dates_item = batch.add("gameConfig.getDates", {})
# After the block - all resolved in one POST:
country = country_item.result
gov = gov_item.result
prices = prices_item.result
dates = dates_item.result
Large batches
# 200 company IDs → 4 concurrent POSTs of 50, results merged
companies = await client.company.get_many(list_of_200_ids)
# Same for any resource with get_many
users = await client.user.get_many(user_ids) # list[User]
regions = await client.region.get_many(region_ids) # list[Region]
rounds = await client.round.get_many(round_ids) # list[Round]
mus = await client.mu.get_many(mu_ids) # list[MilitaryUnit]
Partial failure handling
async with client.batch() as batch:
good = batch.add("country.getAllCountries", {})
bad = batch.add("company.getById", {"companyId": "nonexistent"})
print(good.ok) # True
print(bad.ok) # False
if not bad.ok:
print(bad._error) # WareraNotFoundError
Wire format (for reference)
POST /trpc/proc0,proc1,...,proc49?batch=1
Content-Type: application/json
X-API-Key: <token>
{"0": {input0}, "1": {input1}, ..., "49": {input49}}
Request Cancellation (AbortController)
If you trigger a massive collect_all() task but the user closes their browser or navigates away, you don't want the SDK to keep burning API rate limits on background requests. You can gracefully abort operations using a CancellationScope.
from warera import CancellationScope
async def fetch_data(scope: CancellationScope):
try:
async with scope:
# If scope.cancel() is called elsewhere, this instantly raises asyncio.CancelledError
# Any HTTP request waiting in the 5ms batch queue is silently pruned before hitting the network!
data = await client.user.collect_all()
except asyncio.CancelledError:
print("Operation was gracefully cancelled!")
# Elsewhere in your application:
# scope.cancel()
Persistent SWR Caching
By default, the SDK uses an in-memory true-LRU OrderedDict to cache static endpoints like gameConfig using Stale-While-Revalidate semantics.
To persist this data across bot restarts or server crashes, you can configure the client to use the SQLiteCacheBackend.
from warera.cache_backends import SQLiteCacheBackend
# Creates or connects to cache.db in the current directory
client = WareraClient(cache_backend=SQLiteCacheBackend("cache.db"))
Request Priority
In complex applications, you may have background workers fetching millions of records while a user clicks a button that needs an instant response. To prevent the user's request from getting stuck behind 10,000 background jobs in the auto-batching queue, use RequestPriority.HIGH.
from warera import RequestPriority
# This request jumps to the very front of the internal batching queue
# and will be dispatched in the next immediate physical HTTP POST (≤ 5ms)
critical_user = await client.user.get_by_id("123", priority=RequestPriority.HIGH)
Error Handling
from warera.exceptions import (
WareraError, # base - catch everything
WareraUnauthorizedError, # 401 - bad/missing API key
WareraForbiddenError, # 403
WareraNotFoundError, # 404
WareraRateLimitError, # 429 - auto-retried; raised after all retries exhausted
# .retry_after → float | None (seconds from Retry-After header)
WareraServerError, # 5xx - auto-retried
WareraValidationError, # Pydantic parse failure
WareraBatchError, # one or more batch items failed
# .errors → dict[int, WareraError]
# .results → dict[int, Any]
)
try:
user = await client.user.get_by_id("99999")
except WareraNotFoundError:
print("User not found")
except WareraRateLimitError as e:
print(f"Still rate-limited after retries. Retry after: {e.retry_after}s")
except WareraError as e:
print(f"API error: {e}")
Configuration
WareraClient(
api_key: str | None = None, # also reads WARERA_API_KEY env var
base_url: str = "https://api2.warera.io/trpc",
timeout: float = 30.0, # HTTP request timeout in seconds
max_retries: int = 3, # retry attempts for 429 / 5xx errors
initial_delay_ms: int = 250, # initial retry delay in ms
max_delay_ms: int = 5000, # max retry delay in ms
backoff_multiplier: float = 2.0, # exponential backoff multiplier
jitter: bool = True, # add random jitter to delays
batch_size: int = 50, # max procedures per batch POST chunk
# values above 50 are silently clamped
# to the server's hard limit
auto_batch_delay: float = 0.005, # wait time in seconds to accumulate batch chunks
event_hooks: dict | None = None, # dict mapping 'request'/'response' to async hooks
headers: dict | None = None, # additional custom HTTP headers to send
retryable_status_codes: set | None = None, # custom HTTP status codes to trigger retry
on_retry: Callable | None = None, # called before each retry sleep with a RetryInfo
)
# on_retry example — feed retries into your own logs/metrics:
def log_retry(info: warera.RetryInfo) -> None:
print(f"retry #{info.attempt}: HTTP {info.status_code}, waiting {info.delay_s:.2f}s")
client = WareraClient(on_retry=log_retry)
# You can also configure the extreme maximum concurrency for massive bulk fetching operations
# (defaults to 500 to perfectly match the API rate limit). Dial this down to 50 or 100 if you
# are running in constrained environments to save memory.
# export WARERA_MAX_CONCURRENCY=50
Project Structure
warera/
├── __init__.py # public API surface
├── client.py # WareraClient
├── sync.py # sync shim
├── exceptions.py # error hierarchy
├── _enums.py # all StrEnum classes from schema
├── _http.py # httpx session, GET/POST, rate-limit headers, retry
├── _pagination.py # paginate(), collect_all()
├── _batch.py # BatchSession, BatchItem, fetch_many_by_ids
├── models/ # Pydantic response models (31 files)
└── resources/ # Resource classes (32 files)
Development
git clone https://github.com/wareraprojects/api-client-py
cd api-client-py
pip install -e ".[dev]"
# Unit tests (no API key needed)
pytest tests/unit/ -v
# Integration tests (live API)
WARERA_API_KEY=your_key pytest tests/integration/ -v
# Lint + type check
ruff check warera/
mypy warera/
License
MIT
Credits
- WarEraProjects: Massive credit to WarEraProjects team as well as all other contributors for the TypeScript Wrapper which gave a foundational reference to work with on bringing the wrapper features into python.
Metadata
Release files for warera-client 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| warera_client-0.2.4.tar.gz | 194.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| warera_client-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 302.5 kB
Release files / warera_client-0.2.4.tar.gz
| Download URL | warera_client-0.2.4.tar.gz |
|---|---|
| Size | 194.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06c66dbfd2c83d888365f46c6099fe1ad67d3deb50f5aff20fa2f3c5cfedb84d
|
|
BLAKE2b-256 checksum How to use checksums |
2de9f3cd87bb7965b891325b234a61835ec83598dd0daf4d1df49f1efffc7eea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2026.
Transparency logRelease files / warera_client-0.2.4-py3-none-any.whl
| Download URL | warera_client-0.2.4-py3-none-any.whl |
|---|---|
| Size | 107.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d435d8629a6eae2ba5d3e55be35c53a09e41e9319bb10acc5417787d17f0a862
|
|
BLAKE2b-256 checksum How to use checksums |
8b0bb5432c39ac04d9cd2017a0bf43b7a5e13b011042872ec34dac4a7f409ec1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2026.
Transparency logSecurity for warera-client 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for warera_client-0.2.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.