CountyWar: The ultimate all-county battle royale.

GAME 22 OVER : Game 23 will start on Monday at 7:01 AM MST(AZ) / 14:01 UTC.

COUNTY WAR'S VERY GEEKY API

OK, since we are going to develop what many may find as a totally pointless website that is very long and drawn out, like a test cricket match; we might as well include an open application programming interface (API) to go with it.

The API is simply some of the functions from the CountyWAR site that you can use to develop your own interface to the data and live results. Perhaps, build a desktop app that sounds an alarm when your selected county is engaged in battle. The possibilities are only limited to what you can really do with randomized US counties.

The API is delivered in JSON and there are several endpoints that can be used. Enjoy the API while you engage down your path of expanding your inner-nerdiness.

game SECTION

Many of our endpoints provide a section called game. This section gives some basic information about the live game including:

curGame	The number of the current or last game played. This will increment once per week on Monday mornings.
inProgress	If the value is 1, then there is a live game in progress. A value of 0 indicates that the game has ended.
curRound	The last round number that has been played.
lastBattle	Timecode of when the last battle was conducted.
curEntities	Count of the current number of entities remaining in the game.
sleep	If the value is 1, the game is currently in the overnight cease fire mode where the game is in progress but no battles are taking place. On Monday through Thursdays, the battles resume at 7AM MST/14:00 UTC.

CERTAIN VALUES IN RAW AND FORMATTED VERSIONS

Certain values such as populations and number of entities are provided in the next level down. value contains the value of the variable. formatted is the value of the variable but formatted with commas for display purposes.

GEOGRAPHIC IDENTIFIERS (geoId)

The geoId is a 5-digit zero-filled value that uniquely identifies a county entity. The values are based on the Federal Information Processing Standards (FIPS) code for that county or other third-level entity.

LIVE RESULTS API

Endpoint: https://countywar.com/api/live

This API provides information on the last battle/round that was played. The data in this endpoint updates once per minute during the period of when a live game is in progress.

In addition to the game section described above, this endpoint also includes the following sections:

battle - General information about the last round played. Note: The terms "battle" and "round" are used interchangeably in this game.

battleType	The type of battle being played in this round: W - War - One entity attempts to take the land of the other entity. L - Liberation - One entity has revolted without a fight and has been liberated. In this case, the county becomes independent and subject to future attack as well as eligible to originate its own attacks.
popInvolved	The total population for both the attacker and target which is currently at stake in the current battle in raw and formatted versions.
entityCount	The total number of county entities for both the attacker and the target which is currently at stake in the current battle in raw and formatted versions.
outcome	In the perspective of the attacker: W - Attacker wins the round. (Attacker always wins liberation and free pass rounds) L - Target wins the round. (this element is not displayed in liberation rounds.)
freePass	true if the round was a "free pass" given to the attacker as a result of achieving a perfect 9 hit points in the previous round. Otherwise, it is false.
outcomeText	The plain English account of the battle which is displayed on the main page. The API version does not include the line breaks used on the website presentation.
majorBattle	true if this is considered a major battle, false if not. A major battle is one where both entities current have at least 25 entities each at the time of the battle.

attack and target - These are two separate sections that use the same data structure. Attack is the entity that engaged the Target in the battle. Liberation rounds will only display the attack section:

geoId	The geoID for the controlling county entity.
name	Name of the county entity.
state	Postal abbreviation for the state of the county entity.
pop	Current population of the entity including acquisitions in both raw and formatted versions.
entity	Current count of entities that have been captured by the controlling entity. This is available in raw and formatted versions.
fullName	The county and state formatted on a single line.
outcome	Outcome of this controlling entity in the battle (win or lose).
hitPoints	The total number of hit points that were achieved by the controlling entity in this battle. This value can range from 0~9.

hitPoints - This is a simple array that shows the outcome for each of the 9 fights within the battle. A value of 1 indicates that the attacker won the point where a value of 2 indicates that the target was the winner. Hit points are not used in liberation or free pass rounds.

LEADERBOARD API

Endpoint (entity leaders): https://countywar.com/api/leaderboard
Endpoint (population leaders): https://countywar.com/api/leaderboard/?pop=1

The leaderboard API identifies the top 25 controlling entities. It is updated after each round of the live game. There are two different versions for entity leaders and population leaders.

This API includes the game section shown above.

leader

entity GeoID of the controlling entity with the most entities. If there is a tie, then population will break the tie.

pop GeoID of the contorlling entity with the largest captured population.

leaderboard - Up to 25 of the following values ranked by either entities or population:

pop	Population of the controlling entity in raw and formatted versions.
entity	Number of entities controlled by the controlling entity in raw and formatted versions.
county	Name of the county entity.
state	Postal state abbreviation for the county entity.
name	Name and state of county entity on a single line for display.
geoId	GeoID for the subject controlling entity.

Developer API

REC Privacy Policy | REC GDPR Policy