tarkov.dev APItarkov.dev ↗
Access Escape from Tarkov ammunition stats (damage, penetration, armor damage) and full wipe duration history via the tarkov.dev API.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/8ce03f91-33d8-4656-9735-4b3e9452ae06/get_ammo' \ -H 'X-API-Key: $PARSE_API_KEY'
Extract all ammunition types and their stats from the Tarkov.dev GraphQL API, including damage, penetration, armor damage, caliber, speed, and various modifiers.
No input parameters required.
{
"type": "object",
"fields": {
"ammo": "array of objects containing ammunition stats including item name/shortName, caliber, damage, penetrationPower, armorDamage, fragmentationChance, accuracyModifier, recoilModifier, initialSpeed, ammoType, projectileCount, lightBleedModifier, heavyBleedModifier, staminaBurnPerDamage"
},
"sample": {
"data": {
"ammo": [
{
"item": {
"name": "5.56x45mm M855",
"shortName": "M855"
},
"damage": 54,
"caliber": "Caliber556x45NATO",
"ammoType": "bullet",
"armorDamage": 37,
"initialSpeed": 922,
"recoilModifier": 0,
"projectileCount": 1,
"accuracyModifier": 0,
"penetrationPower": 31,
"heavyBleedModifier": 0,
"lightBleedModifier": 0,
"fragmentationChance": 0.5,
"staminaBurnPerDamage": 0.144
}
]
},
"status": "success"
}
}About the tarkov.dev API
This API exposes 2 endpoints covering Escape from Tarkov game data sourced from tarkov.dev. The get_ammo endpoint returns a full list of ammunition types with per-round stats including damage, penetration power, armor damage, caliber, speed, and fragmentation modifiers. The get_wipe_info endpoint returns historical wipe records with start and end dates, individual wipe lengths, and a computed average across the last 6 completed wipes.
Ammunition Data
The get_ammo endpoint takes no input parameters and returns an ammo array. Each object in the array includes the item's full name and short name, caliber classification, damage, penetrationPower, armorDamage, projectile speed, and several modifiers such as fragmentation chance. This covers all ammunition types tracked by tarkov.dev, making it suitable for comparisons across calibers or building ammo-selection tooling.
Wipe History and Duration Statistics
The get_wipe_info endpoint returns two top-level fields. historical_wipes is an array of objects, each containing the patch version, wipe_start date (YYYY-MM-DD), wipe_end date (YYYY-MM-DD, or the string 'Ongoing wipe' for the current cycle), and wipe_length as a human-readable string. The second field, average_wipe_length, is a precomputed string (e.g., '175 days') derived from the last 6 completed wipes, so you don't need to compute the rolling average yourself.
Coverage Notes
Neither endpoint requires authentication or query parameters — both return the full dataset on every call. The wipe data includes an active wipe record with 'Ongoing wipe' as the end date, which your client code should handle explicitly if computing durations. Ammo stats reflect the tarkov.dev dataset at the time of the request; values change when Battlestate Games patches the game and tarkov.dev updates accordingly.
- Build an ammo comparison tool that ranks rounds by penetration power versus armor damage across all calibers.
- Generate a tier list of ammunition for a given caliber using the damage and fragmentation modifier fields.
- Display current wipe status and estimated remaining wipe length based on historical average wipe duration.
- Track wipe cycle patterns over time using historical start and end dates from get_wipe_info.
- Integrate ammo stats into a loadout builder that surfaces penetration and speed data per cartridge.
- Trigger alerts or notifications when a new wipe starts by detecting a changed wipe_start date.
- Compute wipe length variance across patches using the individual wipe_length values in historical_wipes.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.