Mock sample for your project: ICICI Prudential Life Insurance Company Ltd API

Integrate with "ICICI Prudential Life Insurance Company Ltd API" from in no time with Mockoon's ready to use mock sample

ICICI Prudential Life Insurance Company Ltd

Version: 3.0.0

Use this API in your project

Integrate third-party APIs faster by using "ICICI Prudential Life Insurance Company Ltd API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
It also helps reduce your dependency on third-party APIs: no more accounts to create, API keys to provision, accesses to configure, unplanned downtime, etc.


APIs provided by ICICI Prudential Life Insurance Company Ltd.

Other APIs by

Chitkara University
Degree Certificates of various courses issued by Chitkara University can be downloaded in citizen's DigiLocker account.

Gauhati University
GAUHATI UNIVERSITY ( has made available Registration Certificate in DigiLocker, which can be pulled by students into their accounts.

University Of Delhi
University of Delhi ( is issuing Degree certificates through DigiLocker. These can be pulled by students into their DigiLocker accounts. Currently data for 2017 is available.

AIIMS Mangalagiri
AIIMS Mangalagiri is one of the AIIMS healthcare institutes being established by the Ministry of Health & Family Welfare, Government of India.

CISCE ( is issuing marksheets, passing certificates, migration certificates through DigiLocker. These can be pulled by students into their DigiLocker accounts. Currently available - 2014-2019 (marksheets, passing certificates of ICSE & ISC and migration certificates of ISC).

Board of Higher Secondary Examinations, Directorate of General Education, Government of Kerala has made available HSE Certificate cum Marklist of MARCH 2020, which can be pulled by students into their Digilocker account

Acko General Insurance Limited
Insurance policies issued by Acko General Insurance ( can be fetched by the citizens in their Digilocker accounts.

eDistrict Chandigarh, Chandigarh
eDistrict Chandigarh( is the online service delivery portal for Chandigarh Administration. Certain documents issued by it (e.g. Senior Citizen Identity Card) can be pulled into citizens' DigiLocker accounts.

Civil Supplies Department, Kerala
Ration Cards issued by The Department of Civil Supplies functions under the Department of Food, Civil Supplies and Consumer Affairs of the Government of Kerala. ( are available for download on DigiLocker.

Mizoram Police, Mizoram
Identification cards, as issued by Mizoram Police to its personnels, can be downloaded by them in their DigiLocker accounts

Transport Department, Andhra Pradesh
Driving License (DL) and Vehicle Registration Certificate (RC) of the State, as available on Parivahan Sewa ( of Ministry of Road Transport and Highways, are available on DigiLocker. Citizens can pull these documents into their DigiLocker accounts.

National Insurance Company Ltd.
APIs provided by National Insurance Company Ltd..

Other APIs in the same category

Accountants General, Tripura
APIs provided by Accountants General, Tripura.

Karnataka Department of Transport, Karnataka
Driving License (DL) & Vehicle Registration Certificate (RC) as issued by Transport Department, Government of Karnataka ( can be pulled by citizens into their DigiLocker accounts.

DriveBC's Open511 API

This API is DriveBC's implementation of the Open511 specification. It provides information about known road events (traffic accidents, construction, etc.) in British Columbia, Canada. Please note that you may experience issues when submitting requests to the delivery or test environment if using this OpenAPI specification in other API console viewers.

Crediwatch's Covid APIs
An API collection for Covid 19 by Crediwatch

This REST-API enables you to query information about travel centers in Germany.

Times Newswire API

With the Times Newswire API, you can get links and metadata for Times articles and blog posts as soon as they are published on The Times Newswire API provides an up-to-the-minute stream of published items.

U.S. EPA Enforcement and Compliance History Online (ECHO) - Safe Drinking Water Act

Enforcement and Compliance History Online (ECHO) is a tool developed and maintained by EPA's Office of Enforcement and Compliance Assurance for public use. ECHO provides integrated compliance and enforcement information for over 1 million regulated facilities nationwide.
SDW Rest Services provides multiple service endpoints, each with specific capabilities, to search and retrieve data on public water systems regulated under the Safe Drinking Water Act (SDWA). The returned results reflect data drawn from EPA's Federal Safe Drinking Water Information System (SDWIS) database.
The getsystems, getqid, and get_download end points are meant to be used together.
The recommended use scenario for getsystems, getqid, and get_downoad is:
1) Use getsystems to validate passed query parameters, obtain summary statistics and to obtain a queryid (QID). QIDs are time sensitive and will be valid for approximately 30 minutes.
2) Use get_qid, with the returned QID, to paginate through arrays of water system results.
3) Use get_download, with the returned QID, to generate a Comma Separated Value (CSV) file of water system information that meets the QID query criteria.
Use the qcolumns parameter to customize your search results. Use the Metadata service endpoint for a list of available output objects, their Column Ids, and their definitions to help you build your customized output.
Additional ECHO Resources: Web Services, About ECHO's Data, Data Downloads

UK Parliament Search Service

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

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.

About CROssBAR & data
CROssBAR: Comprehensive Resource of Biomedical Relations with Deep Learning Applications and Knowledge Graph Representations
CROssBAR is a comprehensive system that integrates large-scale biomedical data from various resources e.g UniProt, ChEMBL, Drugbank, EFO, HPO, InterPro & PubChem and stores them in a new NoSQL database, enrich these data with deep learning based prediction of relations between numerous biomedical entities, rigorously analyse the enriched data to obtain biologically meaningful modules and display them to the user via easy to interpret, interactive and heterogeneous knowledge graphs.
CROssBAR platform exposes a set of 12 endpoints to query data stored in the CROssBAR database. These endpoints help the user to find data of interest using different parameters provided by the API endpoint.
For example, -> will provide protein information about accession 'A0A023GRW5' including its interactions, functions, cross-references, variations and more. -> will provide ChEMBL bio-interactions related information including targets and bio-activity measurements associated with molecule chembl id 'CHEMBL465983'
Knowledge graphs
Another use case of CROssBAR's API endpoints is in building knowledge graphs. These endpoints can be weaved together (output from one API endpoint fed as input to another API endpoint) programmatically to link nodes like protein, disease, drugs etc. as nodes of the graph. The endpoints are designed to be independent from each other which allows users the flexibility to drive biological networks from any facet e.g drug-centric, disease-centric, gene-centric etc. Our service for knowledge graph construction is available at
An example for the part of the background queries on the CROssBAR API during the construction of a knowledge graph,
(with the aim of keeping the example simple, we have only included the processes related to pathways, genes/proteins and drugs/compounds)
In this example, we would like to find bio-active compounds (with a pChEMBL value threshold of at least 6.0) & drugs targeting all proteins belonging to "WNT ligand biogenesis and trafficking" pathway (based on Reactome pathway annotations).
This can be achieved by using endpoints listed on this swagger documentation as illustrated in following steps-
Find bio-active compounds (with a pChEMBL value threshold of at least 6.0) & drugs targeting all proteins belonging to "WNT ligand biogenesis and trafficking" pathway (based on Reactome annotations)
This can be achieved by using endpoints listed on this swagger documentation as illustrated in following steps-
Get all proteins from “/proteins” API endpoint which have a reactome pathway name equal to "WNT ligand biogenesis and trafficking".
From the collection of uniprot protein accessions collected from step 1 above, we query “/targets” API endpoint to obtain the ‘targetchemblid’s of these proteins.
From the collection of targetchemblids collected from step 2 above, we query “/activities” API endpoint with pChEMBL value >=6, to obtain the ’moleculechemblid’s of the molecules that we need.
From the collection of uniprot protein accessions collected from step 1 above, we find out Drug names and ids from the “/drugs” API endpoint that targets our proteins.
From the collection of ’moleculechemblid’s obtained in step3, we query “/molecules” endpoint to get the compounds that are interacting with the genes/proteins belonging to the “WNT ligand biogenesis and trafficking” pathway.

You can use the CORE API to access the
resources harvested and enriched by CORE. If you encounter any problems with the API, please report them to us.
The API is organised by resource type. The resources are articles,
journals and repositories and are represented using JSON data format. Furthermore,
each resource has a list of methods. The API also provides two global methods for accessing all resources at once.
Response format
Response for each query contains two fields: status and data.
In case of an error status, the data field is empty. The data field contains a single object
in case the request is for a specific identifier (e.g. CORE ID, CORE repository ID, etc.), or
contains a list of objects, for example for search queries. In case of batch requests, the response
is an array of objects, each of which contains its own status and data fields.
For search queries the response contains an additional field totalHits, which is the
total number of items which match the search criteria.
Search query syntax
Complex search queries can be used in all of the API search methods.
The query can be a simple string or it can be built using terms and operators described in Elasticsearch
The usable field names are title, description, fullText,
authors, publisher,,,
doi, oai, identifiers (which is a list of article identifiers including OAI, URL, etc.),
and year. Some example queries:
title:psychology and AND year:2014
identifiers:"" OR identifiers:""
Retrieving the latest Articles
You can retrieve the harvested items since specific dates using the following queries:
repositoryDocument.metadataUpdated:>2017-03-01 AND repositoryDocument.metadataUpdated:
Sort order
For search queries, the results are ordered by relevance score. For batch
requests, the results are retrieved in the order of the requests.
The API methods allow different parameters to be passed. Additionally, there is an API key parameter which is common to all API methods. For all API methods
the API key can be provided either as a query parameter or in the request header. If the API key
is not provided, the API will return HTTP 401 error. You can register for an API key here.
API methods