Mock sample for your project: PAC Control REST API

Integrate with "PAC Control REST API" from opto22.com in no time with Mockoon's ready to use mock sample

PAC Control REST API

opto22.com

Version: R1.0a


Use this API in your project

Speed up your application development by using "PAC Control REST API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and allow you to stop relying on an external API to get the job done. No more API keys to provision, accesses to configure or unplanned downtime, just work.
Enhance your development infrastructure by mocking third party APIs during integrating testing.

Description

Revised: 6/15/2018
Overview
This API provides secure access to a SNAP-PAC-R or -S series controller's variable and I/O tags. Confidentiality for API transactions is provided by HTTPS. Authentication uses HTTP Basic Authentication with an API key. An API key ID is submitted in the Basic Authentication userid field and API key value in the password field.
For more information visit: developer.opto22.com
Examples
Read an array of all the integer32 variables defined in the PAC's strategy.
For example, on your SNAP-PAC-R or -S series controller at IP address 1.2.3.4, you would use the URL:
Note on packet sizes:
When doing POSTs or GETs, the JSON payload in the body should not exceed 3k (3072 bytes).

Other APIs by opto22.com

groov View Public API

Revised: 2019-11-21
Overview
groov View Public API revision 1.

Other APIs in the same category

KeyServ

keyserv.solutions
KeyServ API

groov View Public API

Revised: 2019-11-21
Overview
groov View Public API revision 1.

IoE² IoT API - to create end-user applications

Who Hosts This API

Discover the hosting provider for any web site

Meraki Dashboard API

meraki.com
The Cisco Meraki Dashboard API is a modern REST API based on the OpenAPI specification.
> Date: 04 August, 2021
>
> What's New
API Documentation
Community Support
Meraki Homepage

Quick start - Telematics SDK

telematicssdk.com
Introduction
We have prepared a set of APIs for quick start to integrate telematics SDK that powers mobile telematics inside 3rd party mobile applications.
CONTACT US
SANDBOX
DEV.PORTAL
DEMO APP
Overview
Datamotion provides telematics infrastructure for mobile applications.
Telematics SDK turns any smartphone into telematics data gathering device to collect Location, driving and behavior data. API services unlocks power of your mobile application
There are 3 groups of methods:
1 - user management
2 - statistics for mobile app
3 - statistics for back-end(s)
in certain cases you will need SNS or any other notification services. read more here
Possible architecture
There are three common schemes that are used by our clients. These schemes can be combined
Collect, Process, Store (required: 1&2)
Collect, Process (required: 1& sns)
Collect (required 1&sns)
Collect, Process, Store
Collect, Process, Store
Collect, Process
Collect, Process
Collect
Collect
Telematic sdk
Common use-cases:
Safe and efficient driving
Usage-based insurance
Safe driving assessment
Driver assessment
Trip log
Geo-analysis
Accident monitoring
Driving engagements
Location based services
Realtime Tracking
and beyond
How to start
Register a SANDBOX ACCOUNT
Get CREDENTIALS
Follow the guide from DEVELOPER POERTAL
Authentication
To create a user on datamotion platform, you require to use InstanceID and InstanceKEY. You can get it in Datahub -> management -> user-service credentials
Once you create a user, you will get Device token, JWT token and refresh token. then, you will use it for APIs

M-Bus HTTPD API

mbus.local

PAC Control REST API

Revised: 6/15/2018
Overview
This API provides secure access to a SNAP-PAC-R or -S series controller's variable and I/O tags. Confidentiality for API transactions is provided by HTTPS. Authentication uses HTTP Basic Authentication with an API key. An API key ID is submitted in the Basic Authentication userid field and API key value in the password field.
For more information visit: developer.opto22.com
Examples
Read an array of all the integer32 variables defined in the PAC's strategy.
For example, on your SNAP-PAC-R or -S series controller at IP address 1.2.3.4, you would use the URL:
Note on packet sizes:
When doing POSTs or GETs, the JSON payload in the body should not exceed 3k (3072 bytes).

Adafruit IO REST API

adafruit.com
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 and a simple Internet of Things capable device like the Feather Huzzah.
This API documentation is hosted on GitHub Pages and is available at https://github.com/adafruit/io-api. For questions or comments visit the Adafruit IO Forums or the adafruit-io channel on the Adafruit Discord server.
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 "iousername" and the key "iokey_12345" could look like this:
$ curl -H "X-AIO-Key: iokey12345" https://io.adafruit.com/api/v2/io_username/feeds
Or like this:
$ curl "https://io.adafruit.com/api/v2/iousername/feeds?X-AIO-Key=iokey_12345
Using the node.js request library, IO HTTP requests are as easy as:
Client Libraries
We have client libraries to help you get started with your project: Python, Ruby, Arduino C++, Javascript, and Go are available. They're all open source, so if they don't already do what you want, you can fork and add any feature you'd like.

ClearBlade API

clearblade.com
A friendly little API to help you interact with the ClearBlade platform.

Brain Web API

This document describes the Intellifi Brain
Web API specification using the OpenAPI specification.
The Brain Web API is a RESTful API that allows you to interact with the
Intellifi devices 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.
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
See also
About Intellifi and what we do: intellifi.nl
Technical and background information: intellifi.zendesk.com

MIMIC REST API

This is the API for MIMIC client to connect to MIMIC daemon.