EVEDEX Hedging API

The Hedging API from EVEDEX — 2 operation(s) for hedging.

Operations 2

POST /api/hedging/finery/account
POST /api/hedging/bybit/account

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/evedex-hedging-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

evedex-hedging-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: EVEDEX - Backoffice general Hedging API
  version: 1.0.0
servers:
- url: https://backoffice-api.private.evedex.com
tags:
- name: Hedging
paths:
  /api/hedging/finery/account:
    post:
      tags:
      - Hedging
      security:
      - AccessToken: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FineryAccountObject'
      responses:
        '200':
          description: 200 OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EmptyResponse'
  /api/hedging/bybit/account:
    post:
      tags:
      - Hedging
      security:
      - AccessToken: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BybitAccountObject'
      responses:
        '200':
          description: 200 OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EmptyResponse'
components:
  schemas:
    BybitAccountObject:
      type: object
      properties:
        user:
          type: string
          format: uuid
        name:
          type: string
        accountType:
          type: string
          enum:
          - UNIFIED
          - REGULAR
        apiKey:
          type: string
        apiSecret:
          type: string
      required:
      - user
      - name
      - accountType
      - apiKey
      - apiSecret
    FineryAccountObject:
      type: object
      properties:
        user:
          type: string
          format: uuid
        name:
          type: string
        apiKey:
          type: string
        apiSecret:
          type: string
      required:
      - user
      - name
      - apiKey
      - apiSecret
    EmptyResponse:
      type: object
  securitySchemes:
    AccessToken:
      type: http
      scheme: bearer