> ## Documentation Index > Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt > Use this file to discover all available pages before exploring further. # List trading venues > List the perpetual-futures trading venues (providers), each with the actions it supports and a JSON Schema per action describing the exact `args` that action accepts. This is a proxy to the Yield.xyz Perps `GET /v1/providers` endpoint. Portal validates the upstream response against the schema documented here before returning it under `data`, and translates funding-chain `network` values to CAIP-2 (venue slugs pass through unchanged). If Yield.xyz changes the response shape, Portal returns a 500 with `id: INTEGRATION_RESPONSE_SCHEMA_DRIFT` instead of a partial response. Upstream reference: [Yield.xyz Perps API](https://docs.yield.xyz). ## OpenAPI ````yaml /openapi/client-api.yaml get /clients/me/integrations/yield-xyz-perps/providers openapi: 3.1.0 info: title: Portal Client API version: '3.0' description: > The Portal Client API provides endpoints for managing wallets, building transactions, and interacting with blockchain networks. All endpoints require authentication via a Client API Key or Client Session Token (CST) passed as a Bearer token. ## Base URL `https://api.portalhq.io/api/v3` ## Authentication Include your Client API Key or Client Session Token as a Bearer token in the `Authorization` header of every request. ## Chain ID Format Chain parameters use either friendly names (e.g. `ethereum`, `solana`) or CAIP-2 format (e.g. `eip155:1`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`). When using CAIP-2 format in URLs, ensure the colon is URI-encoded (`%3A`). servers: - url: https://api.portalhq.io/api/v3 description: Production security: - bearerAuth: [] tags: - name: Clients description: Core client management endpoints - name: Wallet description: >- Read wallet state — balances, NFTs, transaction history, capabilities, and transaction details - name: Transactions description: Build, broadcast, and evaluate blockchain transactions - name: Funding description: Fund wallets with testnet tokens - name: Wallet Shares description: Manage signing and backup share pairs - name: Delegations description: Manage token approvals, revocations, and delegated transfers - name: Session Keys description: Manage EIP-7702 session keys for smart accounts - name: 0x description: Token swap endpoints powered by the 0x protocol - name: Yield.xyz description: Yield opportunities and staking actions powered by Yield.xyz - name: Yield.xyz Borrow description: >- Supply collateral, borrow, repay and withdraw from lending markets (Aave V3, Morpho Blue, SparkLend, Lista) powered by Yield.xyz Borrow - name: Yield.xyz Perps description: >- Trade perpetual futures — open/close leveraged positions, manage stop-loss/take-profit, and fund/withdraw a trading account — powered by Yield.xyz Perps - name: Li.Fi description: Cross-chain swaps and bridging powered by Li.Fi - name: Blockaid description: Transaction and address security scanning powered by Blockaid - name: Hypernative description: >- Transaction, address, token, and NFT security scanning powered by Hypernative - name: Noah description: KYC onboarding, payins, and payouts powered by Noah - name: Meld description: Buy and sell crypto with fiat through aggregated providers powered by Meld - name: Due description: Payins, payouts, virtual accounts, and FX powered by Due - name: EIP-7702 description: EIP-7702 account type detection and authorization management - name: Deprecated description: >- Legacy endpoints scheduled for removal. Use the newer equivalents listed in each endpoint's description. paths: /clients/me/integrations/yield-xyz-perps/providers: get: tags: - Yield.xyz Perps summary: List trading venues description: >- List the perpetual-futures trading venues (providers), each with the actions it supports and a JSON Schema per action describing the exact `args` that action accepts. This is a proxy to the Yield.xyz Perps `GET /v1/providers` endpoint. Portal validates the upstream response against the schema documented here before returning it under `data`, and translates funding-chain `network` values to CAIP-2 (venue slugs pass through unchanged). If Yield.xyz changes the response shape, Portal returns a 500 with `id: INTEGRATION_RESPONSE_SCHEMA_DRIFT` instead of a partial response. Upstream reference: [Yield.xyz Perps API](https://docs.yield.xyz). operationId: listYieldXyzPerpsProviders responses: '200': description: List of trading venues content: application/json: schema: $ref: '#/components/schemas/YieldXyzPerpsProvidersResponse' '400': description: >- Invalid request (a field failed validation, or a funding `network` is not a chain Portal supports). Also returned when Yield.xyz Perps rejects the request (e.g. a 412 precondition such as insufficient margin) or the configured API key; a vendor `details.code` is surfaced when present. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Yield.xyz Perps rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: >- Yield.xyz Perps returned a response that does not match the schema Portal expects (`id: INTEGRATION_RESPONSE_SCHEMA_DRIFT`). content: application/json: schema: $ref: '#/components/schemas/IntegrationSchemaDriftErrorResponse' '503': description: Yield.xyz Perps is unreachable or returned an upstream error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: YieldXyzPerpsProvidersResponse: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/YieldXyzPerpsProvider' ErrorResponse: type: object properties: error: type: string description: Error message describing what went wrong IntegrationSchemaDriftErrorResponse: type: object description: >- Returned (HTTP 500) when a third-party response no longer matches the schema Portal proxies for it. The `id` is stable: SDKs should key off it and fail gracefully. Portal is alerted automatically and fixes the mapping server-side. required: - error - id - details properties: error: type: string example: >- yield-xyz-borrow returned a response for GET /v1/positions that does not match the expected schema id: type: string enum: - INTEGRATION_RESPONSE_SCHEMA_DRIFT details: type: object required: - integration - endpoint - issues properties: integration: type: string example: yield-xyz-borrow endpoint: type: string description: The upstream vendor endpoint whose response drifted. example: GET /v1/positions issues: type: array items: type: object required: - path - message - code properties: path: type: string description: Dotted path of the offending field in the vendor response. example: supplyBalances.0.balanceUsd message: type: string example: Expected string, received number code: type: string example: invalid_type YieldXyzPerpsProvider: type: object description: A trading venue. required: - id - name - network - metadata - supportedActions - argumentSchemas properties: id: type: string description: Opaque venue slug, used unchanged as `providerId` everywhere else. example: hyperliquid name: type: string example: Hyperliquid network: type: string description: Venue slug (a venue is not a chain; passed through unchanged). example: hyperliquid metadata: $ref: '#/components/schemas/YieldXyzPerpsProviderMetadata' supportedActions: type: array description: >- Actions this venue supports. Known values: `open`, `close`, `updateLeverage`, `stopLoss`, `takeProfit`, `cancelOrder`, `editOrder`, `fund`, `withdraw`, `approveAgent`, `approveBuilderFee`, `updateMargin`, `setTpAndSl`, `setUnifiedAccount`. Treat unknown values as opaque. items: type: string example: - open - close - fund - withdraw - approveAgent argumentSchemas: type: object additionalProperties: true description: >- A JSON Schema per action describing the exact `args` that action accepts on this venue. YieldXyzPerpsProviderMetadata: type: object description: >- Venue display metadata. Fields are soft (nullable) so a single venue missing one does not fail the list. properties: description: type: string nullable: true example: A high-performance L1 optimized for perpetual futures trading. externalLink: type: string nullable: true example: https://hyperliquid.xyz logoURI: type: string nullable: true example: https://assets.stakek.it/providers/hyperliquid.svg securitySchemes: bearerAuth: type: http scheme: bearer description: > Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header. ````