Mock sample for your project: HERE Network Positioning API v2

HERE Tracking is a cloud product designed to address location tracking problems for a wide range of Location IoT industry verticals.
HERE Tracking also includes end-user mobile and web applications that can be used to demonstrate the product.

API de Dados Abertos com dados processados pelo grupo de monitoramento de Queimadas do INPE.

Before using this API, we recommend you read our Authorization Guide for more information on how to generate an access token.
Please also be aware that our test environment is based on a subset of the production, if you are not returning any results try with big cities/airports like LON (London) or NYC (New-York).

API for the Water Linked Underwater GPS. For more details: http://www.waterlinked.com
Recommended approach for connecting to a Underwater GPS via the API is:
If "GET /api/" times out, the Underwater GPS is not running (on this IP address)
If "GET /api/" responds with 200 OK check that the api version returrned (eg "v1") is supported by the client (eg: also supports "v1").
If the api version returned does not match what the client supports: give an error to the user and recommend upgrading. (Eg: response is "v2" while client only supports "v1")
If "GET /api/" responds with 301 Moved permanently. "GET /api/v1/version" to check if the kit has a version earlier than 1.5.
"GET /api/v1/version" will always respond with 200 OK on Underwater GPS earlier than 1.5 release.
Configuration API is is not considered stable and will potentially be changed

Global marine weather data from multiple sources in one single API with hourly resolution. Get your API key by visiting the Storm Glass web site.

Routing consists of the following service:
Calculate Route
Calculates a route between an origin and a destination, passing through waypoints (if specified). Additional routing parameters like traffic, avoidance conditions, departure/arrival time etc. can be taken into account.
Calculate Reachable Range
Calculates a set of locations that can be reached from the origin point, subject to the available fuel or energy budget that is specified in the request.

Drive your app to success with Lyft's API

Worldwide forward and reverse geocoding

Download OpenAPI 3.0 Specification
Download Postman Collection
The Enode API is designed to make smart charging applications easy to develop. We provide an abstraction layer that reduces the complexity when extracting vehicle data and sending commands to vehicles from a variety of manufacturers.
The API has a RESTful architecture and utilizes OAuth2 authorization.
We are always available to handle any issues or just answer your questions. Feel free to reach out on [email protected]
Registration for API access
In order to use the API you will need a clientid and clientsecret. Please contact us if you are interested in using our API in production, and we will provide these credentials.
Authorization
Vehicle / hardware access via the Enode API is granted to your application by the User in a standard OAuth Authorization Code flow.
> The authorization scheme documented here is the recommended approach for most situations. However, it is also possible to user other OAuth flows, non-confidential clients, and temporary users. Please feel free to contact us if you have any questions about your use-case or the integration of your existing infrastructure.
Preparation: Configure your OAuth client
Because Enode API implements the OAuth 2.0 spec completely and without modifications, you can avoid rolling your own OAuth client implementation and instead use a well-supported and battle-tested implementation. This is strongly recommended. Information on available OAuth clients for many languages is available here
To configure your chosen OAuth client, you will need these details:
Your client_id
Your client_secret
Authorization URL: https://link.test.enode.io/oauth2/auth
Token URL: https://link.test.enode.io/oauth2/token

Convert an OSGB36 easting and northing (British National Grid) to WGS84 latitude and longitude.

API for OpenAQ LCS

Positioning API accepts requests with radio network measurements and replies with corresponding location estimate. For more details and examples, see Developer's Guide. Cellular measurements are given in terms defined in 3GPP and 3GGP2 specifications, see the corresponsing documentation at http://www.3gpp.org.
Breaking changes from v1:
JSON fields
altaccuracy, baselat, baselng, cellparams, pilotpower, pnoffset, powrx, rxlevel,
have been deprecated and replaced with
altAccuracy, baseLat, baseLng, cellParams, pilotPower, pnOffset, rss, rxLevel
respectively.
Dependent parameters combined as a subobject.
CDMA, GSM, WCDMA, TD-SCDMA and LTE local identification parameters for serving cell moved under localId property.
GSM neighbor global ID: lac and cid for neighbor cell moved under globalIdentity property.