Skip to main content
POST
/
api
/
dual-signed-ops
/
{opId}
/
release-expired
Release an EXPIRED split / merge lock after verifying on-chain absence
curl --request POST \
  --url https://core-api.adipredictstreet.com/api/dual-signed-ops/{opId}/release-expired \
  --header 'X-Api-Key: <api-key>'
{
  "signedOpId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "<string>",
  "vaultAddress": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3",
  "deadline": 123,
  "refunded": true,
  "refundAppliedNow": true,
  "updatedAt": "2023-11-07T05:31:56Z",
  "reason": "<string>",
  "txHash": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.adipredictstreet.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
X-Api-Key
string
header
required

Partner / integrator key — format ps_live_<keyId>_<secret>. Issued by PredictStreet ops on request; never self-service. Never ship to a browser. multi_wallet partners must additionally send X-User-Wallet: 0x<40-hex> on every authenticated request to declare the acting wallet. See the API keys guide for scope taxonomy, partner kinds, rate limits, and rotation procedure.

Headers

​
X-User-Wallet
string

Required for multi_wallet partners on every authenticated request; ignored for single_wallet. Declares the acting end-user wallet for this request — drives KYC checks, balances/positions/orders attribution, rate-limit buckets, and audit. Lower-cased server-side. Missing on a multi_wallet key → 401 api_key_user_wallet_required; malformed → 401 api_key_user_wallet_invalid. The on-chain CTFExchange/Vault contracts still verify EIP-712 signer ↔ vault binding, so loosening API-layer attribution is safe by construction.

Pattern: ^0x[a-fA-F0-9]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

Path Parameters

​
opId
string<uuid>
required

signed_ops.id UUID returned by the original split / merge / convert signature endpoint.

Response

Refund applied, or no-op snapshot of an already-terminal op (use refundAppliedNow to distinguish).

​
signedOpId
string<uuid>
required

signed_ops.id — same UUID the original signature endpoint returned.

​
opKind
enum<string>
required

Operation kind. Always SPLIT or MERGE on success — other kinds short-circuit with 400 op_kind_unsupported.

Available options:
SPLIT,
MERGE
​
status
string
required

Post-call status. EXPIRED after a successful refund; whatever the row was already in (EXPIRED / CANCELLED / REVERTED / REJECTED / FAILED) on an idempotent re-request.

​
vaultAddress
string
required
Pattern: ^0x[a-fA-F0-9]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

​
deadline
integer
required

Unix seconds the op was signed against. Always more than 90s in the past on a successful response.

​
refunded
boolean
required

signed_ops.refunded after this call — true for any EXPIRED/CANCELLED/REVERTED/REJECTED/FAILED terminal.

​
refundAppliedNow
boolean
required

true if this call performed the refund transition; false for an idempotent re-request against an already-terminal op (the row is returned unchanged).

​
updatedAt
string<date-time>
required

ISO-8601 timestamp of the last signed_ops mutation.

​
reason
string | null

signed_ops.reason audit string — set to user:<vaultAddress> after a successful refund by this endpoint; may be sweeper / cosigner / etc. on rows refunded by other paths.

​
txHash
string | null

signed_ops.tx_hash. Always null on this endpoint's responses — the op never confirmed on-chain by definition.