Mock sample for your project: Storm Glass Marine Weather API

Worldwide forward and reverse geocoding

Enable people to store spots on public and private maps

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

The API ecotaco allows you to connect, create an account,
manage your credit cards and order rides.
Authentication
Ecotaco API use a system of application key and authentification token.
Application key :
The application key is generated by Ecota.co and unique to an application.
Before accessing EcoTa.co APIs, you need to register your application. Please supply the following information to [email protected]:
Application name
Company (if appropriate)
Contact name, phone and address
Contact email
Is this a web application, a desktop application, or an application running on a device?
Short description of your application
It must be passed on request : "accounts -> login", "accounts -> facebook login" and "accounts -> register" .
Authentification token :
The authentification token is retrieved at login or register of an user.
It must be passed in request for authenticate action in Authorization HTTP header.
Example :
Authorization: Token token=e55887022c1aca4c86abcc49e85ceb8a0c855d2af4d9fac75c08040a583dcde4
Language
On some of our resources, we filter the content displayed based on the Accept-Language header.
If the language is not defined or if we don't use the language defined in this header, we automatically use French as the default language.
EcoTa.co currently support two languages: English, French. ("en" and "fr")
Encoding
All requests and answers on EcoTa.co are in UTF-8.

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).

Open Source GPS Tracking Platform

API to view feed information and download feeds from TransitFeeds.com

Background
This RESTful API provides information about physical VA facilities. Information available includes
geographic location, address, phone, hours of operation, and available services.
VA operates several different types of facilities, the types represented in this API include:
Health Facilities (vha)
Benefits Facilities (vba)
Cemeteries (nca)
Vet Centers (vc)
To read an FAQ on how wait times are calculated, click the "For more information" link on this page.
Getting Started
Base URLs
The base URLs for the VA Facilities API in the various environments are:
Sandbox: https://sandbox-api.va.gov/services/va_facilities/v0
Production: https://api.va.gov/services/va_facilities/v0
Authorization
API requests are authorized through a symmetric API token, provided in an HTTP header with name apikey.
Response Formats
Clients may request several response formats by setting the Accept header.
application/json - The default JSON response format complies with JSON API. This media type is not available for bulk requests using the /facilities/all endpoint. It will return 406 Not Acceptable.
application/geo+json - GeoJSON-compliant format, representing each facility as a feature with a point geometry.
application/vnd.geo+json - Deprecated. Prefer application/geo+json.
text/csv - Available for the bulk download operation only. Some structured fields are omitted from the CSV response.
Response Elements
Some data elements within the response are only present for facilities of a given type:
The patient satisfaction scores contained in the satisfaction element are only applicable
to VA health facilities.
The patient wait time values contained in the wait_times element are only applicable to
VA health facilities.
The list of available services in the services element is only applicable to VA health and
benefits facilities.
The operational hours special instructions contained in the operationalhoursspecial_instructions element is only applicable to VA health and Vet Center facilities.
Facility ID Formats and Constraints
A facility ID has the format prefix_stationNumber. The prefix is one of nca, vc, vba, or vha. Cemeteries may be national (VA) or non-national; non-national cemeteries have the station number prefixed with an s. There are no other constraints on the format. Examples:
Health: vha_402GA
Benefits: vba_539GB
National cemetery: nca_063
Non-national cemetery: nca_s1082
Vet center: vc_0872MVC
Mobile Facilities
The mobile health facilities move regularly within a region. If a facility comes back from this API with "mobile": "true", the latitude/longitude and address could be inaccurate. To get the exact current location, please call the number listed.
Deprecations
activestatus field is deprecated and replaced with operatingstatus.
application/vnd.geo+json media type is deprecated and replaced by application/geo+json
Reference
Raw VA Facilities Open API Spec
GeoJSON Format
JSON API Format

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

API for OpenAQ LCS