> For the complete documentation index, see [llms.txt](https://docs.reya.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reya.xyz/developers/changelog/changelog-archive.md).

# Changelog archive (devnet1)

{% hint style="info" %}
These entries come from the devnet1 order-book changelog, kept as published before the mainnet launch on 28 September 2026. They describe changes on devnet1 leading up to launch; links point to the current pages. For changes since launch, see the [Changelog](https://docs.reya.xyz/developers/changelog/changelog.md).
{% endhint %}

Tags follow the [legend](https://docs.reya.xyz/developers/changelog/changelog.md#legend) on the main changelog.

## Log

### 2026-09-21 — All orders on `orderChanges` (API [3.6.1](https://github.com/Reya-Labs/reya-api-specs/tree/8bbf158edcabf46751a1c80d7146a1364fedabc0))

`[WS-Info]` **Changed.** All orders publish state changes on `orderChanges`.

### API 3.6.0 — transport outcomes

Canonical contract: [API 3.6.0 specification](https://github.com/Reya-Labs/reya-api-specs/tree/4431a2d7d9e493dde355d3de046ab8849d9c6e30).

REST and WebSocket order entry distinguish requests that were not accepted from operations that may have been applied. `SERVICE_UNAVAILABLE_ERROR` replaces `UNAVAILABLE_MATCHING_ENGINE_ERROR` and `UNAVAILABLE_ACCOUNT_OWNER_ERROR` for failures before acceptance; retry with a fresh nonce after backing off. `ORDER_OUTCOME_UNKNOWN_ERROR` requires reconciliation first. The same rules apply across all five order operations. REST uses the originating request for correlation; WebSocket responses retain the envelope `id`. Error bodies do not add nonce or clientOrderId. `NO_PRICES_FOUND_FOR_SYMBOL_ERROR` is removed from the error-code enum.

Update exhaustive error-code handling and follow [Handling ambiguous outcomes](https://docs.reya.xyz/developers/connectivity/handling-ambiguous-outcomes.md). Before API 3.6.0, the unavailable code can also mean an unknown outcome; reconcile before retrying.

### Agreed launch limits — account, connection and IP allowances

`[REST]` `[WS-OrderEntry]` `[WS-Info]` **Launch policy.** Values agreed on 19 September 2026.

* Account-operation budgets are shared across REST and WebSocket Order Entry, with separate allowances for create/modify, single cancellation, bulk cancellation and countdown control.
* Market Maker resting-order caps are **1,500 per account**, **300 per market** and **$50 million gross notional**. Standard caps remain 200, 50 and $250,000.
* Per-IP edge limits are **2,000 REST trading requests/minute**, **1,500 other REST requests/minute** and **300 new WebSocket connection attempts/minute shared across all Order Entry and Info hostnames**. All REST trading operations, including cancellations and countdown refreshes, share the trading bucket. Exceeding an edge limit blocks its traffic scope for **60 seconds**, with no `Retry-After` header. This block was first announced as 10 seconds and was changed to 60 seconds on 25 September 2026. The existing portfolio limit remains **200 requests per 10 seconds**.
* Simultaneous WebSocket caps are **20 total Order Entry** and **100 total Info connections per IP**, shared across all clients using that IP. Message limits and account budgets apply independently.

See [Rate Limits](https://docs.reya.xyz/developers/connectivity/rate-limits.md) for the complete tables, scope and recovery guidance. The account error codes and optional `retryAfterMs` are part of the API 3.6.0 contract.

### Upcoming — perp summary oracle price uses the Stork spot feed

`MarketSummary.oraclePrice` changes source from `<BASE>USDMARK` to the underlying's **spot index** feed `<BASE>USD`, for example `ETHUSD`. The field name and response shape are unchanged. The value is divided by `USDCUSD`, using the same quote conversion and feed family as spot summaries. Consumers tracking the old CEX-mark series should account for this source change.

The change applies to REST `GET /v2/perpMarkets/summary` and `GET /v2/perpMarket/{symbol}/summary` and both matching WS channels. Missing or stale spot ticks omit the field; there is no silent MARK fallback. `markPrice` and collateral pricing are unchanged. This entry describes the pending implementation, not a completed deployment.

### 2026-09-17 — Cumulative average fill price (API 3.5.4)

`[REST]` `[WS-OrderEntry]` `[WS-Info]` **Added.** The optional decimal-string `avgFillPx` field reports the quantity-weighted average execution price across all maker and taker fills of an order, excluding fees.

The field is included on REST and WebSocket Order Entry create/modify responses, WebSocket Info `orderChanges` updates and subscription snapshots, and REST `openOrders` and `orderHistory`. It corresponds to `cumQty`, is omitted before the first fill, and is preserved across amendments and cancellation. Values are rounded half-up to at most 9 decimal places. Individual executions continue to report their own `price`.

This is an additive response-field change. See [Average fill price](https://docs.reya.xyz/developers/order-entry/order-lifecycle.md#average-fill-price) for examples and the immutable [API 3.5.4 canonical spec](https://github.com/Reya-Labs/reya-api-specs/tree/a4503404027f36e863be13ac491a85f80ec21394) for the contract.

### 2026-09-15 — September 28 launch: required API migration

`[REST]` `[WS-OrderEntry]` `[WS-Info]` `[On-chain]` **Breaking migration notice.** Reya v2 launches on **September 28, 2026**. Existing spot and perpetual API integrations must migrate to the perpOB contract currently available on devnet. Production API base URLs remain the same; individual endpoint paths change. The exact cutover time will be announced.

Start testing on devnet1 now. At cutover, use the production endpoints and production signing configuration with the updated client. Follow the launch migration checklist (retired after launch) and V2 Migration Reference (retired after launch); the devnet configuration is for testing and must not be reused for production signing.

### 2026-09-15 — Spec downloads follow the deployed API

`[REST]` `[WS-OrderEntry]` `[WS-Info]` **Documentation.** Spec download links now point to the live devnet1 endpoints. Duplicate YAML snapshots have been removed from this docs repository; use the immutable canonical spec links in release entries for historical versions. GitBook continues importing its generated REST reference from the API endpoint.

### 2026-09-14 — Trigger requests omit fixed Boolean fields (API 3.5.2)

`[REST]` `[WS-OrderEntry]` **Breaking.** Effective date: September 14, 2026 (devnet1).

For `STOP_LOSS` and `TAKE_PROFIT`, omit `reduceOnly` and `postOnly` on both create and modify. Supplying either field, including `false`, returns `INPUT_VALIDATION_ERROR`. Both signed EIP-712 values remain `false`; the signature type and hashing are unchanged. LIMIT rules are unchanged.

Update SDKs and remove these arguments from trigger callers at cutover. `timeInForce` remains required; GTT requires `expiresAfter`, while GTC/IOC omit it. Trigger modifications still change only the two prices and restate the original lifetime.

The deployed contract for this release is API **3.5.2**, preserved in the [canonical spec source](https://github.com/Reya-Labs/reya-api-specs/tree/4fafae7d19076e8d31811930000a78d842758d9f). The [Python SDK source snapshot](https://github.com/Reya-Labs/reya-python-sdk/tree/37450ccb2babc99398d1ac1290d48860a9a2e2fa) is **3.5.2.0**; install it using the pinned commit in [Onboarding](https://docs.reya.xyz/developers/getting-started/onboarding.md#install-the-pinned-python-sdk). The published npm SDK is `@reyaxyz/sdk@0.146.5-perpob.257`, with `@reyaxyz/api-v2-sdk@0.303.1-perpob.257`; the devnet UI uses this release.

### 2026-09-12 — Devnet documentation refresh (API 3.4.0)

*Verified against the public devnet1 APIs and deployment configuration on September 12. This records observed behavior, not a newly announced cutover.*

* The API contracts were verified against the deployed **3.4.0** endpoints; the [canonical source](https://github.com/Reya-Labs/reya-api-specs/tree/c1bf8fee0464f8816f81edf45031e9584cd0223e) preserves this version. The onboarding SDK is pinned to **3.4.0.0** at immutable commit [`c2d553d8`](https://github.com/Reya-Labs/reya-python-sdk/tree/c2d553d81e45eeff37f46fdff4e6ae01624fe20c).
* The regular fee schedule is now reported as **3.0–2.0 bp taker, 0 maker** by `feeTiers`; the earlier 4 bp configuration warning is removed.
* [Contract Addresses](https://docs.reya.xyz/developers/reference/contract-addresses.md) now identifies devnet1's own pool, srUSD, oracle manager and oracle adapters instead of Cronos values.
* The trigger Boolean-field omission change is pending; current 3.4.0 trigger examples remain unchanged until the coordinated API/SDK cutover.

### 2026-09-11 — Documentation alignment: order-history recording eligibility

*Verified against the devnet1 deployment on September 11; this records the current behavior, not a new rollout date. The endpoint and response shape are unchanged.*

#### Changed — \[REST] account history recording

The automatic exclusion threshold is now **more than 100 order-change events per account in a fixed matching-engine event-time minute**, replacing the previously documented 200-event threshold. Recording resumes after **two consecutive completed minutes below 50 events**, including idle minutes. Excluded events are not backfilled. Trading and live `orderChanges` are unaffected.

Applications needing a complete order timeline must continue recording the live stream and handling gaps. See [retention and recording eligibility](https://docs.reya.xyz/developers/api-reference/rest-api-reference.md#retention-and-recording-eligibility) for the current rules.

### 2026-09-11 — Documentation alignment: live triggers, pre-trade risk and bounded depth

*These behaviours are already deployed on devnet1. This entry corrects the integration documentation as of September 11; it is not a new rollout date or advance notice. Historical entries below describe their original release state. The current API serves spec 3.3.0.*

#### 🔴 BREAKING — \[REST] · \[WS-OrderEntry] SL/TP firing and chosen time-in-force

`timeInForce` is required on **every** create, including `STOP_LOSS` / `TAKE_PROFIT`. Send and sign IOC/GTC/GTT to select the order the stop becomes when it fires against the mark price. GTT requires `expiresAfter`; GTC/IOC omit it. A GTT trigger and child share one immutable expiry and both stop early to allow time for settlement. `limitPx` must satisfy the market's permitted trigger-price band. The EIP-712 envelope and full-position sentinel are unchanged.

Only armed triggers can be modified. Fired children are cancel-only. Firing cancels the OCO sibling even when nothing fills; a risk or position refusal before firing cancels both legs. Protective firing can cancel the account's own resting makers to avoid self-trading. Monitor these outcomes and re-arm protection deliberately; see [Trigger Orders (SL/TP)](https://docs.reya.xyz/developers/order-entry/trigger-orders.md).

#### Added — \[REST] · \[WS-Info] protective-order lifecycle fields and reasons

`triggered` distinguishes armed triggers from fired children on `openOrders` and live `orderChanges`. It is always omitted on `orderHistory`, where absence means unknown. Handle `OCO_SIBLING_FIRED`, `PROTECTIVE_SELF_TRADE_SWEEP`, `POSITION_CLOSED`, and `RISK_REJECTED`. Cancellation reason messages are fixed explanations, not individual risk-check diagnostics.

#### 🔴 BREAKING — \[REST] · \[WS-OrderEntry] · \[WS-Info] pre-trade risk is enforced

Reya performs pre-trade risk checks, taking pending fills into account. Fills must also pass settlement checks. Interactive admission failures are errors; an already-resting maker that fails at match time is cancelled with `RISK_CANCELLED` and matching continues through the remaining book. The former "settlement-only margin checks" description is obsolete. See [Margin System](https://docs.reya.xyz/developers/risk/margin-system.md#pre-trade-risk-checks).

#### 🔴 BREAKING — \[REST] · \[WS-Info] bounded public depth

REST depth defaults to **100 levels per side** and caps `limit` at **1,000**. WS snapshots and updates maintain the **top 100 per side**, including zero-quantity removals for levels leaving that view and full quantities for levels entering it. These are bounded views, not full-book feeds. See [REST OpenAPI contract](https://github.com/Reya-Labs/reya-api-specs/blob/d256f22283346efc493e42fa5dce44e5f468bd17/openapi-trading-v2.yaml) and [WS Info](https://docs.reya.xyz/developers/api-reference/websocket-api-reference.md).

#### Fixed — API bundles and Python SDK version

This release updated the REST and WebSocket contracts to **3.3.0** from immutable spec commit [`d256f222`](https://github.com/Reya-Labs/reya-api-specs/tree/d256f22283346efc493e42fa5dce44e5f468bd17), replacing the stale 3.0.23 downloads and navigation links.

Python examples pin SDK source commit [`259ed1be`](https://github.com/Reya-Labs/reya-python-sdk/tree/259ed1be3ba4d6f557b5024db0bd61fdc9be7429), whose `specs` submodule uses that same API commit. Its package metadata and generated client version are **3.3.0.0** (API spec **3.3.0**, SDK build `0`). Follow the [pinned installation steps](https://docs.reya.xyz/developers/getting-started/onboarding.md#install-the-pinned-python-sdk). This is a source snapshot; this documentation update does not publish a PyPI release.

#### Migration checklist

1. For this release, regenerate strict models from the pinned 3.3.0 canonical spec source above; older 3.0.23 bundles predate chosen-TIF triggers and bounded WS depth.
2. Update trigger create/signing and modify rules together; keep JSON `qty` omitted.
3. Track armed versus fired orders, OCO cancellations and risk outcomes before submitting replacement orders or re-arming protection.
4. Maintain the WS top-100 view using complete updates; use REST for independent deeper snapshots.

### 2026-09-10 — Wallet transfer history, the account ledger (API 3.4.1)

*Additive, non-breaking. Targets API* [*`3.4.1`*](https://github.com/Reya-Labs/reya-api-specs/pull/92)*. The `3.4.1` specification tag must be published before this feature is released; no cutover is required because nothing existing changes shape.*

#### Added — \[REST] `GET /v2/wallet/{address}/transfers`

Every movement of collateral into, out of, or between a wallet's accounts as it settles on-chain — deposits, withdrawals, transfers, pool stakes and unstakes, the token legs of spot trades and auto-exchanges, perp fees and rebates, liquidation penalties — as one `Transfer` entry per account side, newest first, signed from the account's view and labelled by `TransferType`. Perp fee entries link to executions through `fillId` and `symbol` when available. Paged by an opaque cursor (`meta.nextCursor` → `cursor`, `CursorPaginationMeta`) that visits every entry exactly once; `startTime` / `endTime` filter, `type` filters on a comma-separated list. Zero-amount legs are never returned. Net deposits only: `netDepositsAfter` is not `realBalance`, and realized PnL, funding and ADL never appear. See [Transfer History (Account Ledger)](https://docs.reya.xyz/developers/executions-and-settlement/transfer-history.md).

#### Added — \[WS-Info] `/v2/wallet/{address}/transfers`

The same entries live: the `subscribed` acknowledgement carries the most recent entries in `contents.data`, then one `channel_data` frame per new entry.

Closed-model consumers must regenerate from `3.4.1` to read the new `Transfer`, `TransferType`, `TransferList` and `CursorPaginationMeta` schemas. New `TransferType` values may be added; treat an unfamiliar value as `OTHER`.

### 2026-09-02 — Fee breakdown on perp executions (API 3.3.0)

*Additive, non-breaking. Ships with API* [*`3.3.0`*](https://github.com/Reya-Labs/reya-api-specs/releases/tag/3.3.0)*; no cutover date because nothing existing changes shape.*

#### Added — \[REST]·\[WS-Info] `PerpExecution` fee component fields

Every perp fill under the current fee model now exposes the four settlement buckets its gross `takerFee` was split into: `protocolFeeCredit`, `referrerFeeCredit`, `takerRebateCredit`, and `poolFeeCredit` (all rUSD, all optional). Whenever they are present, `takerFee` equals their exact sum. REST `GET /v2/wallet/{address}/perpExecutions`, `GET /v2/market/{symbol}/perpExecutions` and the WS `perpExecutions` channels carry identical values. Legacy executions omit all four; they are never synthesized. `takerRebateCredit` is part of the gross taker debit, not a net credit back to the taker. See [Executions & Trade History](https://docs.reya.xyz/developers/executions-and-settlement/executions-and-trade-history.md).

Closed-model consumers (generated SDKs, strict schema validators) must regenerate from `3.3.0` to read the new fields; open-model consumers are unaffected.

#### Fixed — \[REST]·\[WS-Info] `makerFee` presence wording

The `PerpExecution.makerFee` description previously said the field was absent for "legacy V2" executions, which was backwards. It is present only on legacy executions that recorded a maker debit or credit, and absent on every fill under the current fee model as well as `ADL` and `MARKET_CLOSE`. Runtime behaviour is unchanged; the contract text now matches it.

### 2026-09-01 — CEX-mark price on perp summaries, book mid on spot summaries (API 3.2.0)

*Additive, non-breaking. Ships with API* [*`3.2.0`*](https://github.com/Reya-Labs/reya-api-specs/releases/tag/3.2.0)*; no cutover date because nothing existing changes shape or meaning.*

#### Added — \[REST]·\[WS-Info] `MarketSummary.oraclePrice` (perp CEX-mark feed)

Perp market summaries now carry `oraclePrice`: Stork's **CEX-mark feed** for the market's underlying (`<ASSET>USDMARK`), quoted in the market's quote currency. Nothing of the sort was on the perp summary before this release.

**Source update:** the entry above records the original 3.2.0 source. The upcoming source change above replaces it with the Stork spot index feed; the API field remains `oraclePrice`. `markPrice` remains the ME valuation price used for PnL, margin and liquidations.

The field is **optional and omitted** whenever a fresh value cannot be produced — most commonly a tick older than 60 seconds, but also a missing cross-rate, a market with no Stork feed, or unavailable current summary data. It is never republished stale and never defaulted: absent means "no fresh value", not zero.

REST `GET /v2/perpMarkets/summary`, `GET /v2/perpMarket/{symbol}/summary` and the WS `/v2/perpMarkets/summary` and `/v2/perpMarket/{symbol}/summary` channels carry identical values.

Closed-model consumers (generated SDKs, strict schema validators) must regenerate from `3.2.0` **or later** to read this field; open-model consumers are unaffected.

#### Added — \[REST]·\[WS-Info] `SpotMarketSummary.throttledMidPrice` (spot book mid)

Spot market summaries now carry `throttledMidPrice`, the throttled order-book mid — the same field and semantics the perp summary already exposed. Spot summaries previously had no order-book mid at all.

It is **optional and omitted** when no mid can be produced: an empty or one-sided book, or a degraded market-data read. As above, absent is not zero.

REST `GET /v2/spotMarkets/summary`, `GET /v2/spotMarket/{symbol}/summary` and the matching WS channels carry identical values. Closed-model consumers must regenerate from `3.2.0` or later.

#### Fixed — \[REST]·\[WS-Info] `SpotMarketSummary.oraclePrice` description

Our WebSocket reference described this field as a legacy value that "on perp order-book markets currently tracks the mark, not the raw Stork index". That sentence was about the perp `Price` type and was never true of the spot summary: `SpotMarketSummary.oraclePrice` is, and always was, the Stork price for the market's base token, quoted in USDC (also called rUSD on Reya Network). Runtime behaviour is unchanged and the API specification was already correct — only our published reference was wrong.

### 2026-07-21 — Fee and execution model alignment on devnet1

*Effective coordinated devnet1 cutover from API `3.0.13` to* [*`3.0.18`*](https://github.com/Reya-Labs/reya-api-specs/releases/tag/3.0.18)*. This is the cumulative integration migration note: it includes the `3.0.14` legacy-prices contract removal and `3.0.15` trigger-order changes described in the dated entries below, plus the fee-model and execution-enum changes in `3.0.16`–`3.0.18`.*

Reconnect, re-subscribe, and reconcile open orders and executions before resuming normal trading. The EIP-712 domain and type shapes are unchanged by this release; do not change `verifyingContract` unless the [environment configuration](https://docs.reya.xyz/developers/getting-started/environments.md) is separately updated.

#### Added — \[On-chain] self-service devnet1 signer management

Account owners can now add or remove authorised signer wallets through the devnet1 [API Keys page](https://app-devnet-cf.reya.xyz/api-page). Despite the page name, these are on-chain signer permissions rather than issued bearer tokens: generate and retain each keypair yourself, then enter only its public address. Each signer has an independent nonce sequence, while REST and WebSocket Order Entry share the sequence for the same signer.

#### 🔴 BREAKING — \[REST] · \[WS-Info] fee-tier volume changes from 14 to 30 days

`FeeTierParameters.volume14d` is removed and replaced by the required `volume30d` field. Regenerate closed models from API `3.0.18` and update any fee-tier display, alert, or threshold logic to consume `volume30d`.

#### Changed — \[REST] · \[WS-Info] Trading fee economics

Regular tier eligibility now uses trailing 30-day volume. The target taker schedule runs from **3.0 bp below $1M** to **2.0 bp at $5B+**, with a **0** maker fee; that separate taker-rate configuration is not yet applied on devnet1. `feeTiers` currently reports the existing tier-0 configuration as **4.0 bp taker and 4.0 bp maker**, but the maker-rate slot is deprecated and is not applied to new perp fills. Maker rebates are not live yet.

For new perp fills under the current fee model:

* `takerFee` is the taker's total signed rUSD debit, including protocol, referrer, taker-rebate, and pool fee-credit legs.
* `makerFee` is omitted because there is no maker fee or rebate leg. Treat absence as the execution fee contract; do not require a zero-valued field.
* The fee-component breakdown is not exposed by the API in this phase.

Use `feeTiers` for the live tier assignment and taker-rate configuration; do not infer a maker charge on new perp fills from its currently reported `makerFee`. See [Fees](https://docs.reya.xyz/developers/reference/fees.md).

#### 🔴 BREAKING — \[REST] · \[WS-Info] `ExecutionType.DUST` renamed to `MARKET_CLOSE`

`DUST` is removed from the closed `ExecutionType` enum and replaced by `MARKET_CLOSE`. `MARKET_CLOSE` is a **perp-only** terminal execution used to close a residual position when a market is force-closed; it is never emitted for spot executions.

#### Fixed — \[REST] · \[WS-Info] trigger re-prices and single-order cancels

A successful trigger modify now surfaces the new `triggerPx` immediately on `openOrders` and `orderChanges`. Single-order cancellation reliability is also improved. Follow the trigger signing and modify rules in the 2026-07-18 entry below; no additional cancellation payload changes are required.

#### Integration cutover checklist

1. Regenerate API models from `3.0.18` (and upgrade the reference Python SDK when its matching release is published).
2. Replace `volume14d` with `volume30d` and `DUST` with `MARKET_CLOSE` before reconnecting; both are closed-contract changes.
3. Remove `/v2/prices` consumers using the replacements in the 2026-07-08 entry below.
4. For SL/TP, keep JSON `qty` omitted and sign the raw full-position sentinel; apply the trigger-specific modify rules. Do not rely on automatic firing yet.
5. Make `makerFee` optional for perp fills under the current fee model and interpret `takerFee` as the total taker debit.
6. Reconnect and re-subscribe, rebuild open-order state from the snapshot, and reconcile executions before resuming normal trading.

### 2026-07-18 — SL/TP trigger orders natively armed; trigger modify enabled

*API spec `3.0.15`.*

#### 🔴 BREAKING — \[REST] · \[WS-OrderEntry] trigger orders sign the full-position sentinel, not `0`

The EIP-712 `quantity` for a `STOP_LOSS` / `TAKE_PROFIT` is now the **full-position sentinel** `±(2²⁵⁵ − 1)` (`type(int256).max`, raw — not E18-scaled), with the sign matching `isBuy`. The previous facade contract (signed `quantity = 0`) is rejected at signature verification. The JSON wire contract is unchanged — `qty` stays omitted.

**What to do:** if you submit trigger orders, update your signer to encode the sentinel (or sign through the reference Python SDK, which derives it from `is_buy`). `LIMIT` signing is unchanged. See [Trigger Orders (SL/TP)](https://docs.reya.xyz/developers/order-entry/trigger-orders.md#signing-the-full-position-sentinel).

#### Changed — \[REST] · \[WS-Info] trigger orders are natively armed and tracked

`STOP_LOSS` / `TAKE_PROFIT` orders are no longer a preview facade: the matching engine durably arms them (surviving restarts), surfaces them as `OPEN` on `openOrders` / `orderChanges` / `orderHistory`, retains them on Cancel-on-Disconnect, and clears them on a user `cancelAll`. At most **one stop-loss and one take-profit** can be armed per account per market (a second same-type trigger is rejected). Triggers remain perp-only. **Execution at `triggerPx` is still not live** — see [Trigger Orders (SL/TP)](https://docs.reya.xyz/developers/order-entry/trigger-orders.md).

#### Added — \[REST] · \[WS-OrderEntry] `modifyOrder` accepts armed triggers

An armed trigger can be re-priced **in place** (keeping its `orderId`): the modifiable fields for a trigger modify are **`limitPx` and `triggerPx` only** (`triggerPx` required), with `qty` / `expiresAfter` omitted and the values `postOnly: false`, `reduceOnly: false`, and `timeInForce: GTC` sent as immutable full restates. Modify is no longer `LIMIT`-only.

### 2026-07-08 — Legacy prices feed removed from the published devnet1 API

*Spec change from API specs PR* [*#68*](https://github.com/Reya-Labs/reya-api-specs/pull/68)*, tagged `3.0.14`.*

#### 🔴 BREAKING — \[REST] · \[WS-Info] `/v2/prices` removed from the API contract

The legacy mixed market/collateral prices REST endpoints and WebSocket channels are removed from the published V2 spec and generated SDK, together with the `Price` schema. The devnet1 REST compatibility routes currently still respond, but they are outside API `3.0.18` and must not be relied on.

**What to do:** replace each use by intent:

* Asset/collateral Stork oracle prices: use `GET /v2/assetOraclePrices` or WS `/v2/assetOraclePrices` (`AssetOraclePrice { asset, oraclePrice, updatedAt }`).
* Perp valuation/mark price: use market summary `markPrice` from `GET /v2/perpMarket/{symbol}/summary` or WS `/v2/perpMarket/{symbol}/summary`.
* Book prices and mid-price data: use `GET /v2/market/{symbol}/depth`, WS `/v2/market/{symbol}/depth`, or summary/depth fields appropriate to the view.

### 2026-07-03 — Retail order history and order-event sequence numbers on devnet1

*API spec `3.0.13`.*

#### Added — \[REST] `GET /v2/wallet/{address}/orderHistory`

The devnet1 API adds a wallet-scoped order-history endpoint. It returns recent order updates newest-first for the wallet's accounts, with optional `startTime` / `endTime` millisecond filters. `sequenceNumber` is present on `orderHistory` REST rows and live `orderChanges` WebSocket event rows as a matching-engine order-event sequence number. Open-order/resting snapshots, including `GET /v2/wallet/{address}/openOrders` and the `orderChanges` subscribe snapshot, omit `sequenceNumber`.

The time filters are inclusive. If you page backward by passing the previous page's `meta.endTime` as the next `endTime`, de-duplicate repeated boundary rows by `Order.sequenceNumber`. If you do not need same-millisecond boundary ties, you can instead page with `endTime = meta.endTime - 1`. Rows also include `firstFillId` / `fillCount` when an order update includes a fill range.

This endpoint is for account-history and support views. History is bounded per account and recording can exclude high-throughput accounts. Applications needing a complete order timeline should persist the [`orderChanges`](https://docs.reya.xyz/developers/api-reference/websocket-api-reference.md) stream and handle gaps explicitly. See the [current retention and recording rules](https://docs.reya.xyz/developers/api-reference/rest-api-reference.md#retention-and-recording-eligibility), which have changed since this release.

#### Added — \[WS-Info] `snapshotSequenceNumber` on `orderChanges` subscribe

The `/v2/wallet/{address}/orderChanges` subscribe ack now includes `contents.snapshotSequenceNumber` alongside `contents.data`, the current open-orders snapshot. Snapshot orders do not include `sequenceNumber`; subsequent `orderChanges` event rows include `sequenceNumber` values greater than `snapshotSequenceNumber`.

**What to do:** retain your live-stream recorder if your application needs a complete order timeline; REST `orderHistory` cannot replace it. For account-history UI or support tooling, regenerate closed SDK/schema bindings against the updated specs and treat `sequenceNumber`, `firstFillId`, and `fillCount` as optional on `Order`.

### 2026-07-02 — Structured execution-bust reasons on devnet1

*API spec `3.0.11`, included in deployed spec `3.0.13`.*

#### 🔴 BREAKING — \[REST] · \[WS-Info] `ExecutionBust.reason` is now a structured object

`ExecutionBust.reason` remains the field that explains why settlement failed, but its wire type changed from a human-readable string to a machine-readable `ExecutionBustReason` object union keyed by `reasonName`. Known contract errors have typed shapes, for example:

```json
{
  "reasonName": "AccountBelowIM",
  "accountId": 1234,
  "delta": "-321",
  "shortfall": "321"
}
```

Decoded but unmodeled contract errors return `{ "reasonName": "<ErrorName>", "args": { ... } }`; legacy already-decoded strings return `{ "reasonName": "DecodedReason", "message": "..." }`; and undecodable bytes return `{ "reasonName": "UnknownReason", "message": "Unknown reason, reach out for support" }`.

**What to do:** regenerate closed SDK/schema bindings and update bust consumers to branch on `reason.reasonName` instead of treating `reason` as a string. You still do not need to ABI-decode raw revert bytes yourself. There is no public `rejectReason` field; the field name is `reason`.

### 2026-07-01 — Feed-reset cancel reason; sharper modify/cancel error codes (devnet1)

#### Added — \[WS-Info] `FEED_RESET` cancel reason on feed re-seeds

`CancelReason` gains `FEED_RESET`. When the order-book feed is re-seeded (e.g. after a matching-engine restart), `orderChanges` delivers a `CANCELLED` update with `cancelReason: FEED_RESET` for every resting order, immediately followed by fresh order events re-publishing your current open orders (same `orderId`s). It is a **resync signal, not a real cancellation** — the orders are still live.

**What to do:** on `cancelReason: FEED_RESET`, discard your cached order view and rebuild from the re-published events (or reconcile via `GET /v2/wallet/{address}/openOrders`) rather than treating the orders as cancelled. Regenerate closed SDK/schema bindings to pick up the new enum value. See [Reconnecting & resyncing](https://docs.reya.xyz/developers/api-reference/websocket-api-reference.md#reconnecting--resyncing).

#### Fixed — \[REST] · \[WS-OrderEntry] `modifyOrder` / `cancelOrder` return branchable codes for halted markets and zero/missing targets

A `modifyOrder` against a halted market now returns `TRADING_HALTED_ERROR` (was the `MODIFY_ORDER_OTHER_ERROR` catch-all), and a zero/sentinel sole target (`orderId` or `clientOrderId` = `"0"`) on `modifyOrder` / `cancelOrder` now returns `INPUT_VALIDATION_ERROR` (was the `*_OTHER_ERROR` catch-all).

**What to do:** nothing required — the free-text `message` is unchanged; update error-branching if you want to handle these cases specifically.

### 2026-06-30 — Modify order client id semantics simplified (devnet1)

#### Changed — \[REST] · \[WS-OrderEntry] `modifyOrder` uses one `clientOrderId` field

`modifyOrder` no longer has a separate resting-client-id concept. Target by `orderId` when present, otherwise by non-zero `clientOrderId`. The same `clientOrderId` field restates the order's immutable client id for signing. Omit `clientOrderId` when the resting order has no client id; the JSON request must not send a placeholder value.

**What to do:** remove any SDK/client code that passes a separate `restingClientOrderId` / `resting_client_order_id`, or sends `"0"` as a no-client-id placeholder, and regenerate closed SDK/schema bindings.

### 2026-06-30 — Request error-code suffix convention completed (devnet1)

#### Fixed — \[REST] · \[WS-OrderEntry] remaining not-found error codes use `_ERROR`

The public `RequestErrorCode` enum now uses the `_ERROR` suffix consistently for not-found style request failures. `SYMBOL_NOT_FOUND`, `NO_ACCOUNTS_FOUND`, and `NO_PRICES_FOUND_FOR_SYMBOL` are renamed to `SYMBOL_NOT_FOUND_ERROR`, `NO_ACCOUNTS_FOUND_ERROR`, and `NO_PRICES_FOUND_FOR_SYMBOL_ERROR`.

**What to do:** regenerate closed SDK/schema bindings and update any string comparisons for these three codes.

### 2026-06-30 — Order and execution response schemas aligned (devnet1)

#### Changed — \[REST] · \[WS-Info] order and spot execution fields

`Order` responses now include optional `clientOrderId` when the resting order has a non-zero client id. `ModifyOrderResponse.execQty` is present only when the modify crossed and filled immediately; rested modifies omit it. `SpotExecution` renames taker-side fields to `takerAccountId`, `takerOrderId`, and `takerFee`; `ExecutionBust` renames `accountId` and `orderId` to `takerAccountId` and `takerOrderId`.

**What to do:** regenerate closed SDK/schema bindings and update spot execution and execution-bust consumers to the `taker*` field names.

#### Added — \[REST] · \[WS-Info] `fillId` and `PerpExecution` maker-side fields

Executions and busts gain an optional `fillId` (a stable fill identifier) on `PerpExecution`, `SpotExecution`, and `ExecutionBust` — a stable key to join a settled fill to its ME fill and to `orderChanges`; absent for legacy and non-`ORDER_MATCH` (e.g. auto-exchange) executions. `PerpExecution` additionally gains optional maker-side fields — `makerAccountId`, `makerOrderId`, `makerFee` (negative = rebate), `makerOpeningFee`, `makerRealizedPnl`, `makerPriceVariationPnl`, `makerFundingPnl` — so one execution record carries both sides of a fill.

**What to do:** regenerate closed SDK/schema bindings and treat all of these as optional. Use `fillId` to reconcile a fill across executions, busts, and `orderChanges`.

### 2026-06-30 — Order expiry response shape clarified (devnet1)

#### Fixed — \[REST] · \[WS-Info] `Order.expiresAfter` omitted for non-GTT orders

`Order.expiresAfter` on open-orders and `orderChanges` responses is present only for `GTT` orders. `GTC`, `IOC`, and order types with no public lifetime omit the field instead of using `0`.

**What to do:** detect a GTT expiry from a present `expiresAfter` value on an order response. Request signing is unchanged: non-GTT order-entry requests still encode `OrderDetails.expiresAfter = 0` internally.

### 2026-06-29 — Asset oracle price feed added; legacy prices deprecated (devnet1)

*Effective with the 2026-06-29 devnet1 API update.* This is a backward-compatible change now: the legacy prices feed remains live, but is deprecated. Removing it will be a separate breaking change with its own notice.

#### Added — \[REST] · \[WS-Info] asset oracle prices

`GET /v2/assetOraclePrices` and the `/v2/assetOraclePrices` WebSocket channel return asset Stork oracle prices as `AssetOraclePrice { asset, oraclePrice, updatedAt }`.

The replacement feed deliberately does **not** include AMM-era `poolPrice`.

**What to do:** use this feed when you need asset oracle prices. Use market summary `markPrice` and depth/mid-price fields for market prices.

#### Deprecated — \[REST] · \[WS-Info] `/v2/prices` and `/v2/prices/{symbol}`

The legacy prices endpoints/channels mix market and collateral semantics and keep the AMM-era `poolPrice` field name for backward compatibility. They are still served for existing clients, but new integrations should not build against them.

**What to do:** migrate asset-oracle consumers to `/v2/assetOraclePrices`. For perp market valuation use market summary `markPrice`; for book mid/depth use the market summary/depth surfaces.

#### Removed — \[REST] · \[WS-Info] unprefixed perp market summary routes

Use `/v2/perpMarkets/summary` and `/v2/perpMarket/{symbol}/summary` for perp market summaries. The unprefixed `/v2/markets/summary` and `/v2/market/{symbol}/summary` aliases are removed.

### 2026-06-29 — AMM-era reference endpoints removed (devnet1)

*Effective with the 2026-06-29 devnet1 API update.* These are breaking REST changes for clients still calling AMM-era reference-data endpoints.

#### 🔴 BREAKING — \[REST] `GET /v2/marketDefinitions` removed

The unprefixed AMM-era market-definitions route is removed from devnet1. Use `GET /v2/perpMarketDefinitions` for perp market definitions. `perpMarketDefinitions` is the canonical route and carries the live perp market parameters such as `marketId`, `minOrderQty`, `qtyStepSize`, `tickSize`, risk parameters, and `oiCap`.

**What to do:** replace every `GET /v2/marketDefinitions` call and generated SDK method binding with `GET /v2/perpMarketDefinitions`.

#### 🔴 BREAKING — \[REST] `GET /v2/liquidityParameters` removed

The `LiquidityParameters` response was specific to AMM pricing (`depth` and `velocityMultiplier`) and does not apply to perpOB. Order-book liquidity is exposed through per-market depth snapshots instead.

**What to do:** delete `LiquidityParameters` consumers. Use `GET /v2/market/{symbol}/depth` for live order-book depth, and use `GET /v2/perpMarketDefinitions` for static market parameters.

### 2026-06-29 — Cancel reasons, branchable order-entry errors, and status cleanup (devnet1)

*Effective with the 2026-06-29 devnet1 API update.* These are mostly additive integration-surface changes, with one devnet1-only enum cleanup: open-schema clients continue to work, while closed-enum and generated clients should regenerate.

#### 🔴 BREAKING — \[REST] · \[WS-OrderEntry] · \[WS-Info] `OrderStatus.REJECTED` removed

Public order statuses are now only `OPEN`, `FILLED`, and `CANCELLED`. Request-level rejects such as post-only-would-cross return an error response instead: REST uses the relevant `RequestErrorCode`, and ws-exec replies `ok: false` with the same error payload. Accepted orders that terminate without resting or fully filling use `CANCELLED` plus optional `cancelReason`.

**What to do:** remove `REJECTED` branches from closed `OrderStatus` enums. Handle request failures through error responses and cancelled accepted outcomes through `cancelReason`.

#### Added — \[REST] · \[WS-OrderEntry] · \[WS-Info] cancel reasons on order responses and order state

`Order`, `CreateOrderResponse`, and `ModifyOrderResponse` can now include optional `cancelReason` and `cancelReasonMessage` fields when an order is cancelled. The initial reason set is `NO_LIQUIDITY`, `IOC_REMAINDER`, `SELF_TRADE_PREVENTION`, `GTT_EXPIRED`, `USER_CANCEL`, `MASS_CANCEL`, and `CANCEL_ALL_AFTER`.

**What to do:** regenerate closed SDK/schema bindings and treat both fields as optional. Use `cancelReason` to distinguish normal user/cancel-all flows from engine outcomes such as IOC remainder, no liquidity, self-trade prevention, and GTT expiry.

Precedence note: if an IOC partially fills and its remaining quantity is then cancelled by self-trade prevention, the response keeps the fill quantities and reports `cancelReason: SELF_TRADE_PREVENTION`. `IOC_REMAINDER` only covers remaining IOC quantity cancelled because matching stopped without a self-cross.

#### Added — \[REST] · \[WS-OrderEntry] more specific `RequestErrorCode` values

Order-entry request failures now expose more precise codes instead of collapsing into broad catch-alls. New values are `RATE_LIMITED_ERROR`, `INSUFFICIENT_BALANCE_ERROR`, `OPEN_ORDER_CAP_ERROR`, `PRICE_QTY_BOUNDS_ERROR`, `SERVICE_DISABLED_ERROR`, `UNAUTHORIZED_ACCOUNT_ERROR`, `TRADING_HALTED_ERROR`, and `DUPLICATE_CLIENT_ORDER_ID_ERROR`.

**What to do:** add these values to closed enums and branch on them where useful. Existing catch-all values remain possible; keep reading the `message` field for operation-specific details.

#### Fixed — \[REST] · \[WS-OrderEntry] order-entry docs/spec alignment

`POST /v2/cancelAll` is documented with a required request body, the `CancelAllAfter` signing reference includes signed `deadline`, and out-of-range `cancelAllAfter.timeoutMs` is documented as `INPUT_VALIDATION_ERROR` rather than a matching-engine catch-all.

### 2026-06-29 — Order-to-fill range fields on order responses and `orderChanges` (devnet1)

*Live with the 2026-06-29 devnet1 API update.* Additive, backward-compatible.

#### Added — \[REST] · \[WS-OrderEntry] · \[WS-Info] `firstFillId` + `fillCount` on order responses and order state

`Order` (open-orders + `orderChanges`), `CreateOrderResponse`, and `ModifyOrderResponse` now carry optional `firstFillId` (identifier of the first fill) and `fillCount` (number of fills). Together they advertise the contiguous fill-ID range an order update produced — `[firstFillId, firstFillId + fillCount − 1]`. Both are present only when the update represents fills (absent for non-fill updates and resting snapshots); `fillCount` is `≥ 1` whenever present.

**What to do:** use `firstFillId` / `fillCount` to join an order update directly to its `fillId`-keyed executions (see [Executions & Trade History](https://docs.reya.xyz/developers/executions-and-settlement/executions-and-trade-history.md)), instead of reconciling by `orderId` alone. Regenerate closed SDK/schema bindings and treat both fields as optional.

### 2026-06-29 — Perp Order Book launch (devnet1)

*Effective 2026-06-29.* The order book replaces the previous AMM trading model. The order-entry and on-chain settlement surfaces changed for **both perp and spot** — even spot-only integrators must update their client. Porting an existing mainnet V2 client? The **V2 perpOB Migration Reference** (retired after launch) is the complete, field-by-field guide.

Headlines:

* 🔴 Order-entry EIP-712 signing envelope rebuilt — every integrator (incl. spot) must re-sign.
* 🔴 `postOnly` is now enforced; `expiresAfter` is TIF-coupled (GTC / IOC omit it).
* 🔴 `orderId` / `clientOrderId` are now opaque strings; several response fields and enums renamed (`TP` / `SL` → `TAKE_PROFIT` / `STOP_LOSS`).
* `STOP_LOSS` / `TAKE_PROFIT` orders are natively armed, re-priceable, and cancellable; they do not execute at `triggerPx` until the firing release.
* Added: `modifyOrder` (in-place amend) and `cancelAllAfter` (dead-man's switch).

See the V2 perpOB Migration Reference (retired after launch) for all 27 breaking changes and a migration checklist.
