Skip to content

Overview

Paros runs strategies against your own custody accounts. This is the API you use to configure accounts, approve venue access, define strategies, and read what happened.

Everything goes through one REST API on paros-server. Salt sits behind it and holds the keys; the API is what you call, and custody is what signs.

Open the diagram full screen ↗

Base URL: https://app.paros.xyz Interactive reference: https://app.paros.xyz/api-docs/

The trailing slash on the reference matters. Without it the path returns 404.

Start here

If you are integrating for the first time, read these in order:

  1. Authentication — get a token, learn which credential each call needs.
  2. Hyperliquid Connection — approve the agent that trades on your behalf.
  3. Trading Call Flow — the exact order of calls from new account to live trading.

Then the reference material:

Response format

Every response is a JSON envelope.

{ "success": true, "data": {} }

{ "success": false, "error": "Validation failed", "details": [] }

On a 400, details lists each failing field with its path and message.

Common errors

These can come back from any endpoint.

Status Meaning
400 Validation failed. Read details
401 Missing or expired token. Refresh and retry
403 Your role cannot perform this. Ownership or signing policy refused the call
419 The Salt token expired. Re-authenticate and retry
429 Rate limited
500 Server error. If this is agent approval, check the account is funded
502 The custody service is unavailable
504 The custody service or an RPC timed out

A note on scope

This documentation covers the public API: the operations you need to run your own account. Staff operations, custody-organisation administration, and internal event intake are not documented here and are not part of your integration surface.