> ## Documentation Index > Fetch the complete documentation index at: https://docs.trdrs.co/llms.txt > Use this file to discover all available pages before exploring further. # List Connect’s tiles > Returns the tiles Connect shows a trader in the trading platform: each listed venue, as a venue’s entry that opens the provider the venue runs on, and each listed provider a trader signs in to with their own login, as a provider’s own entry. A trader who is signed in also sees each provider a venue that issued them an account plugged in and shows its traders. The route is keyless: a trader deciding where to connect hasn’t signed in yet. ## OpenAPI ````yaml /api/openapi.json get /api/connect/tiles openapi: 3.1.0 info: title: trdrs Engine API version: 1.1.0 description: >- ## API Reference Every route the trdrs engine serves, with what to send and what comes back. It covers market data and news, trading and account state for a trader's own software, the Connect API a Connect app's backend calls and the Connect dashboard's routes, Connect pre-registration, the statements that carry a Connect account between environments, the venue routes a prop firm or brokerage runs its accounts through, and a trader's own challenges. Start with the Quickstart for your first call. The API standards hold the rules every route shares: keys, errors, rate limits, idempotency, paging and streaming. servers: - url: https://app.trdrs.co description: Production - url: / description: This engine security: [] tags: - name: Venue platform preview description: >- Run your venue: its providers, instruments, conditions, groups, routes, stages, venue rules, keys, accounts, usage, balance receipts and webhooks. These routes are in preview. They are served on the sandbox to every venue, and production access is arranged when a venue qualifies. Every route here under `/api/venues/` takes a Venue key. The back office reaches the same routes under `/api/back-office/` with a verified owner’s session, because the Venue key stays on your server, and both run the same checks. The team’s routes under `/api/organizations` serve the back office and the Connect dashboard alike, since one organization can run venues and Connect apps with one team. Changes to these routes are additive only from here on. - name: Market data description: >- Search and look up symbols, read price history and quotes, check the server clock, and stream live bars. Crypto prices come from each provider’s public feed. Futures prices are licensed to each user and stream only from that trader’s own futures source: a login on their venue’s production Rithmic system, under their own market data subscription. A Rithmic Test login carries no market data. Without a source, a futures request answers 503 `feed_requires_connection` and the symbol search lists no futures. - name: News description: >- Market news and the economic calendar, from licensed and open sources, tagged with futures roots as they arrive. The content is the same for everyone, and these routes admit the same callers as market data: a licensed origin, a session or a Trading API key. Page headlines by publish time, filter them by instrument root, and stream them live over server-sent events. Thumbnails come through the image route. - name: Trading description: >- Place, change and cancel orders, set a position’s exits, and close or flatten positions. Every call that places an order takes a `clientOrderId` as its idempotency key. - name: Account description: >- Read an account a trader can trade: its balance, positions, working orders, fills, profit and loss history, and the live account stream. You don’t create accounts here. A trader connects their own account at a provider, or opens their own Demo on the paper book, in the trdrs app. A venue issues accounts on the paper book with Issue an account into a group, and a venue pre-registers accounts at a provider through Connect with Pre-register a trader’s account. - name: Connect description: >- Connect is the account picker a trader opens: in the trdrs app, where it lists the built-in providers and every listed venue, and in hosted Connect on a Connect app’s website, where it lists the tiles the app chose. The pre-registration routes let a venue fill Connect in the trdrs app ahead of time, for a trader who signs in to trdrs. You tell trdrs that a trader has an account at a built-in provider: their sign-in email, and optionally the account number and login name. When that trader signs in, Connect shows the account ready to link, and they sign in to the provider themselves, once. The trader types their own password, and access starts when their own login succeeds. You can list who you pre-registered and who has linked, and cancel a pre-registration that hasn’t been used. A pre-registration expires after 30 days, and sending it again refreshes it. These routes take the pre-registration key. The whole flow is in the **[Quick Start](/docs/guides/quick-start)**. - name: Connect apps preview description: >- Run a Connect app: your own trading interface, whose traders connect their accounts in hosted Connect on your website and trade them on your screens. The Connect API is what your backend calls with your app’s API key: Create a Connect link, read and close it, and the account, market and trading routes with your trader named in `x-trdrs-trader`. Hosted Connect calls its own routes with the frame session a Connect link opens. The Connect dashboard calls the rest with your Connect sign-in session: your apps, each app’s name and logo, API keys, websites, tiles, white-label paper and Demos, traders and active traders, invoices, conformance runs and its Connect pass. These routes are in preview, served on the sandbox, where they are free. Once production opens to Connect apps, it serves the route that records an app’s Connect pass, which opens the app’s production. - name: Connect accounts description: >- A Connect client's team signs in to the Connect dashboard with a Connect account of its own, never a trader's, and one login reaches both environments. Production answers a short statement for the signed-in account, naming its verified email and the Connect apps it owns, and sandbox exchanges it for a sandbox session and the counterpart app of each: the sandbox app that stands for the production one. The environments share no credential: production signs the statement with its own key, and sandbox checks it with production's public key alone. These routes take the Connect dashboard's own session, from the dashboard's origin; a trader's session and every key are refused, and a Connect account's session reaches no trading, account, market or AI route. - name: Challenges description: >- These routes list evaluation programs and a trader’s own enrollments. **Preview: the one group in this reference outside the additive-only guarantee.** Their shapes will change when challenges are rebuilt; see Stability. **They take a signed-in session, not a key**, and are served only where the engine runs with `CHALLENGES_ENABLED`. Without it, the routes don’t exist and every one answers `404`. The administration half isn’t documented here, because it is trdrs’s own tooling, not part of the API. paths: /api/connect/tiles: get: tags: - Connect summary: List Connect’s tiles description: >- Returns the tiles Connect shows a trader in the trading platform: each listed venue, as a venue’s entry that opens the provider the venue runs on, and each listed provider a trader signs in to with their own login, as a provider’s own entry. A trader who is signed in also sees each provider a venue that issued them an account plugged in and shows its traders. The route is keyless: a trader deciding where to connect hasn’t signed in yet. responses: '200': description: The tiles, in Connect’s order. content: application/json: schema: $ref: '#/components/schemas/ConnectTilesResponse' x-codeSamples: - lang: javascript label: TypeScript source: |- const res = await fetch('https://app.trdrs.co/api/connect/tiles', { headers: { Authorization: `Bearer ${process.env.TRDRS_API_KEY}` }, }) const data = await res.json() - lang: shell label: cURL source: |- curl 'https://app.trdrs.co/api/connect/tiles' \ -H "Authorization: Bearer $TRDRS_API_KEY" components: schemas: ConnectTilesResponse: type: object description: Connect’s tiles. properties: tiles: type: array items: $ref: '#/components/schemas/ConnectTile' description: >- Each listed venue and each listed provider a trader signs in to with their own login, in Connect’s order, then the providers a venue plugged in and shows the signed-in trader. required: - tiles example: tiles: - id: 00000000-0000-0000-0000-000000000001 name: Meridian Futures provider: rithmic loginStyle: trader_login entry: venue logoUrl: >- /api/connect/companies/00000000-0000-0000-0000-000000000003/logo.png logoBleed: true referralUrl: null system: Meridian connectEnvironment: live blurb: null enabled: true sortOrder: 20 access: open - id: 00000000-0000-0000-0000-000000000002 name: Hyperliquid provider: hyperliquid loginStyle: wallet_key entry: provider logoUrl: null logoBleed: false referralUrl: null system: null connectEnvironment: null blurb: Crypto perpetuals via an agent key enabled: true sortOrder: 70 access: open ConnectTile: type: object description: >- One tile in Connect: a venue’s entry, which opens the provider the venue runs on, or a provider’s own. It says what it opens, how a trader signs in to it, and how it looks. properties: id: type: string description: The tile’s id. On white-label paper it is `paper:{appId}`. name: type: string description: The name the tile shows. provider: type: string enum: - rithmic - tastytrade - hyperliquid - binance - bybit - paper - public description: >- The provider the tile opens: for a venue’s tile, the provider the venue runs on. `paper` is trdrs’s paper book, which a trader opens by signing in to trdrs, and `public` is a provider a venue plugged in and shows its own traders. loginStyle: type: string enum: - trader_login - oauth - api_key - wallet_key - firm_credentials - none description: How a trader signs in to that provider, as the provider declares it. entry: type: string enum: - venue - provider description: >- Whose entry the tile is: a venue’s, or a provider’s own. White-label paper is the paper book’s entry under a Connect app’s name. logoUrl: type: - string - 'null' description: The tile’s logo, or null for none. logoBleed: type: boolean description: True when the logo’s art reaches its edges; false without a logo. referralUrl: type: - string - 'null' description: Where a trader without an account opens one, or null. system: type: - string - 'null' description: The Rithmic system a venue’s Rithmic tile signs in to, or null. connectEnvironment: type: - string - 'null' enum: - live - sim - null description: >- The Rithmic gateway family this environment connects through: `sim` in the sandbox and `live` in production. Null for every other provider. blurb: type: - string - 'null' description: One line about the venue or provider, or null. enabled: type: boolean description: True while the tile can be opened. sortOrder: type: integer description: 'The tile’s place: Connect shows tiles in ascending order.' access: type: string enum: - open - unknown - gated description: >- Whether a venue’s Rithmic system lets traders in through trdrs: `gated` shows as coming soon, and a system no login has proved yet is `unknown`. Every other tile is `open`. required: - id - name - provider - loginStyle - entry - logoUrl - logoBleed - referralUrl - system - connectEnvironment - blurb - enabled - sortOrder - access ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.