FarmOps Public API

Quick start

# 1. Create an alliance key in alliance settings, or a read-only
#    server key from the server's "API Access" page.
#    Keys are bound to exactly one alliance or server.
# 2. Export power history as CSV:
curl -H "Authorization: Bearer fops_live_<your-key>" \
     "https://www.lastwar.farm/api/v1/alliance/members/power?format=csv"

# 3. Import power values:
curl -X POST -H "Authorization: Bearer fops_live_<your-key>" \
     -H "Content-Type: application/json" \
     -d '{"entries":[{"name":"PlayerOne","power":12500000}]}' \
     https://www.lastwar.farm/api/v1/alliance/members/power

# 4. List server players with a server-scoped key:
curl -H "Authorization: Bearer fops_live_<server-key>" \
     "https://www.lastwar.farm/api/v1/server/players?page=1&pageSize=100"

To use the Postman collection: download it and import via File → Import in the Postman desktop or web app. Calls return AUTO_SYNC_REQUIRED when alliance Auto Sync is inactive, or TRIAL_EXPIRED when the key's tenant lacks active Pro access.

Historical Train rosters

Export up to 100 dates per page with an alliance READ key. JSON returns a nextCursor; CSV returns X-Next-Cursor. Pass that date as the exclusive before cursor to download older pages. Future planned rosters are excluded.

# Export the latest 100 historical dates (IDs and replacement versions included):
curl -H "Authorization: Bearer fops_live_<your-key>" \
     "https://www.lastwar.farm/api/v1/alliance/train/history?format=csv&limit=100" \
     -o train-history.csv

# Preview an edited CSV with a WRITE key before committing:
curl -X POST -H "Authorization: Bearer fops_live_<write-key>" \
     -H "Content-Type: text/csv" \
     -H "Idempotency-Key: train-history-import-20260930-001" \
     --data-binary @train-history.csv \
     "https://www.lastwar.farm/api/v1/alliance/train/history?preview=true"

# After review, commit the same CSV and key without preview=true.
# Retry a failed commit response with the exact same key and payload.

Imports require the key creator to remain an owner, admin, or manager, and the alliance must allow writes. Each date replaces its full roster, so omitted positions become empty. Existing dates need their current exported version, including unchanged rosters; a blank version creates a new date only. Preview applies the same checks and writes no history or receipt. A stale version rejects the whole batch; export and review again before using a new operation key.

JSON accepts member IDs. CSV accepts IDs or exact, unambiguous current or alternate names; an ID takes precedence. Former members and sparse seats are allowed. Limits are 2 MiB, 100 dates, and 2,300 occupied position rows. Reusing a committed key with an edited payload returns REQUEST_CONFLICT. The Train section below includes JSON and CSV examples and all error responses.