Open documentation ↗Overview
The subscription management service for rapid product development
KeyServ is an iot API from keyserv.solutions. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 24 endpoints.
At a glance
- Authentication
- No auth
- HTTPS
- Yes
- CORS
- Unknown
- Category
- IoT
- Base URL
https://keyserv.solutions- Version
- 1.4.5
- Endpoints
- 24
- OpenAPI
- Specification ↗
- Spec updated
- 2021-01-26
Make a first request
Replace the placeholders; the documentation says exactly where credentials go.
curl -X GET "https://keyserv.solutions/v1/KeysApi/Current/SERIAL" \
-H "Accept: application/json"const response = await fetch("https://keyserv.solutions/v1/KeysApi/Current/SERIAL", {
method: "GET",
headers: {
"Accept": "application/json",
},
});
const data = await response.json();
console.log(data);import requests
response = requests.request(
"GET",
"https://keyserv.solutions/v1/KeysApi/Current/SERIAL",
headers={
"Accept": "application/json",
},
timeout=30,
)
print(response.json())Endpoints
| Method | Path | What it does |
|---|---|---|
| GET | /v1/KeysApi/Current/{serial} | KeysApi_Current |
| GET | /v1/KeysApi/Custom/{serial} | KeysApi_Custom |
| GET | /v1/KeysApi/Expiry/{serial} | KeysApi_Expiry |
| GET | /v1/KeysApi/Find/{serial} | KeysApi_Find |
| POST | /v1/ProductsApi | ProductsApi_PatchProduct2 |
| PATCH | /v1/ProductsApi | ProductsApi_PatchProduct |
| POST | /v1/ProductsApi/Count | ProductsApi_Count |
| POST | /v1/ProductsApi/Find | ProductsApi_Find |
| POST | /v1/ProductsApi/List | ProductsApi_List |
| POST | /v1/ProductsApi/Save | ProductsApi_Save |
| POST | /v1/ProductsApi/{serial} | ProductsApi_DeleteProduct2 |
| DELETE | /v1/ProductsApi/{serial} | ProductsApi_DeleteProduct |
| POST | /v1/SubscriptionsApi | SubscriptionsApi_PutSubscription2 |
| PUT | /v1/SubscriptionsApi | SubscriptionsApi_PutSubscription |
| POST | /v1/SubscriptionsApi/Count | SubscriptionsApi_Count |
| POST | /v1/SubscriptionsApi/Disable | SubscriptionsApi_Disable2 |
| PATCH | /v1/SubscriptionsApi/Disable | SubscriptionsApi_Disable |
| POST | /v1/SubscriptionsApi/Enable | SubscriptionsApi_Enable2 |
| PATCH | /v1/SubscriptionsApi/Enable | SubscriptionsApi_Enable |
| POST | /v1/SubscriptionsApi/Find | SubscriptionsApi_Find |
| POST | /v1/SubscriptionsApi/List | SubscriptionsApi_List |
| POST | /v1/SubscriptionsApi/Save | SubscriptionsApi_Save |
| POST | /v1/SubscriptionsApi/{serial} | SubscriptionsApi_DeleteSubscription2 |
| DELETE | /v1/SubscriptionsApi/{serial} | SubscriptionsApi_DeleteSubscription |
Questions
Does the KeyServ API need an API key?
No. The KeyServ API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.
Does the KeyServ API support HTTPS?
Yes, the KeyServ API is served over HTTPS.
How many endpoints does the KeyServ API have?
Its OpenAPI description lists 24 endpoints in version 1.4.5. All of them are shown on this page.
What are alternatives to the KeyServ API?
Other IoT APIs include Brain Web API, Adafruit IO REST API, Netatmo, Influx OSS API Service, ClearBlade API.
Similar iot APIs
Compare alternatives →Brain Web API
IoTThis document describes the [Intellifi Brain](https://intellifi.zendesk.com/hc/en-us/categories/360000685454) Web API specification using the [OpenAPI specification](https://github.com/OAI/OpenAPI-Specification). The Brain Web API is a RESTful API that allows you to interact with the [Intellifi devices](https://intellifi.zendesk.com/hc/en-us/categories/360000685434) and services in a powerful and simple way. Our end-to-end solution allows you to localize your items/assets based on technologies such as RFID and Bluetooth. # Try it out! The API can be tried out and tested using the ['api-doc/tryitout' endpoint on this site](./tryitout/). This UI allows anyone to visualize and interact with the API’s resources without having any of the implementation logic in place. It’s automatically generated from this Specification, with the visual documentation making it easy for back end implementation and client side consumption. # Authentication Applications are required to provide some form of authentication to the API for every secured endpoint. The Brain offers two forms of authentication. - API key (Via an HTTP request header or URL parameter) - Session cookie <!-- ReDoc-Inject: <security-definitions> --> # See also - About Intellifi and what we do: [intellifi.nl](https://intellifi.nl) - Technical and background information: [intellifi.zendesk.com](https://intellifi.zendesk.com)
Adafruit IO REST API
IoT### The Internet of Things for Everyone The Adafruit IO HTTP API provides access to your Adafruit IO data from any programming language or hardware environment that can speak HTTP. The easiest way to get started is with [an Adafruit IO learn guide](https://learn.adafruit.com/series/adafruit-io-basics) and [a simple Internet of Things capable device like the Feather Huzzah](https://www.adafruit.com/product/2821). This API documentation is hosted on GitHub Pages and is available at [https://github.com/adafruit/io-api](https://github.com/adafruit/io-api). For questions or comments visit the [Adafruit IO Forums](https://forums.adafruit.com/viewforum.php?f=56) or the [adafruit-io channel on the Adafruit Discord server](https://discord.gg/adafruit). #### Authentication Authentication for every API request happens through the `X-AIO-Key` header or query parameter and your IO API key. A simple cURL request to get all available feeds for a user with the username "io_username" and the key "io_key_12345" could look like this: $ curl -H "X-AIO-Key: io_key_12345" https://io.adafruit.com/api/v2/io_username/feeds Or like this: $ curl "https://io.adafruit.com/api/v2/io_username/feeds?X-AIO-Key=io_key_12345 Using the node.js [request](https://github.com/request/request) library, IO HTTP requests are as easy as: ```js var request = require('request'); var options = { url: 'https://io.adafruit.com/api/v2/io_username/feeds', headers: { 'X-AIO-Key': 'io_key_12345', 'Content-Type': 'application/json' } }; function callback(error, response, body) { if (!error && response.statusCode == 200) { var feeds = JSON.parse(body); console.log(feeds.length + " FEEDS AVAILABLE"); feeds.forEach(function (feed) { console.log(feed.name, feed.key); }) } } request(options, callback); ``` Using the ESP8266 Arduino HTTPClient library, an HTTPS GET request would look like this (replacing `---` with your own values in the appropriate locations): ```arduino /// based on /// https://github.com/esp8266/Arduino/blob/master/libraries/ESP8266HTTPClient/examples/Authorization/Authorization.ino #include <Arduino.h> #include <ESP8266WiFi.h> #include <ESP8266WiFiMulti.h> #include <ESP8266HTTPClient.h> ESP8266WiFiMulti WiFiMulti; const char* ssid = "---"; const char* password = "---"; const char* host = "io.adafruit.com"; const char* io_key = "---"; const char* path_with_username = "/api/v2/---/dashboards"; // Use web browser to view and copy // SHA1 fingerprint of the certificate const char* fingerprint = "77 00 54 2D DA E7 D8 03 27 31 23 99 EB 27 DB CB A5 4C 57 18"; void setup() { Serial.begin(115200); for(uint8_t t = 4; t > 0; t--) { Serial.printf("[SETUP] WAIT %d...\n", t); Serial.flush(); delay(1000); } WiFi.mode(WIFI_STA); WiFiMulti.addAP(ssid, password); // wait for WiFi connection while(WiFiMulti.run() != WL_CONNECTED) { Serial.print('.'); delay(1000); } Serial.println("[WIFI] connected!"); HTTPClient http; // start request with URL and TLS cert fingerprint for verification http.begin("https://" + String(host) + String(path_with_username), fingerprint); // IO API authentication http.addHeader("X-AIO-Key", io_key); // start connection and send HTTP header int httpCode = http.GET(); // httpCode will be negative on error if(httpCode > 0) { // HTTP header has been send and Server response header has been handled Serial.printf("[HTTP] GET response: %d\n", httpCode); // HTTP 200 OK if(httpCode == HTTP_CODE_OK) { String payload = http.getString(); Serial.println(payload); } http.end(); } } void loop() {} ``` #### Client Libraries We have client libraries to help you get started with your project: [Python](https://github.com/adafruit/io-client-python), [Ruby](https://github.com/adafruit/io-client-ruby), [Arduino C++](https://github.com/adafruit/Adafruit_IO_Arduino), [Javascript](https://github.com/adafruit/adafruit-io-node), and [Go](https://github.com/adafruit/io-client-go) are available. They're all open source, so if they don't already do what you want, you can fork and add any
Netatmo
IoT<h3>Welcome to the Netatmo swagger on-line documentation !</h3> This site is a complement to the official <a href="https://dev.netatmo.com/">Netatmo developper documentation</a> using swagger to bring interactivity and easy testing of requests with the "try it" button (authenticate with the authorization code OAuth2 flow by clicking the authenticate button in the methods). You can find the source code for this site can be found in the project <a href="https://github.com/cbornet/netatmo-swagger-ui">netatmo-swagger-ui</a>. You can also use the online <a href="./swagger.json">swagger declaration</a> file to generate code or static documentation (see <a href="https://github.com/cbornet/netatmo-swagger-api">netatmo-swagger-api</a>).
Influx OSS API Service
IoT# Authentication <!-- ReDoc-Inject: <security-definitions> -->
ClearBlade API
IoTA friendly little API to help you interact with the ClearBlade platform.
Hardware Sentry TrueSight Presentation Server REST API
IoTHardware Sentry TrueSight Presentation Server REST API
Listed from APIs.guru (CC0).