OpenStreetMap has an Editing API for fetching and saving raw geodata from/to the OpenStreetMap database — this is the entry page for the documentation. If you just want to embed a map into a webpage, you don't want this API. Use a Web Map Framework instead. Alternatively, consider the Overpass API which provides read-only API access.
REST specifications for the editing API
- API v0.6 - (currently used, as of April 2009)
API v0.5(no longer used as of April 2009); though this document may still be of use API v0.4(no longer used as of October 2007) API v0.3(no longer used as of May 2007)
We are labeling wiki pagesif they describe something which does not, or may not work with the 0.6 API version.
Implementations and scripting
The current full serverside implementation is the Rails port.
For other uses, see Develop/Frameworks.
The editing API is provided in order to edit the map data, not for read-only purposes or projects. Clients may be blocked without notice if they are affecting the service level for others or causing data corruption. See our API usage policy.
Imports and automated edits should only be carried out by those with experience and understanding of the way the OpenStreetMap community creates maps, and only with careful planning and consultation with the local community.|
See Import/Guidelines and Automated Edits code of conduct for more information. Imports/automated edits which do not follow these guidelines might be reverted!
Summaries of editing API changes
- API changes between v0.5 and v0.6
- API changes between v0.4 and v0.5
- API changes between v0.3 and v0.4
- API v0.7 - Brainstorming for the next version of the OSM API
- JSON to CSV Converter - A 3rd party tool for converting JSON responses from the OpenStreetMap API to CSV (which can be opened in a spreadsheet).
- JSON to CSV Converter - Alternative 3rd party tool for converting JSON responses from the OpenStreetMap API to CSV.