![]() When testing your software against the API you should consider using instead of the live-api. The API is currently accessible using the following URL: Please note the Future deprecation of HTTP Basic Auth and OAuth 1.0a announcement: įor downloading data for purposes other than editing see Downloading data - you will likely use Overpass API (maybe with Overpass turbo), Planet.osm or extracts. Read requests do not require authorization (except user details). Requests to modify the database are authorized using HTTP Basic Authorization or OAuth. Any payload is in XML form, using the MIME type "text/xml" and UTF-8 character encoding, and may be compressed on the HTTP layer if the client indicates through the HTTP "Accept" header that it can handle compressed messages. The REST requests take the form of HTTP GET, PUT, POST, and DELETE messages. The API is the server component to which REST requests are addressed. For more information on RESTful APIs see wikipedia's Representational State Transfer page. This Editing API is based on the ideas of the RESTful API. 2.7.7 Search for notes: GET /api/0.6/notes/search.2.7.4 Create a new comment: POST /api/0.6/notes/#id/comment.2.7.3 Create a new note: POST /api/0.6/notes.2.7.1 Retrieving notes data by bounding box: GET /api/0.6/notes.2.6.4 Preferences of the logged-in user: GET /api/0.6/user/preferences.2.6.3 Details of the logged-in user: GET /api/0.6/user/details.2.6.2 Details of multiple users: GET /api/0.6/users?users=#id1,#id2.,#idn.2.6.1 Details of a user: GET /api/0.6/user/#id.2.5.5 Download Metadata: GET /api/0.6/gpx/#id/details.2.5.1 Get GPS Points: Get /api/0.6/trackpoints?bbox= left, bottom, right, top&page= pageNumber.2.4.11 Redaction: POST /api/0.6//#id/#version/redact?redaction=#redaction_id.2.4.8 Relations for element: GET /api/0.6//#id/relations.2.3.5 Unhide changeset comment: POST /api/0.6/changeset/comment/#comment_id/unhide.2.3.4 Hide changeset comment: POST /api/0.6/changeset/comment/#comment_id/hide.2.3.3 Unsubscribe: POST /api/0.6/changeset/#id/unsubscribe.2.3.2 Subscribe: POST /api/0.6/changeset/#id/subscribe.2.3.1 Comment: POST /api/0.6/changeset/#id/comment.2.2.9 Diff upload: POST /api/0.6/changeset/#id/upload.2.2.7 Expand Bounding Box: POST /api/0.6/changeset/#id/expand_bbox (deprecated, gone).2.2.6 Download: GET /api/0.6/changeset/#id/download.2.2.3 Read: GET /api/0.6/changeset/#id? include_discussion= true.2.2.2 Create: PUT /api/0.6/changeset/create.2.1.4 Retrieving permissions: GET /api/0.6/permissions.2.1.3 Retrieving map data by bounding box: GET /api/0.6/map. ![]() 2.1.2 Capabilities: GET /api/capabilities.2.1.1 Available API versions: GET /api/versions.1.11 Internal errors while generating a response.In April 2022, JSON support for some changeset endpoints was added JSON output added to changeset(s) endpoints.In March 2022, the permissions endpoint was added.In February 2022, limiting the maximum number of relation members in Limits on number of tags and relation members and Introduce relation member limit.In February 2021, the undocumented, unused and obsolete /changes endpoint was removed.In September 2020, JSON support for user details was added.In March 2020, JSON support for OSM element endpoints was added.In December 2019, the expand_bbox endpoint was removed.In July 2018 after numerous other smaller backwards compatible changes.In January 2016 after the addition of changeset discussions.In April 2013 after the addition of the Map Notes API.This page and the API has been extended and updated multiple times since April 2009: API v0.6 is the current version of the OSM Editing API originally deployed 17-21 April 2009.
0 Comments
Leave a Reply. |