> ## Documentation Index
> Fetch the complete documentation index at: https://docs.olympex.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Get a DCA strategy
> Read one DCA strategy by ID: its tokens, budget, schedule and status.
`GET /dca-order/strategies/{id}` returns one strategy created with your API key: its tokens, budget, schedule, price bounds and `status`. The response doesn't include the strategy's orders. Get them with [`GET /dca-order/strategies/{id}/orders`](/api-reference/dca/list-dca-strategy-orders), or list your strategies together with their orders with [`GET /dca-order/strategies`](/api-reference/dca/list-dca-strategies).
Signed endpoint with no request body. Send `Content-Type: application/json` and the four headers `x-api-key-id`, `x-value-info`, `x-passphrase` and `x-signature` described in [Sign requests](/authentication/sign-requests), signed over the method, the path and the empty string (`bodyHash` `47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU`). `id` is the strategy ID that `POST /dca-order/strategies` returned. The response has no `orders` array. `404 NOT_FOUND` "DCA strategy not found" means the ID doesn't exist or belongs to another API key.
## Strategy status
| `status` | Meaning |
| - | - |
| `active` | Running. Olympex places the orders one `frequency` apart. |
| `cancelled` | Stopped with [`PATCH /dca-order/strategies/{id}`](/api-reference/dca/update-dca-strategy). Cancelling can't be undone. |
| `finished` | Every order ran. |
| `pending` | Reserved for Olympex. |
Treat any other value as not final. The strategy doesn't report its own progress: [list its orders](/api-reference/dca/list-dca-strategy-orders) and read the `status` of each one.
## Fields
* `totalAmount`, `slippage`, `minPrice` and `maxPrice` are JSON numbers in human-readable units, as sent. `minPrice` and `maxPrice` are absent when the strategy has no bounds, and `slippage` is `0` when the strategy was created without it.
* Addresses come back exactly as they were sent. `pair` and `signature` aren't returned.
* `createdAt` and `updatedAt` are ISO 8601 timestamps in UTC.
## Not found
`404 NOT_FOUND` with the message "DCA strategy not found" means that no strategy with this ID belongs to your API key: the ID doesn't exist, or another API key created it. Each API key sees only its own strategies.
```bash cURL theme={null}
# Read one DCA strategy by ID.
# Needs openssl, curl and OLYMPEX_API_KEY_ID, OLYMPEX_SECRET_KEY, OLYMPEX_PASSPHRASE.
STRATEGY_ID='320263ca-2f38-4349-b641-a23aed2ff847'
METHOD=GET
ENDPOINT="/dca-order/strategies/$STRATEGY_ID"
QUERY=''
BODY='' # GET has no body: the signature covers the empty string
TS="${OLYMPEX_TIMESTAMP:-$(date +%s)}"
NONCE="${OLYMPEX_NONCE:-$(openssl rand -hex 12)}"
BODY_HASH="$(printf '%s' "$BODY" | openssl dgst -sha256 -binary | openssl base64 -A | tr '+/' '-_' | tr -d '=')"
VALUE_INFO="$(printf '%s\n%s\n%s' "$TS" "$NONCE" "$BODY_HASH")"
MESSAGE="$(printf 'OLPX-HMAC-SHA256-V2\n%s\n%s\n%s\n%s\n%s\n%s' "$TS" "$NONCE" "$METHOD" "/api/v1$ENDPOINT" "$QUERY" "$BODY_HASH")"
curl -sS -X "$METHOD" "https://api-rest.olympex.io/api/v1$ENDPOINT${QUERY:+?$QUERY}" \
-H "content-type: application/json" \
-H "x-api-key-id: $OLYMPEX_API_KEY_ID" \
-H "x-value-info: $(printf '%s' "$VALUE_INFO" | openssl base64 -A)" \
-H "x-passphrase: $OLYMPEX_PASSPHRASE" \
-H "x-signature: $(printf '%s' "$MESSAGE" | openssl dgst -sha256 -hmac "$OLYMPEX_SECRET_KEY" -binary | od -An -v -tx1 | tr -d ' \n')"
```
```ts TypeScript theme={null}
import { olympexRequest } from "./sign-request.ts"; // /authentication/sign-requests
type DcaStrategy = { id: string; status: string; iterations: number; frequency: number };
const strategyId = "320263ca-2f38-4349-b641-a23aed2ff847";
const strategy = await olympexRequest("GET", `/dca-order/strategies/${strategyId}`);
if (strategy.status === "active") {
// The strategy itself carries no orders: fetch them separately.
const orders = await olympexRequest<{ status: string }[]>("GET", `/dca-order/strategies/${strategyId}/orders`);
console.log(`${orders.length} of ${strategy.iterations} orders created so far`);
} else {
console.log(`Strategy is ${strategy.status}`);
}
```
```python Python theme={null}
from sign_request import olympex_request # /authentication/sign-requests
strategy_id = "320263ca-2f38-4349-b641-a23aed2ff847"
strategy = olympex_request("GET", f"/dca-order/strategies/{strategy_id}")
if strategy["status"] == "active":
# The strategy itself carries no orders: fetch them separately.
orders = olympex_request("GET", f"/dca-order/strategies/{strategy_id}/orders")
print(f'{len(orders)} of {strategy["iterations"]} orders created so far')
else:
print(f'Strategy is {strategy["status"]}')
```
```json 200 theme={null}
{
"success": true,
"data": {
"id": "320263ca-2f38-4349-b641-a23aed2ff847",
"accountTo": "0x1E67cb01969D79B2B895179e4A07D24a839dBb52",
"chainIdFrom": 137,
"chainIdTo": 137,
"tokenAddressFrom": "0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359",
"tokenAddressTo": "0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619",
"tokenSymbolFrom": "USDC",
"tokenSymbolTo": "WETH",
"totalAmount": 100,
"frequency": 86400,
"iterations": 10,
"slippage": 1,
"status": "active",
"createdAt": "2026-09-29T13:48:57.833Z",
"updatedAt": "2026-09-29T13:48:57.833Z"
},
"meta": {
"requestId": "Eds3sh1MIAMEPeg=",
"version": "v1",
"accountType": "integrator",
"apiKeyId": "00000000-0000-4000-8000-000000000000"
}
}
```
```json 404 theme={null}
{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "DCA strategy not found",
"details": []
},
"meta": {
"requestId": "EdjfDjXBIAMEVsA=",
"version": "v1",
"accountType": "integrator",
"apiKeyId": "00000000-0000-4000-8000-000000000000"
}
}
```
```json 403 Gateway theme={null}
{
"message": "Forbidden"
}
```
## OpenAPI
````yaml api-reference/openapi.json GET /dca-order/strategies/{id}
openapi: 3.0.3
info:
title: Olympex REST API
version: 1.0.0
description: >-
Aggregated swap quotes and transactions, limit orders and DCA strategies on
EVM chains, plus the chain and token catalog. Every response uses the same
envelope, except the API gateway's own responses (`{"message": …}`): `401`
or `403` when the signed headers are missing or rejected, `429` when it
throttles requests, and `500` or `503` when it can't get a response from
Olympex in time. Chain IDs are integers on every endpoint. Signed endpoints
require four signed headers; see [Sign
requests](https://docs.olympex.io/authentication/sign-requests).
termsOfService: https://docs.olympex.io/legal/terms
contact:
name: Olympex partnerships
email: partners@olympex.io
url: https://docs.olympex.io
servers:
- url: https://api-rest.olympex.io/api/v1
description: Olympex REST API v1
security: []
tags:
- name: Accounts
description: Create API credentials.
- name: Quotes
description: Aggregated single-chain and cross-chain quotes.
- name: Swap
description: Unsigned transaction calldata for a quoted route.
- name: TxStatus
description: Track a cross-chain transfer after you broadcast it.
- name: Transactions
description: On-chain status of a transaction you broadcast.
- name: Chains and tokens
description: Enabled chains and the tokens listed on each.
- name: Limit orders
description: Orders that Olympex executes when the market reaches your price.
- name: DCA
description: Strategies that buy a token in equal orders over time.
- name: Docs
description: Machine-readable API description.
paths:
/dca-order/strategies/{id}:
get:
tags:
- DCA
summary: Get a DCA strategy
description: >-
Returns one strategy created with your API key, without its orders. To
get the orders, use `GET /dca-order/strategies/{id}/orders`. No request
body: sign the empty string.
operationId: getDcaStrategy
parameters:
- name: id
in: path
required: true
description: Strategy ID, as returned when it was created.
schema:
type: string
example: 320263ca-2f38-4349-b641-a23aed2ff847
responses:
'200':
description: The strategy.
content:
application/json:
schema:
$ref: '#/components/schemas/DcaStrategySuccessResponse'
example:
success: true
data:
id: 320263ca-2f38-4349-b641-a23aed2ff847
accountTo: '0x1E67cb01969D79B2B895179e4A07D24a839dBb52'
chainIdFrom: 137
chainIdTo: 137
tokenAddressFrom: '0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359'
tokenAddressTo: '0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619'
tokenSymbolFrom: USDC
tokenSymbolTo: WETH
totalAmount: 100
frequency: 86400
iterations: 10
slippage: 1
status: active
createdAt: '2026-09-29T13:48:57.833Z'
updatedAt: '2026-09-29T13:48:57.833Z'
meta:
requestId: Eds3sh1MIAMEPeg=
version: v1
accountType: integrator
apiKeyId: 00000000-0000-4000-8000-000000000000
'401':
description: >-
A signing header is missing. The gateway answers with
`{"message":"Unauthorized"}` before your request reaches Olympex;
the handler answers with the `UNAUTHORIZED` envelope when the
authorizer context is missing.
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/GatewayError'
- $ref: '#/components/schemas/ErrorResponse'
example:
message: Unauthorized
'403':
description: >-
Authentication failed: unknown key, wrong passphrase, invalid
signature, timestamp outside the ±300 s window, reused nonce, or
inactive account (gateway `{"message":"Forbidden"}`). The handler
answers with the `FORBIDDEN` envelope when the signed `bodyHash` is
not the hash of an empty body.
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/GatewayError'
- $ref: '#/components/schemas/ErrorResponse'
examples:
gateway:
summary: Signature rejected by the gateway
value:
message: Forbidden
bodyHash:
summary: Body does not match the signed hash
value:
success: false
error:
code: FORBIDDEN
message: Invalid body hash
details: []
meta:
requestId: ENXGDhsXIAMEMEw=
version: v1
accountType: integrator
apiKeyId: 00000000-0000-4000-8000-000000000000
'404':
description: >-
No DCA strategy with this ID belongs to your API key (`NOT_FOUND`).
IDs of other API keys return the same error. An unknown path or
method also returns `NOT_FOUND`, with a message that names the
method and path.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
notFound:
summary: Unknown DCA strategy
value:
success: false
error:
code: NOT_FOUND
message: DCA strategy not found
details: []
meta:
requestId: EdjfDjXBIAMEVsA=
version: v1
accountType: integrator
apiKeyId: 00000000-0000-4000-8000-000000000000
unknownRoute:
summary: Unknown path or method
value:
success: false
error:
code: NOT_FOUND
message: No route for GET /api/v1/quote
details: []
meta:
requestId: E7edogG4IAMEPYA=
version: v1
'500':
description: >-
Olympex could not complete the request (`INTERNAL_ERROR`), or the
gateway could not get a response (`{"message":"Internal Server
Error"}`), which also happens on the first request after a quiet
period. Retry with backoff.
content:
application/json:
schema:
oneOf:
- $ref: '#/components/schemas/ErrorResponse'
- $ref: '#/components/schemas/GatewayError'
example:
success: false
error:
code: INTERNAL_ERROR
message: Unexpected internal error
details: []
meta:
requestId: Edkf0j8MIAMEZsA=
version: v1
accountType: integrator
apiKeyId: 00000000-0000-4000-8000-000000000000
'503':
description: >-
The gateway could not get a response in time (the integration
timeout is about 30 seconds) or the service is briefly unavailable.
Returned by the gateway. Retry with backoff.
content:
application/json:
schema:
$ref: '#/components/schemas/GatewayError'
example:
message: Service Unavailable
security:
- ApiKeyId: []
ValueInfo: []
Passphrase: []
Signature: []
components:
schemas:
DcaStrategySuccessResponse:
type: object
required:
- success
- data
- meta
properties:
success:
type: boolean
enum:
- true
data:
$ref: '#/components/schemas/DcaStrategy'
meta:
$ref: '#/components/schemas/Meta'
GatewayError:
type: object
required:
- message
description: >-
Returned by the API gateway itself: `401` or `403` when the signed
headers are missing or rejected, `429` when it throttles requests, and
`500` or `503` when it can't get a response from Olympex in time. It has
no `success`, `error` or `meta`.
properties:
message:
type: string
example: Forbidden
ErrorResponse:
type: object
required:
- success
- error
- meta
properties:
success:
type: boolean
enum:
- false
error:
$ref: '#/components/schemas/ErrorBody'
meta:
$ref: '#/components/schemas/Meta'
DcaStrategy:
type: object
description: A DCA strategy. Olympex can add fields; ignore the ones you don't use.
required:
- id
- accountTo
- chainIdFrom
- chainIdTo
- tokenAddressFrom
- tokenAddressTo
- tokenSymbolFrom
- tokenSymbolTo
- totalAmount
- frequency
- iterations
- slippage
- status
- createdAt
- updatedAt
properties:
id:
type: string
format: uuid
description: Strategy ID.
accountTo:
type: string
description: Maker wallet, as sent.
chainIdFrom:
type: integer
description: Chain ID.
chainIdTo:
type: integer
description: Chain ID. Equal to `chainIdFrom`.
tokenAddressFrom:
type: string
description: Token sold, as sent.
tokenAddressTo:
type: string
description: Token bought, as sent.
tokenSymbolFrom:
type: string
description: Symbol of the token sold.
tokenSymbolTo:
type: string
description: Symbol of the token bought.
totalAmount:
type: number
description: Total amount of the token sold across all orders, human-readable.
frequency:
type: integer
description: Seconds between orders.
iterations:
type: integer
description: Number of orders.
slippage:
type: number
description: Maximum slippage per order, in percent. `0` when it wasn't sent.
minPrice:
type: number
description: Lower price bound. Absent when not set.
maxPrice:
type: number
description: Upper price bound. Absent when not set.
status:
type: string
enum:
- pending
- active
- cancelled
- finished
description: >-
`active`: running. `cancelled`: stopped by you. `finished`: every
order ran. `pending` is reserved. Treat any other value as not
final.
createdAt:
type: string
format: date-time
description: When the strategy was created (ISO 8601, UTC).
updatedAt:
type: string
format: date-time
description: When the strategy last changed (ISO 8601, UTC).
deletedAt:
type: string
format: date-time
description: Absent unless the strategy was deleted by Olympex.
Meta:
type: object
required:
- requestId
- version
properties:
requestId:
type: string
description: Unique ID for this request. Include it when you contact support.
version:
type: string
default: v1
description: API version that served the request.
accountType:
type: string
description: >-
Account type resolved by the signature check, for example
`integrator`. Present when the request was authenticated; absent on
the `404` for an unknown path or method.
apiKeyId:
type: string
format: uuid
description: >-
The API key ID that signed the request. Present when the request was
authenticated; absent on the `404` for an unknown path or method.
ErrorBody:
type: object
required:
- code
- message
- details
properties:
code:
type: string
description: >-
Machine-readable error code. `VALIDATION_ERROR` (400),
`UNAUTHORIZED` (401), `FORBIDDEN` (403), `NOT_FOUND` (404, also for
an unknown path or method), `CONFLICT` (409), `NO_ROUTE` (422), and
for 500: `QUOTE_ERROR`, `CROSS_CHAIN_QUOTE_ERROR`, `SWAP_ERROR`,
`CROSS_CHAIN_SWAP_ERROR`, `SUPPORT_CHAIN_ERROR`,
`ENABLED_CHAINS_ERROR`, `TOKEN_LIST_ERROR`, `TX_STATUS_ERROR`,
`INTERNAL_ERROR`. Olympex can add codes: handle an unknown code by
its HTTP status.
message:
type: string
description: Human-readable summary. Don't parse it.
details:
type: array
items:
$ref: '#/components/schemas/ErrorDetail'
ErrorDetail:
type: object
additionalProperties: true
description: >-
Validation errors carry `field` and `message`; other errors carry
`message` only.
properties:
field:
type: string
description: >-
Dot path of the invalid field, for example `params.chainId`. Empty
for the top level.
message:
type: string
securitySchemes:
ApiKeyId:
type: apiKey
in: header
name: x-api-key-id
description: >-
Your API key ID (UUID). See [Sign
requests](https://docs.olympex.io/authentication/sign-requests).
ValueInfo:
type: apiKey
in: header
name: x-value-info
description: >-
Base64 of `timestamp + "\n" + nonce + "\n" + bodyHash`, where
`timestamp` is Unix seconds, `nonce` is 24 new hexadecimal characters
and `bodyHash` is the unpadded base64url SHA-256 of the canonical body.
Passphrase:
type: apiKey
in: header
name: x-passphrase
description: Your account passphrase. Treat it like the secret key.
Signature:
type: apiKey
in: header
name: x-signature
description: >-
Lowercase hex HMAC-SHA256 (signature v2), keyed with your secret key
string (UTF-8, not decoded), of seven lines joined with `\n`, with no
trailing newline: `OLPX-HMAC-SHA256-V2`, `timestamp`, `nonce`, the
uppercase method, `path`, `canonicalQuery` and `bodyHash`. `path` is the
request path including `/api/v1`, without the query string, for example
`/api/v1/limit-order/`. `canonicalQuery` is the query parameters
decoded (`+` is a space), sorted by key and then by value, re-encoded
per RFC 3986 and joined with `&`, or the empty string when there is no
query. Headers signed for one request are rejected on any other. See
[Sign requests](https://docs.olympex.io/authentication/sign-requests).
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.