ReliefWeb API v1.1 released
Shuichi Odaka
Today we are announcing the release of version 1.1 of the ReliefWeb API. This release introduces POST support for more elaborate API queries that cannot fit within the browser URL limit of 1024 characters, and a new advanced parameter "facets". Facets allow broad analysis of ReliefWeb’s data, as well as the creation of faceted search UI's on top of the API. These mechanisms are both in use by various ReliefWeb internal projects, and based on what we have seen they will open up a wide range of new capabilities for API users as well.
You can check out the kind of insight the new facets functionality provides at http://trends.rwlabs.org, where it is used to power visualizations on what the ReliefWeb data reveals about the state of the world over the decades of its operations.
Next Steps
Now that we have the Facets capability out in the wild, the next focus for the API will be in closing the remaining gaps preventing it from being used as a first-rate search system. ReliefWeb.int is expected to have significant performance improvements over it's current Sphinx-based search via a custom API integration. Along the way, we expect to add several developer experience improvements to help navigate the many, powerful request parameters.
Want to Learn More?
If you are curious in learning more about the ReliefWeb API, you can check out the following talk:
Adam Ross from Phase2 at API Strategy & Practice Chicago on September 25th (http://apistrategyconference.com/)
The Advanced Request Parameters, including Facets (http://reliefweb.int/help/api/advanced)
The API (http://api.rwlabs.org)
Changelog
Enhancements & Additions
Added support for HTTP POST queries
Added new advanced parameter "facets"
Added support for new ReliefWeb Disaster Alerts (http://reliefweb.int/blogpost/stay-alert-reliefweb-s-enhanced-disaster-monitoring-system)
Bug Fixes
Fixed Date HTTP header format to match RFC 1123
- Fixed ability to specify limit=0 on list requests