Trading212 Public API

Name: Trading212 Public API API
Brand: Trading212 Public API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey25 EndpointsREST

For Agents

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

Connect the Trading212 Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Trading212 Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Trading212 Public API API.

Fetch account cash

Historical order data

Exchange List

Instrument List

Place Limit order

GET STARTED

Start building with Trading212 Public API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Trading212 Public API API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

25 endpoints — trading212.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Trading212 Public API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'fetch account cash') and Jentic returns the matching Trading212 Public API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Trading212 Public API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Trading212 Public API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.