canonical: https://jentic.com/apis/trading212.com/trading212

# Trading212 Public API

trading212.com/main version v0. The API exposes 25 endpoints secured with apiKey authentication.

## For AI agents

Programmatically fetch account cash, fetch account metadata. Covers 25 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Fetch account cash
- Historical order data
- Exchange List
- Instrument List
- Place Limit order

## Use cases

### Developer Tools Operations

Use the Trading212 Public API to perform developer tools operations programmatically. The API provides 25 endpoints covering core functionality including fetch account cash, fetch account metadata, historical order data.

Example prompt: Call GET `/api/v0/equity/account/cash` to fetch account cash

### Automated Instruments Metadata Management

Automate instruments metadata operations by combining multiple Trading212 Public API endpoints. Agents can fetch account metadata and then historical order data in a single workflow.

Example prompt: Call GET `/api/v0/equity/account/info` to fetch account metadata, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Trading212 Public API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'fetch account cash', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v0/equity/account/cash` | Fetch account cash |
| GET | `/api/v0/equity/account/info` | Fetch account metadata |
| GET | `/api/v0/equity/history/orders` | Historical order data |
| GET | `/api/v0/equity/metadata/exchanges` | Exchange List |
| GET | `/api/v0/equity/metadata/instruments` | Instrument List |
| GET | `/api/v0/equity/orders` | Fetch all |
| POST | `/api/v0/equity/orders/limit` | Place Limit order |
| POST | `/api/v0/equity/orders/market` | Place Market order |

## Key resources

- **Instruments Metadata** — Tradeable instruments metadata
- **Pies** — Endpoints for managing pies
- **Equity Orders** — Order information and dispatcher
- **Account Data** — Relevant information about your account
- **Personal Portfolio** — State of your trading portfolio

## Why Jentic

- **Setup:** Wiring the Trading212 Public API by hand means setting up its API key in the Authorization header, choosing the demo or live host, and handling errors yourself. Through Jentic you install once, import the Trading212 Public API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Trading212 order target travels in the request body rather than the URL path, so scope the agent to the operations it needs, such as reading account cash and listing orders, and leave out order placement like a market or limit order unless the workflow requires it. Every operation you allow is one you have chosen.
- **Credential handling:** Your Trading212 API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'fetch account cash' or 'list open orders', and Jentic returns the matching Trading212 Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Trading212 Public API use?

The Trading212 Public API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I fetch account cash with the Trading212 Public API?

Yes. Use the GET `/api/v0/equity/account/cash` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Trading212 Public API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I fetch account cash through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fetch account cash'. Jentic returns the matching Trading212 Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Trading212 Public API have?

The Trading212 Public API exposes 25 endpoints covering instruments metadata, pies, equity orders operations.

### Can I limit what my agent is allowed to do with the Trading212 Public API?

Yes. Because you run Jentic One yourself, your own rules decide which Trading212 operations and credentials the agent can use. You can allow read-only calls such as GET `/api/v0/equity/account/cash`, listing orders, and pulling instrument or exchange metadata, while withholding order placement like the limit and market order endpoints. Since the order target travels in the request body rather than the URL, you scope at the operation level, so every action the agent can take is one you have explicitly permitted.