VIAMICHELIN REST API
Access to a location resource providing its unique identifier (locid). This location can be an administrative area (country, city, etc), an adress with strret number or a POI (cityhall, etc)
Access to a place = a charged request (whetever the number of results)
|1.0||Added to REST API|
|locid||yes||string||Location unique identifier||N/A|
|authkey||yes||string||Authentication key. This could be a JS key, a token generated by the token function, or the client's id if request is signed (see signature parameter).||N/A|
|signature||no||string||Request signed with the HMAC-SHA1 method where client's password is the secret key. If request signed, authKey must be valued with client's id, and expires must also be valued. URL strings must be URL-encoded before signing.||empty|
|expires||no except if signature valued||date||Expiration GMT date in yyyy-MM-dd'T'HH:mm:ss.SSS`'Z format.||vide|
|callback||yes if json||string||Callback function name (applied only if output is json)||empty|
|charset||no||string||Response encoding charset||'ISO-8859-1'|
|ie||no||string||Request encoding charset||'ISO-8859-1'|
- returned locid have no meaning outside ViaMichelin services. They are not portable among other geodata suppliers. They should not be considered sustainable over time.
Please note that unexplained data fields are intended for internal ViaMichelin use only. These can change at any moment and should not be considered for use. Their existence highlights the fact that ViaMichelin uses the same services and technical infrastructure internally as its business clients.