Mock sample for your project: Twilio - Taskrouter API

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

This is the public Twilio REST API.

Introduction
Welcome to the SureVoIP RESTful hypermedia API (sometimes known as a VoIP REST API, Telecom REST API, SIP API, Hypermedia API or just VoIP API.)
The SureVoIP API is a way for you to automate your interaction with the SureVoIP platforms. With the API, you can create your own scripts, applications or mashups which can:
List calls
create customers
search numbers
provision numbers
send SMS texts
create outbound calls
schedule announcements
schedule call hangups with an announcement
subscribe to events/alerts
track calls
retrieve invoices
grab your SIP details
check your IP address
be 100% self-sufficient
and much more!

This is the public Twilio REST API.

Socio-demo API can be used to obtain time-aggregated data representing groups of people on the given location in the Czech Republic. Having a location, the API can return count of people belonging to age group or gender aggregated by hours. The socio-demo data is based on presence of mobile stations in O2 mobile network.

This is the public Twilio REST API.

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management described using OpenAPI.

The general-purpose API

This is the public Twilio REST API.

The Zoom API allows developers to access information from Zoom. You can use this API to build private services or public applications on the Zoom App Marketplace. To learn how to get your credentials and create private/public applications, read our Authorization Guide.
All endpoints are available via https and are located at api.zoom.us/v2/.
For instance you can list all users on an account via https://api.zoom.us/v2/users/.

Overview
The JSON REST API allows you to submit and receive BulkSMS messages. You can also get access to past messages and see your account profile.
The base URL to use for this service is https://api.bulksms.com/v1. The base URL cannot be used on its own; you must append a path that identifies an operation and you may have to specify some path parameters as well.
Click here to go to the main BulkSMS developer site.
In order to give you an idea on how the API can be used, some JSON snippets are provided below. Have a look at the messages section for more information.
Probably the most simple example
The insecure base URL http://api.bulksms.com/v1 is deprecated and may in future result in a 301 redirect response, or insecure requests may be rejected outright. Please use the secure (https) URI above.
HTTP Content Type
All API methods expect requests to supply a Content-Type header with the value application/json. All responses will have the Content-Type header set to application/json.
JSON Formatting
You are advised to format your JSON resources according to strict JSON format rules. While the API does attempt to parse strictly invalid JSON documents, doing so may lead to incorrect interpretation and unexpected results.
Good JSON libraries will produce valid JSON suitable for submission, but if you are manually generating the JSON text, be careful to follow the JSON format. This include correct escaping of control characters and double quoting of property names.
See the JSON specification for further information.
Date Formatting
Dates are formatted according to ISO-8601, such as 1970-01-01T10:00:00+01:00 for 1st January 1970, 10AM UTC+1.
See the Wikipedia ISO 8601 reference for further information.
Specifically, calendar dates are formatted with the 'extended' format YYYY-MM-DD. Basic format, week dates and ordinal dates are not supported. Times are also formatted in the 'extended' format hh:mm:ss. Hours, minutes and seconds are mandatory. Offset from UTC must be provided; this is to ensure that there is no misunderstanding regarding times provided to the API.
The format we look for is yyyy-MM-ddThh:mm:ss[Z|[+-]hh:mm]
Examples of valid date/times are2011-12-31T12:00:00Z 2011-12-31T12:00:00+02:00
Entity Format Modifications
It is expected that over time some changes will be made to the request and response formats of various methods available in the API.
Where possible, these will be implemented in a backwards compatible way.
To make this possible you are required to ignore unknown properties.
This enables the addition of information in response documents while maintaining compatibility with older clients.
Optional Request Entity Properties
There are many instances where requests can be made without having to specify every single property allowable in the request format.
Any such optional properties are noted as such in the documentation and their default value is noted.

Use this JSON API to build and test radio links for any radio, anywhere. Authenticate with your API2.0 key in the request header as key

Control and manages real Smartphone devices from browser and restful apis