API documentation for the Monster Hunter World API (https://mhw-db.com)
CharmRank objects, the name field is now deprecated, and will be removed in v1.19.0.$size operator..length fields are now deprecated in favor of the $size operator for querying relationship length.Weapon.attributes.elderseal to Weapon.elderseal.Weapon.attributes.phialType to Weapon.phial (charge blade / switch axe only).Weapon.attributes.ammoCapacities to Weapon.ammo (bowguns only).Weapon.attributes.coatings to Weapon.coatings (bows only).Weapon.attributes.specialAmmo to Weapon.specialAmmo (bowguns only).Weapon.attributes.deviation to Weapon.deviation (bowguns only).Weapon.attributes.boostType to Weapon.boostType (insect glaive only).Weapon.attributes.damageType to Weapon.damageType.Weapon.attributes.shellingType to Weapon.shelling (gunlance only).attributes.elderseal field is now deprecated in favor of the elderseal field. It will be removed in v1.17.0.attributes.phialType field is now deprecated in favor of the phial field. It will be removed in v1.17.0.attributes.ammoCapacities field is now deprecated in favor of the ammo field. It will be removed in v1.17.0.attributes.coatings field is now deprecated in favor of the coatings field. It will be removed in v1.17.0.attributes.specialAmmo field is now deprecated in favor of the specialAmmo field. It will be removed in v1.17.0.attributes.deviation field is now deprecated in favor of the deviation field. It will be removed in v1.17.0.attributes.boostType is now deprecated in favor of the boostType field. It will be removed in v1.17.0.attributes.damageType is now deprecated in favor of the damageType field. It will be removed in v1.17.0.attributes.shellingType is now deprecated in favor of the shelling field. It will be removed in v1.17.0.The big features in this update are support for monster rewards, which have been asked for a lot, and the in-game events feed. For monster rewards, please be aware that data will be added over time, as contributors are able to fill out the necessary information.
The events feature is, basically, just a copy of the live and upcoming events feed available on Capcom's official site (here for console, and here for PC). It's updated automatically once per day, and provides all events as a JSON feed for easy consumption. Once an event updates, it will be removed from the list the next time the events are updated (midnight UTC every day), and new events will be added to the list at the same time. Click here to view the events currently available through the API.
See LartTyler/MHWDB-API#91 for a comprehensive list of backend changes.
Item.buyPrice and Item.sellPrice fields.Weapon.sharpness field.slug fields from all entities that had a slug. Please note that this was not a documented deprecation, but was a necessary change to support the user contribution system.This release has been a long time coming. Monster data is one of the most commonly requested features, and this update will finally bring support for them to the API. It's important to note that I say "support", as ailments, locations, and monsters will be the first endpoints to rely solely on user contributed data as opposed to the scraping system that the API has used in the past.
To begin with, contributions will only be allowed from a select few users that I'll be manually inviting to the contribution system. I'd eventually like to open contributions up to anyone that uses the API (similar to how a wiki allows edits from any user), but there's more work to be done before I feel comfortable opening things up that much. If you're interested in helping out with contributions of your own, feel free to reach out to me at [email protected].
For now, once this release goes live, I'll be adding data for ailments, locations, and monsters myself, to ensure that all the data is available. From there, we'll begin going back through the other endpoints and correcting inaccurate information and adding any missing information (like some of the new weapons added since the Kulve Taroth update).
See LartTyler/MHWDB-API#79 for a comprehensive list of backend changes.
durability field to weapons.buyPrice and sellPrice on items into a single field named value.Weapon.attributes.attack field.Weapon.attributes.deviation
Weapon.attributes.specialAmmo
Weapon.attributes.deviation
Weapon.attributes.coatings
Weapon.attributes.boostType
Weapon.attributes.phialType no longer contain the "phial" string, e.g. "Impact Phial" would become "impact" and "Dragon Phial 300" would become "dragon 300".Weapon.attributes.boostType no longer contain the "boost" string, e.g. "Sever Boost" would now be "sever".buyPrice and sellPrice are now deprecated, and will be removed on 2018-08-25. Use the value field instead.sharpness field is now deprecated, and will be removed on 2018-08-25. Use the durability field instead.p query parameter to all endpoints, which will allow projection against API results. For usage information, please see the docs.assets field to weapons.attributes.attack to attack.display and added attack.raw.Decoration.skill field.Weapon.attributes.element* fields.Weapon.attributes.sharpness* fields.attributes.attack is now deprecated, and will be removed on 2018-05-19. Use the attack object instead.Armor.skills or Weapon.elements) will now expose a length property that can be used when searching the API. For example, to search for any weapon that cannot be upgraded, you could use {"crafting.branches.length":0}. The length field will NOT be visible in the API output, and is only available to search by. Please see the docs for more information.