​

Activity

GET /v1/predexon/activity — Retrieve on-chain activity operations (MERGE, SPLIT, REDEEM) for a specific user wallet. Filter by time range, market, or condition with offset pagination.

• Base URL: https://api.predexon.com/v1
• Auth: x-api-key: <YOUR_API_KEY>
• Time: All timestamps are Unix timestamps (seconds) for filtering; responses use ISO-8601 format.
• Pagination: Offset-based via limit and offset parameters.
• Rate Limits: 100 requests/minute per API key. Returns 429 with Retry-After header (seconds) when exceeded. Use exponential backoff on 429/503 responses.

​

Endpoint

GET /v1/predexon/activity

​

Query parameters

​

Validation rules

• user (required): Must be provided. Returns 400 if missing.
• market_slug vs condition_id: Only one of these filters can be applied. If both are provided, returns 400 bad_request.
• time range: If both start_time and end_time are provided, start_time must be less than end_time. Returns 400 if violated.
• limit: Must be between 1 and the configured MAX_LIMIT (typically 1000). Returns 400 if exceeded.
• offset: Must be >= 0. Returns 400 if negative.

​

Response schema

{
  "activities": [
    {
      "id": "activity_001",
      "user": "0x742d35Cc6634C0532925a3b844Bc9e7595f42bF",
      "activity_type": "MERGE",
      "timestamp": "2025-10-15T14:32:45Z",
      "market_slug": "crypto-btc-above-75000-2025-07-01",
      "condition_id": "0x1234567890abcdef",
      "token_from": "0x...",
      "token_to": "0x...",
      "quantity": "150.50",
      "tx_hash": "0xabc123...",
      "block_number": 18750432,
      "status": "confirmed"
    }
  ],
  "pagination": {
    "limit": 100,
    "offset": 0,
    "count": 45,
    "has_more": false
  }
}

​

Field reference

​

Activity object

​

Pagination object

​

Activity types

​

MERGE

{
  "activity_type": "MERGE",
  "token_from": ["0x...", "0x..."],
  "token_to": "0x...",
  "quantity": "100.00"
}

​

SPLIT

{
  "activity_type": "SPLIT",
  "token_from": "0x...",
  "token_to": ["0x...", "0x..."],
  "quantity": "50.00"
}

​

REDEEM

{
  "activity_type": "REDEEM",
  "token_from": "0x...",
  "quantity": "200.50"
}

​

Examples

curl -s "https://api.predexon.com/v1/predexon/activity?user=0x742d35Cc6634C0532925a3b844Bc9e7595f42bF&limit=50" \
  -H "x-api-key: YOUR_API_KEY"

{
  "activities": [
    {
      "id": "activity_001",
      "user": "0x742d35Cc6634C0532925a3b844Bc9e7595f42bF",
      "activity_type": "MERGE",
      "timestamp": "2025-10-15T14:32:45Z",
      "market_slug": "crypto-btc-above-75000-2025-07-01",
      "condition_id": "0x1234567890abcdef",
      "token_from": "0x...",
      "token_to": "0x...",
      "quantity": "150.50",
      "tx_hash": "0xabc123...",
      "block_number": 18750432,
      "status": "confirmed"
    }
  ],
  "pagination": {
    "limit": 100,
    "offset": 0,
    "count": 45,
    "has_more": false
  }
}

​

Errors

{
  "error": {
    "type": "invalid_parameter",
    "message": "user is required",
    "param": "user"
  }
}

{
  "activities": [],
  "pagination": {
    "limit": 100,
    "offset": 0,
    "count": 0,
    "has_more": false
  }
}

​

Best practices

1. Use time filters: For large datasets, filter by start_time and end_time to reduce result set and improve performance.
2. Pagination strategy: Start with offset=0 and increment by limit. Use has_more to detect the last page instead of checking array length.
3. Filter specificity: Use either market_slug or condition_id, not both. Choose the one most relevant to your query.
4. Monitoring activity: Poll the endpoint on an interval (e.g., 30–60 seconds) or store the latest processed timestamp to detect new activity.
5. Error handling: Implement exponential backoff for 429 and 503 responses. For 400 errors, validate parameters before retrying.
6. Caching: Cache results by the full query string and invalidate when appropriate (e.g., on user request or periodic refresh).
7. Large result sets: If a user has many activities, use pagination with reasonable limits (100–500 per page) to avoid timeouts.

​

Related

• Orders — Historical order data with filtering
• Trading Data Overview — Introduction to trading endpoints