> ## Documentation Index > Fetch the complete documentation index at: https://finance.dev/llms.txt > Use this file to discover all available pages before exploring further. # Get Event Contracts > Returns a single event together with every contract defined under it, read live from the catalogue. **Use Case:** Enumerate the tradable strikes of one event, and read current tradability before acting on a search hit. ## Overview An **event** is one real-world question (for example `HORC_1126`). The **contracts** under it are the individual tradable outcomes or strikes. This endpoint returns the event's metadata plus the full contract list in one response. ``` GET /v1/predictions/events/HORC_1126/contracts ``` ## This is the current view [Search](/api-reference/predictions/search) reads a full-text index that trails the catalogue by seconds. This endpoint reads the catalogue itself. Anything that must be current — in particular `state` and `tradable` — should be read here, using the `symbol` from a search hit as the key, rather than taken from the hit. ## Response `data.event` carries the event, `data.contracts` the array of contracts: ```json theme={null} { "success": true, "data": { "event": { "eventId": "HORC_1126", "baseEventId": "HORC", "eventQuestion": "Which party will control the House after the 2026 election?", "timeSpecifier": "2026.11", "lastSyncedAt": "2026-04-18T13:45:01.234Z" }, "contracts": [ { "symbol": "HORC_1126_Republican", "eventId": "HORC_1126", "baseEventId": "HORC", "state": "ACTIVE", "tradable": true, "nonTradable": false, "tickSize": "0.01", "symbolSubTypes": [], "lastSyncedAt": "2026-04-18T13:45:01.234Z" } ] } } ``` ### Fields worth knowing | Field | Notes | | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | `tickSize` | Exact decimal as a string. Parse with a decimal type. | | `timeSpecifier` | Published precision of the event, one of `YYYY`, `YYYY.MM`, or `YYYY.MM.DD`. | | `expectedPayoutTime`, `expectedLastTradeTime`, `expectedResolutionTime` | Venue **wall-clock** times. The feed carries no time zone, so the trailing `Z` is a label, not a conversion — do not shift these into local time. | | `priceLimit`, `tradingSchedule`, `rawPayload` | Venue JSON passed through unchanged; shape is not guaranteed stable. | ## Example ```bash theme={null} curl -X GET "https://api.aries.com/v1/predictions/events/HORC_1126/contracts" ``` ## Errors * `400` — `eventId` missing or malformed * `404` — no event with that ID * `500` — unexpected server error ## OpenAPI ````yaml openapi.json GET /v1/predictions/events/{eventId}/contracts openapi: 3.0.3 info: contact: email: dev@aries.com name: Aries Financial description: >- OpenAPI Specification for the Aries trading platform API. # Authentication Learn how to authenticate with the Aries API using OAuth2 and manage access tokens in your SDK. ## Overview The Aries API uses **OAuth2 with Bearer tokens** (JWT format) for authentication. All API requests require a valid access token in the `Authorization` header: ``` Authorization: Bearer ``` ## Providing Client ID and Client Secret (SDK) When using the generated SDK, provide your **Client ID** and **Client Secret** when you create the API client (e.g. in the constructor or security options). The SDK will use these to obtain and refresh the access token internally; you do not need to manage tokens yourself. Obtain your OAuth2 credentials from the Aries platform (e.g. Client Center / Manage Account at https://app.aries.com): - **Client ID** – Your application identifier (pass to SDK client) - **Client Secret** – Your application secret key (pass to SDK client; use PKCE for public clients where secret cannot be stored) ## Authentication Flow ### 1. Authorization Code Flow For server-side or confidential clients: 1. **Redirect the user** to the authorization URL to sign in and consent: - **URL:** `https://app.aries.com/oauth2/authorize` - **Query params:** `response_type=code`, `client_id`, `redirect_uri`, `scope`, `state` 2. **Exchange the code for tokens** (after user is redirected back with `?code=.`): - **POST** `https://api.aries.com/v1/oauth2/token` - **Body:** `grant_type=authorization_code`, `code`, `redirect_uri`, `client_id`, `client_secret` - Response includes `access_token` and `refresh_token` 3. **Call the API** with the access token: `Authorization: Bearer ` ### 2. PKCE Flow For SPAs and mobile apps (public clients that cannot store `client_secret`): 1. Generate a **code_verifier** (random string) and **code_challenge** = BASE64URL(SHA256(code_verifier)). 2. **Redirect the user** to `https://app.aries.com/oauth2/authorize` with `code_challenge`, `code_challenge_method=S256`, plus `client_id`, `redirect_uri`, `scope`, `state`. 3. **Exchange the code** at POST `https://api.aries.com/v1/oauth2/token` with `grant_type=authorization_code`, `code`, `redirect_uri`, `client_id`, `code_verifier` (no client_secret). 4. Use the returned `access_token` as Bearer. ### 3. MFA Verification If the user has MFA enabled, the authorize step may return `is_mfa: true` and a `next_step_auth_id`. Call **POST** `https://api.aries.com/v1/oauth2/authorize/mfa` with `next_step_auth_id` and `verification_code` (6-digit code). Then continue with **POST** `/v1/oauth2/authorize/confirm` to get the authorization code, and exchange it at `/v1/oauth2/token`. ## Token Management - **Refresh when expired:** POST `https://api.aries.com/v1/oauth2/token` with `grant_type=refresh_token`, `client_id`, `client_secret`, `refresh_token`. - **Using a Bearer token directly:** If you already have an access token, set the header `Authorization: Bearer ` on every request. The SDK can accept a pre-obtained token and use it until it expires. ## OAuth2 Scopes Request only the scopes your application needs. Available scopes: | Scope | Description | |-------|-------------| | `user:information` | View user profile and personal details | | `account:information` | View account balances, positions, and transaction history | | `order:execution` | Place, modify, and cancel orders | | `order:information` | View order history and status | | `position:information` | View current positions and holdings | | `market:information` | Access live and historical market data | | `calendar:information` | Access earnings, economic, and market schedule data | | `options:information` | Access options chains and expiration data | | `analytics:information` | View analytics, ratings, and market insights | | `market:supplemental` | News, company profiles, financials, filings, ETF data, technical analysis | Specify multiple scopes as a space-separated string, e.g. `account:information order:execution market:information`. ## Security Best Practices - **Store credentials securely** – Use environment variables or a secrets manager for `client_id` and `client_secret`. Never hardcode them. - **Handle token expiration** – Check for 401 responses and refresh the token using the refresh_token, then retry the request. - **Use HTTPS** – All authorization and token endpoints must be called over HTTPS. - **Validate state** – When using the authorization code flow, validate the `state` parameter on the callback to prevent CSRF. ## Error Handling - **400 Bad Request** – Invalid or missing parameters, validation failures, or malformed JSON. Response bodies follow the same patterns as other errors (flat `error` string, optional `codes`, nested `error` object, or rarely no body). - **401 Unauthorized** – Invalid or expired access token; refresh the token or re-authenticate. JSON bodies are not identical on every route: you may see a flat `error` string (sometimes with `codes`), a nested `error` object (`type`, `code`, `message`), or rarely an empty body - **403 Forbidden** – Insufficient scope or permissions for the requested resource. Error JSON may be flat or nested, like 400/401. - **404 Not Found** – Resource does not exist or is not visible. Error JSON may be flat or nested. - **429 Too Many Requests** – Rate limit exceeded; slow down and respect `Retry-After` when the header is present. Error JSON may be flat or nested. - **500 / 5xx** – Server or upstream failure; retry with backoff. Do not depend on a single error JSON shape; some responses may have no body. --- Endpoints in this spec: health, OAuth2 (authorize, confirm, mfa, token), users, accounts, orders, market data, watchlist, chart, analytics, calendars, company, economy, financials, indices, options, news, and supplemental data. title: Aries API — OpenAPI Specification version: 1.0.0 servers: - description: Production server url: https://api.aries.com security: [] tags: - description: >- Analytics endpoints for market data analysis including top gainers, losers, volume leaders, sector analysis, analyst ratings, market breadth, and net inflow name: Analytics - description: User management and profile endpoints name: Users - description: >- Order management endpoints for placing, updating, canceling, and previewing orders name: Orders - description: Account management endpoints for positions, orders, and balances name: Accounts - description: Calendar and mergers/acquisitions endpoints name: Calendar - description: >- Market data endpoints for symbol search, real-time data access, and equity details name: Market Data - description: >- Watchlist endpoints for listing, creating, updating, and deleting watchlists name: Watchlist - description: Chart endpoints for config, symbols, history, quotes, and server time name: Chart - description: News and news sentiment endpoints name: News - description: >- Indices endpoints for groups, list, search, bar, bars, chart-bars, realtime values name: Indices - description: Logos search and sync endpoints name: Logos - description: 'Corporate actions: spinoffs, tender offers, IPO calendar, dividends' name: Corporate Actions - description: 'Economy endpoints: inflation, inflation expectations, treasury yields' name: Economy - description: >- Options endpoints: expiry dates, contracts, activity, trades, quotes, unusual activity name: Options - description: >- Financials: reported, statements, revenue breakdown, short volume, ratios, short interest name: Financials - description: Signals and bull-bear cases name: Signals - name: Company - name: ETF - name: Filings - name: Market - name: Ownership - name: Stocks - name: Stock Estimates - name: Stock Alternative description: >- Transcripts, company presentation, social sentiment, investment themes, supply chain, and ESG data - name: Technical Analysis - name: Prediction Historical Data description: Historical YES/NO tick data for prediction-market contracts - name: Prediction Market Data description: >- Prediction-market reference data and full-text search over base events, events, and contracts paths: /v1/predictions/events/{eventId}/contracts: servers: - url: https://api.aries.com description: Production - url: https://api.tradearies.dev description: Staging get: tags: - Prediction Market Data summary: Get an event and all contracts under it operationId: getEventContracts parameters: - name: eventId in: path required: true schema: type: string example: HORC_1126 responses: '200': description: Event with its contracts content: application/json: schema: allOf: - $ref: '#/components/schemas/PredMdSuccessEnvelope' - type: object properties: data: $ref: '#/components/schemas/PredMdEventWithContracts' '400': $ref: '#/components/responses/PredMdBadRequest' '404': $ref: '#/components/responses/PredMdNotFound' '500': $ref: '#/components/responses/PredMdInternalServerError' security: [] components: schemas: PredMdSuccessEnvelope: type: object description: >- Standard success envelope used by all success responses. `data` is endpoint-specific. properties: success: type: boolean example: true data: {} required: - success PredMdEventWithContracts: type: object properties: event: $ref: '#/components/schemas/PredMdEvent' contracts: type: array items: $ref: '#/components/schemas/PredMdContract' required: - event - contracts PredMdEvent: type: object description: One real-world event under a base event (e.g. HORC_1126). properties: eventId: type: string baseEventId: type: string eventDisplayName: type: string eventQuestion: type: string sourceAgency: type: string sourceAgencyUrl: type: string underlyingSpec: type: string calculationMethod: type: string timeSpecifier: type: string description: 'Published precision: YYYY, YYYY.MM or YYYY.MM.DD.' example: '2026.06' expectedPayoutTime: type: string format: date-time nullable: true description: >- Venue wall-clock time; the feed carries no zone, so the Z is a label, not a conversion. expectedLastTradeTime: type: string format: date-time nullable: true description: >- Venue wall-clock time; the feed carries no zone, so the Z is a label, not a conversion. expectedResolutionTime: type: string format: date-time nullable: true description: >- Venue wall-clock time; the feed carries no zone, so the Z is a label, not a conversion. lastSyncedAt: format: date-time type: string required: - eventId - baseEventId - lastSyncedAt PredMdContract: type: object description: A single tradable event contract at a specific strike. properties: symbol: type: string eventId: type: string baseEventId: type: string description: type: string question: type: string state: type: string tradable: type: boolean nonTradable: type: boolean strikeValue: type: string strikeUnit: type: string evaluationType: type: string baseCurrency: type: string tickSize: type: string format: decimal description: >- Exact decimal, serialized as a string so no client parses it through a float. example: '0.01' multiplier: type: integer minTradeQty: type: string symbolSubTypes: items: type: string type: array startDate: type: string format: date-time nullable: true expirationDate: type: string format: date-time nullable: true terminationDate: type: string format: date-time nullable: true lastTradeDate: type: string format: date-time nullable: true priceScale: type: string priceLimit: description: Venue JSON payload (passthrough). tradingSchedule: description: Venue JSON payload (passthrough). rawPayload: description: Venue JSON payload (passthrough). lastSyncedAt: format: date-time type: string required: - symbol - eventId - baseEventId - state - tradable - nonTradable - lastSyncedAt - tickSize - symbolSubTypes ErrorEnvelope: type: object description: >- Prediction-market error envelope. Returned by historical-data and prediction-market reference endpoints on 400/404/500/502. properties: success: type: boolean example: false error: $ref: '#/components/schemas/AppError' required: - success - error AppError: type: object description: Structured application error returned inside an `ErrorEnvelope`. properties: type: type: string description: >- Categorical error type. Use this for branching error-handling logic; the values are stable across endpoints: - `VALIDATION` — request body or query parameters failed validation. - `AUTHENTICATION` — missing, invalid, or expired token. - `AUTHORIZATION` — token is valid but lacks the required scope/permission. - `NOT_FOUND` — the requested resource does not exist. - `CONFLICT` — request conflicts with current state (e.g. duplicate). - `INTERNAL` — server-side error; retry or contact support. - `TIMEOUT` — operation took too long. - `UNKNOWN` — uncategorized error; check `message`. (Additional categorical values may appear in service-specific responses.) enum: - UNKNOWN - VALIDATION - AUTHENTICATION - AUTHORIZATION - NOT_FOUND - CONFLICT - INTERNAL - TIMEOUT - RATE_LIMIT - BAD_REQUEST - DATABASE - EXTERNAL_SERVICE - PRECONDITION_FAILED - SERVICE_UNAVAILABLE - GRPC - QUEUE - JSON_PARSING code: type: string description: Machine-readable code, e.g. `SYMBOL_REQUIRED`, `EVENT_NOT_FOUND`. example: SYMBOL_REQUIRED message: type: string description: >- Error detail as a string. Exact message content is not fixed and should not be hard-coded. example: string details: type: object additionalProperties: true service: type: string operation: type: string request_id: type: string required: - type - code - message responses: PredMdBadRequest: description: >- Invalid request (validation error, malformed JSON, or missing required parameters). Response body is a prediction-market `ErrorEnvelope` with a structured `AppError`. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: success: false error: type: VALIDATION code: SYMBOL_REQUIRED message: string PredMdNotFound: description: >- Resource not found. Response body is a prediction-market `ErrorEnvelope` with a structured `AppError`. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: success: false error: type: NOT_FOUND code: EVENT_NOT_FOUND message: string PredMdInternalServerError: description: >- Unexpected server error. Response body is a prediction-market `ErrorEnvelope` with a structured `AppError`. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: success: false error: type: INTERNAL code: INTERNAL_ERROR message: string ````