Page Title

ArbJournal API Products

Arbjournal API has following products.

1. ArbJournal Trial API
2. ArbJournal API

ArbJournal Trial API

Trial – API

This trial API will return deal information for the year. Supported parameters are:

1. timezone = < timezone > (Example: Universal Time Coordinated)

Example: https://arbjournal.azure-api.net/basic/api/trail/Deals

ArbJournal API

Deals by ID

As the name indicates, it returns complete detail about a single deal based on the provided ID.
This API will return deal information for the deal id supplied through http request parameter. This API will return all the deals data. Supported parameters are:

1. Deal Id along with URL as suffix
2. timezone = < timezone > (Example : Universal Time Coordinated)

Example: https://arbjournal.azure-api.net/api/SearchByID/Deals/14193

Deals by Search Criteria

This endpoint returns a list of deals based on the provided search criteria. This endpoint has multiple configurable parameters.
Out of which the summary parameter can be leveraged to pull complete details about multiple deals.
By default, the summary parameter is set to yes. This would return only a summarized overview of the deal. But this parameter can be set to no, to return list of deals along with its full details of each deal, similar to the output of Deals By ID API.
The search criteria will be supplied as http query parameters. It is not necessary to supply all the search criteria parameters.

Example: https://arbjournal.azure-api.net/api/Search/Deals

Supported search criteria parameters:

Name	Type	Input	Description
summary	string	Default Yes
offset	int	Default 0
limit	int	Default 10
timezone	string	Universal Time Coordinated
keywords	string	comma separated strings
aquirer_name	string	company name
aquirer_ticker	string	company ticker
target_name	string	target name
target_ticker	string	target ticker
status	string	Any \| Active \| Inactive	“Any” which means return both active and inactive deals. “Active” which means return only active deals. “Inactive” which means return only inactive deals.
service	string	Any \| US \| EU \| Dual
type	string	Financial \| Strategic
value	string	< 200 Million \| 200 Million - 1 Billion \| > 1 Billion
failed_deals	string	failed_deals string Antitrust \| Other Regulatory \| Mutual Consent \| Financing \| SH Vote Failure \| MAC Breach \| Superior Bid
consideration_type	string	Cash & Stock Exchange \| Cash Merger \| Cash Tender \| Stock Exchange \| Stock Tender
consideration_terms	string	consideration terms
other_considerations	string	ADR/ADS \| No ADR/ADS, CVR \| No CVR
industry	string	industry
jurisdiction	string	jurisdiction
hsr_second_request	string	Yes \| No
enforcement_action	string	Yes \| No
financing_condition	string	Yes \| No
marketing_period	string	Yes \| No
go_shop_period	string	Yes \| No
announced_start_date	DateTime	yyyy-MM-dd	Fetches all deals that are announced on or after the provided date
announced_end_date	DateTime	yyyy-MM-dd	Fetches all deals that are announced on or before the provided date
announced_end_date	DateTime	yyyy-MM-dd	Fetches all deals that are announced on or before the provided date
completion_start_date	DateTime	yyyy-MM-dd	Fetches all deals that are completed on or after the provided date
completion_end_date	DateTime	yyyy-MM-dd	Fetches all deals that are completed on or before the provided date
journal_alert_start_date	DateTime	yyyy-MM-dd	Fetches all deals that are journal details created on or after the provided date
journal_alert_end_date	DateTime	yyyy-MM-dd	Fetches all deals that are journal details created on or before the provided date
deal_created_start_date	DateTime	DateTime	Fetches all deals that are created on or after the provided date
deal_created_end_date	DateTime	yyyy-MM-dd	Fetches all deals that are created on or before the provided date
deal_updated_start_date	DateTime	yyyy-MM-dd	Fetches all deals that are updated on or after the provided date
deal_updated_end_date	DateTime	yyyy-MM-dd	Fetches all deals that are updated on or before the provided date

FAQ:

1. API Rate limit – What is "Requests per minute?"

Currently our API gateway is rate limited with 10 requests every 5 minutes, so that would require a minimum delay of 30 seconds between requests.

2. API limit – What is "Requests per day?"

Arbjournal API Services have an overall limit of 1000 requests per day that needs to be considered, when consuming the APIs.
Arbjournal Trial API Services have a Total limit of 1000 requests. (Not per day but overall limit of 1000 requests).

3. What is “Out of call volume quota”?

This would mean the above mentioned daily limit has been reached (1000 requests / day). Once the limit has been reached, users would require to wait till next day to start sending requests again.

4. API to access data from a large number of historical deals - Is there an endpoint where we can specify a list of deals so that they are all returned in a single API request, instead of just one-deal-per-request?

Currently the only API that can return large number of deals is the Search API. We recommend using this endpoint with a limit of 500 records per request using the limit parameter.

5. How to pull the all the deals data from API?

For the initial data sync, we recommend calling the Search API with a limit of 500 and incrementing the offset starting from 0 until the number of deals returned is either 0 or less than 500. After the initial sync is complete, you can fetch incremental updates by using deal_updated_start_date with a value greater than your last successful sync timestamp.
The "summary" parameter dictates whether deal details should be summarized, returning only an overview. When set to "yes," the API provides a brief summary of the deals.
Alternatively, setting it to "no" results in the retrieval of detailed information for each deal in the list. The information returned for each deal resembles calling the Deal By ID API to fetch comprehensive details.