Benzinga · Mergers and acquisitions
benzinga/calendar/mergers-acquisitionsGet market and financial data with Benzinga · Mergers and acquisitions from Alexandria through one Spiral API key. Use for who is buying whom, at what price, and whether the deal is pending or closed. For the coverage and commentary around a deal use news/search. It runs in the background and returns structured JSON. Pay as you go, with no subscription.
Pricing
$0.026189 per call.
Limits
- Runs
- In the background
- Returns
- json
- Longest queue wait
- 1 hour
- Run deadline
- 5 minutes
- Longest run, end to end
- 225 minutes
- Largest inline input
- 1 MB
- Largest input file
- 2 GB
- Largest output
- 5 GB
Input
| Field | Kind | Default | Description |
|---|---|---|---|
page | number … to 100000 | 0 | Zero-based page offset, capped at 100000. Prefer narrowing by date over paging deep. |
pagesize | number … to 1000 | — | Number of records to return, limit 1000. |
parameters[date] | text | — | A single date, YYYY-MM-DD, as shorthand when date_from and date_to would be the same. Leave unset to get the latest deals. |
parameters[date_to] | text | — | Latest date, YYYY-MM-DD, interpreted against date_sort. |
parameters[tickers] | text | — | Comma-separated ticker symbols, maximum 50. Set this when the caller asks whether a named company is acquiring or being acquired. |
parameters[updated] | number | — | Unix timestamp in UTC; returns only records updated at or after it. Set this when polling for changes since a previous call. |
parameters[date_from] | text | — | Earliest date, YYYY-MM-DD, interpreted against date_sort. |
parameters[date_sort] | one of expected, completed, announced | — | Which deal date to sort on. Use announced for a chronology of new deals, expected for pending closes, or completed for deals that have closed. |
parameters[importance] | one of 0, 1, 2, 3, 4, 5 | — | Minimum importance level, matched as greater than or equal to the value given. Raise it when the caller only wants large or notable deals. |
Same request in code
curl https://api.spiral.ai/v1/runs \
-H "Authorization: Bearer $SPIRAL_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"provider": "alexandria",
"model": "benzinga/calendar/mergers-acquisitions",
"input": {
"page": 0
}
}'Frequently asked questions
How much does Benzinga · Mergers and acquisitions cost?
$0.026189 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.
How do I use Benzinga · Mergers and acquisitions through an API?
Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "benzinga/calendar/mergers-acquisitions"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.
Do I need an account with Alexandria to use Benzinga · Mergers and acquisitions?
No. Spiral runs it on its own Alexandria account and charges your Spiral balance.
Can my AI agent use Benzinga · Mergers and acquisitions?
Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.