# Marketstack integrations: end-of-day prices

> Marketstack is a stock market data API from APILayer that returns end-of-day, intraday and historical prices for tens of thousands of tickers worldwide.

**Canonical page:** https://tray.ai/connectors/marketstack-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Marketstack is a stock market data API from APILayer that returns end-of-day, intraday and historical prices for tens of thousands of tickers worldwide. Tray.ai connects to Marketstack through the HTTP Connector, so your workflows can call the Marketstack API alongside the rest of your stack.

## Use cases

### End-of-day prices

Read end-of-day prices in Marketstack from any Tray.ai workflow. The Marketstack API covers calls such as get end-of-day prices and get latest end-of-day prices.

- Get end-of-day prices
- Get latest end-of-day prices

### Intraday prices

Read intraday prices in Marketstack from any Tray.ai workflow. The Marketstack API covers calls such as get intraday prices and get latest intraday prices.

- Get intraday prices
- Get latest intraday prices

### Tickers

Read tickers in Marketstack from any Tray.ai workflow. The Marketstack API covers calls such as list tickers and get a ticker.

- List tickers
- Get a ticker
- Get ticker dividends

### Exchanges

Read exchanges in Marketstack from any Tray.ai workflow. The Marketstack API covers calls such as list exchanges and get exchange end-of-day prices.

- List exchanges
- Get exchange end-of-day prices
- Get exchange intraday prices

### Corporate actions

Read corporate actions in Marketstack from any Tray.ai workflow. The Marketstack API covers calls such as list stock splits and list dividends.

- List stock splits
- List dividends

## Challenges Tray.ai solves

### Keeping Marketstack credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Marketstack credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Marketstack API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Marketstack API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Marketstack?

Yes. Tray.ai connects to Marketstack through the HTTP Connector, which calls the Marketstack API directly. Any call the Marketstack API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Marketstack?

The Marketstack API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Marketstack connector?

Marketstack runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Marketstack connector from the Marketstack API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
