Mock sample for your project: Erskine May API

Integrate with "Erskine May API" from parliament.uk in no time with Mockoon's ready to use mock sample

Erskine May API

parliament.uk

Version: v1


Use this API in your project

Integrate third-party APIs faster by using "Erskine May API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
Improve your integration tests by mocking third-party APIs and cover more edge cases: slow response time, random failures, etc.

Description

An API that allows querying of Erskine May data.

Other APIs by parliament.uk

Lords Votes API

An API that allows querying of Lords Votes data.

Annunciator content API

Get data from the annunciator system.

Commons Votes API

An API that allows querying of Commons Votes data.

Written Questions Service API

Data around written questions and answers, as well as written ministerial statements.

Bills API

API to get and search for information regarding Bills, their stages, associated amendments and publications.

Members API

An API which retrieves Members data.

Statutory Instruments API

parliament.uk
An API exposing details of the various types of Statutory Instruments laid before Parliament.

UK Parliament Search Service

Performs search on parliament.uk domain. Implements OpenSearch specification. Throttled at 10 requests per second per IP address.

Treaties API

parliament.uk
An API exposing details of the treaties laid before Parliament.

House of Commons Oral and Written Questions API

An API that allows querying all tabled oral and written questions, and motions for the House of Commons.

Other APIs in the same category

Bajaj Allianz General Insurance Company Ltd. (BAGIC)

apisetu.gov.in
Insurance policies such as health, car, two wheeler, property etc. issued by BAGIC are available to be pulled by citizens.

OPTIMADE API

optimade.local
The Open Databases Integration for Materials Design (OPTIMADE) consortium aims to make materials databases interoperational by developing a common REST API.
This specification is generated using optimade-python-tools v0.16.0.

Punjab State eGovernance Society, Punjab

apisetu.gov.in
eDistrict Punjab (http://edistrict.punjabgovt.gov.in) is the online service delivery portal for Punjab State Govt. Certain documents issued by it (e.g. Residence, SC/ST, OBC Certificates etc) can be pulled into citizens' DigiLocker accounts.
Introduction
This API returns information about all of the verses in Rig Veda. The results are JSON objects that contain the name of the god, poet, and meter of the verses in Rig Veda, the category of the god and the poet, and the mandal and sukta number.
The API uses the Swagger 2.0 specification.
Authentication
This is an open API.
Try it out
This sandbox can be used to get data for only one kind of resource, that is, to fetch the data for a category being sung to.
The remaining resources work a similar fashion. For details, see the reference documentation.

AIIMS Rishikesh

apisetu.gov.in
Degree certificates issued by AIIMS Rishikesh in year 2018 can be pulled by students into their DigiLocker accounts

Bajaj Allianz Life Insurance Company Ltd

apisetu.gov.in
Policy Documents issued by Bajaj Allianz Life Insurance Co.Ltd (https://www.bajajallianzlife.com) can be pulled in user's DigiLocker account

eDistrict Himachal Pradesh, Himachal Pradesh

apisetu.gov.in
eDistrict Himachal (http://edistrict.hp.gov.in/) is the online service delivery portal for Himachal Pradesh State Govt. Certain documents issued by it (e.g. Birth, Income, Caste, Agriculturist, Bonafide Himachali Certificates etc) can be pulled into citizens' DigiLocker accounts.

House of Commons Oral and Written Questions API

An API that allows querying all tabled oral and written questions, and motions for the House of Commons.

Jharkhand State Board (Jharkhand Academic Council), Jharkhand

apisetu.gov.in
Jharkhand Academic Council (JAC) is issuing marksheets & passing certificates through DigiLocker. These can be pulled by students into their DigiLocker accounts. Currently available - 2009-2017 [Class XII], 2009-2017 [Class X].

Commons Votes API

An API that allows querying of Commons Votes data.

Semantic API

The Semantic API complements the Articles API. With the Semantic API, you get access to the long list of people, places, organizations and other locations, entities and descriptors that make up the controlled vocabulary used as metadata by The New York Times (sometimes referred to as Times Tags and used for Times Topics pages).
The Semantic API uses concepts which are, by definition, terms in The New York Times controlled vocabulary. Like the way facets are used in the Articles API, concepts are a good way to uncover articles of interest in The New York Times archive, and at the same time, limit the scope and number of those articles. The Semantic API maps to external semantic data resources, in a fashion consistent with the idea of linked data. The Semantic API also provides combination and relationship information to other, similar concepts in The New York Times controlled vocabulary.

TheTVDB API v3

thetvdb.com
API v3 targets v2 functionality with a few minor additions. The API is accessible via https://api.thetvdb.com and provides the following REST endpoints in JSON format.
How to use this API documentation
You may browse the API routes without authentication, but if you wish to send requests to the API and see response data, then you must authenticate.
Obtain a JWT token by POSTing to the /login route in the Authentication section with your API key and credentials.
Paste the JWT token from the response into the "JWT Token" field at the top of the page and click the 'Add Token' button.
You will now be able to use the remaining routes to send requests to the API and get a response.
Language Selection
Language selection is done via the Accept-Language header. At the moment, you may only pass one language abbreviation in the header at a time. Valid language abbreviations can be found at the /languages route..
Authentication
Authentication to use the API is similar to the How-to section above. Users must POST to the /login route with their API key and credentials in the following format in order to obtain a JWT token.
{"apikey":"APIKEY","username":"USERNAME","userkey":"USERKEY"}
Note that the username and key are ONLY required for the /user routes. The user's key is labled Account Identifier in the account section of the main site.
The token is then used in all subsequent requests by providing it in the Authorization header. The header will look like: Authorization: Bearer . Currently, the token expires after 24 hours. You can GET the /refresh_token route to extend that expiration date.
Versioning
You may request a different version of the API by including an Accept header in your request with the following format: Accept:application/vnd.thetvdb.v$VERSION. This documentation automatically uses the version seen at the top and bottom of the page.