broker-openapi

Manual merge YES/NO positions

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://bump.sh/tie-tech/hub/b2b-api/doc/broker-openapi/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "broker-openapi MCP server": {
    "url": "https://bump.sh/tie-tech/hub/b2b-api/doc/broker-openapi/mcp"
  }
}
Close
POST /trading/accounts/{account_id}/merge
Api key auth

Annihilate equal amounts of YES and NO tokens to release capital. The merge_id is deterministically generated from the request fingerprint (cmd_id).

Headers

  • PRE-ACCESS-KEY string Required

    Broker access key identifier.

    Format should match the following pattern: ^[A-Za-z0-9._~-]{1,64}$.

  • PRE-ACCESS-SIGNATURE string Required

    Keyed BLAKE2b-256 signature (hex lowercase, 64 characters).

    Format should match the following pattern: ^[0-9a-f]{64}$.

  • PRE-ACCESS-TIMESTAMP string(date-time) Required

    RFC3339 timestamp with milliseconds (e.g., 2025-10-30T06:00:34.075Z). Must be within clock_skew_tolerance (default 5m) of server time.

  • Idempotency-Key string Required

    Stable idempotency token reused on retries. Reuse with identical payload => 202. Reuse with different payload => 409 idempotency_key_mismatch.

    Maximum length is 64. Format should match the following pattern: ^[A-Za-z0-9._~-]{1,64}$.

Path parameters

  • account_id string Required

    Broker-supplied account identifier; length 1..128; charset [A-Za-z0-9._~-].

    Maximum length is 128. Format should match the following pattern: ^[A-Za-z0-9._~-]{1,128}$.

application/json

Body Required

  • market_id string Required
  • qty object Required
    Hide qty attributes Show qty attributes object
    • units integer(int64) Required
    • nanos integer(int32) Required

      Minimum value is -999999999, maximum value is 999999999.

  • client_ref_id string Required

    Client-supplied identifier for correlation (client_merge_id).

    Maximum length is 64. Format should match the following pattern: ^[A-Za-z0-9._~-]{1,64}$.

Responses

  • 202 application/json

    Merge command accepted

    Hide response attributes Show response attributes object
    • ref_id string Required

      System fingerprint of the request (cmd_id). Use for correlation with Accounting Stream.

    • client_ref_id string Required

      The client-supplied reference ID for correlation.
  • 409 application/json

    Idempotency-Key reused with different payload

    Hide response attributes Show response attributes object
    • error_code string Required
    • message string Required
    • details object

      Additional properties are allowed.
  • 422 application/json

    Validation / semantic error

    Hide response attributes Show response attributes object
    • error_code string Required
    • message string Required
    • details object

      Additional properties are allowed.
  • 503 application/json

    Backpressure / temporary unavailability

    Hide response attributes Show response attributes object
    • error_code string Required
    • message string Required
    • details object

      Additional properties are allowed.
POST /trading/accounts/{account_id}/merge 
curl \
 --request POST 'https://api.example.com/v1/trading/accounts/{account_id}/merge' \
 --header "Content-Type: application/json" \
 --header "PRE-ACCESS-KEY: string" \
 --header "PRE-ACCESS-SIGNATURE: string" \
 --header "PRE-ACCESS-TIMESTAMP: 2026-05-04T09:42:00Z" \
 --header "Idempotency-Key: string" \
 --data '{"market_id":"string","qty":{"units":42,"nanos":42},"client_ref_id":"string"}'
Request examples 
# Headers
PRE-ACCESS-KEY: string
PRE-ACCESS-SIGNATURE: string
PRE-ACCESS-TIMESTAMP: 2026-05-04T09:42:00Z
Idempotency-Key: string

# Payload
{
  "market_id": "string",
  "qty": {
    "units": 42,
    "nanos": 42
  },
  "client_ref_id": "string"
}
Response examples (202) 
{
  "ref_id": "string",
  "client_ref_id": "string"
}
Response examples (409) 
{
  "error_code": "string",
  "message": "string",
  "details": {}
}
Response examples (422) 
{
  "error_code": "string",
  "message": "string",
  "details": {}
}
Response examples (503) 
{
  "error_code": "string",
  "message": "string",
  "details": {}
}