canonical: https://jentic.com/apis/tradematic.com/tradematic-cloud-api

# Tradematic Cloud API

Overview Tradematic Cloud is a trading infrastructure for building investment services. It’s a trading engine + API + ready-made adapters to stock and forex brokers, crypto exchanges, and market data providers. You can use it as a cloud API, or you can deploy it on your servers. How to use Tradematic Cloud API Sign up at [tradematic.cloud](https://tradematic.cloud). After signing up, you will rece. The API exposes 67 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create new autofollow strategy, get autofollow strategies list. Covers 67 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create new autofollow strategy
- Get autofollow strategies list
- Update autofollow strategy
- Send a new signal for autofollow strategy
- Monitor Tradematic Cloud API operational status and events

## Use cases

### Developer Tools Operations

Use the Tradematic Cloud API to perform developer tools operations programmatically. The API provides 67 endpoints covering core functionality including create new autofollow strategy, get autofollow strategies list, get autofollow strategy by id.

Example prompt: Call POST `/autofollow/strategies` to create new autofollow strategy

### Automated Status API Management

Automate status API operations by combining multiple Tradematic Cloud API endpoints. Agents can get autofollow strategies list and then get autofollow strategy by id in a single workflow.

Example prompt: Call GET `/autofollow/strategies` to get autofollow strategies list, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tradematic Cloud 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 'create new autofollow strategy', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/autofollow/strategies` | Create new autofollow strategy |
| GET | `/autofollow/strategies` | Get autofollow strategies list |
| GET | `/autofollow/strategies/{strategyid}` | Get autofollow strategy by ID |
| PUT | `/autofollow/strategies/{strategyid}` | Update autofollow strategy |
| PUT | `/autofollow/strategies/{strategyid}/content` | Update rules for strategy that was created with strategy builder |
| GET | `/autofollow/strategies/{strategyid}/positions` | Get positions for strategy |
| POST | `/autofollow/strategies/{strategyid}/signals` | Send a new signal for autofollow strategy |
| GET | `/autofollow/strategies/{strategyid}/signals` | Get trading signals for strategy |

## Key resources

- **Status API** — Server status
- **Client API** — Clients management
- **Autofollow API** — Trading signals and copy trading
- **TaskManager API** — Backtest and optimization tasks management
- **Builder API** — Strategy builder

## Why Jentic

- **Setup:** Wiring the Tradematic Cloud API by hand means setting up its X-API-Key header auth against api.tradematic.com and handling error and retry behavior yourself. Through Jentic you install once, import the Tradematic Cloud API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Tradematic puts the strategy id in the URL path (`/autofollow/strategies/{strategyId}/...`), so a rule can pin your agent to one autofollow strategy: it can read that strategy's positions and signals and nothing else. You choose the operations it may call, so a strategy update or a new strategy creation is not included unless you add it.
- **Credential handling:** Your Tradematic Cloud 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 'create a new autofollow strategy' or 'read a strategy's positions', and Jentic returns the matching Tradematic Cloud 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 Tradematic Cloud API use?

The Tradematic Cloud API uses an API key passed in the `X-API-Key` 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 create new autofollow strategy with the Tradematic Cloud API?

Yes. Use the POST `/autofollow/strategies` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tradematic Cloud 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 create new autofollow strategy through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create new autofollow strategy'. Jentic returns the matching Tradematic Cloud API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tradematic Cloud API have?

The Tradematic Cloud API exposes 67 endpoints covering status API, client API, autofollow API operations.

### Can I limit what my agent is allowed to do with the Tradematic Cloud API?

Yes. Because Jentic One is self-hosted, your own rules decide which Tradematic Cloud operations and credentials the agent may use. Since Tradematic puts the strategy ID in the URL path, such as `/autofollow/strategies/{strategyId}/positions` and `/autofollow/strategies/{strategyId}/signals`, you can pin the agent to a single strategy and allow only reads of that strategy's positions and signals. You choose the operations it may call, so a strategy update or a new strategy creation stays blocked unless you add it.