> ## Documentation Index > Fetch the complete documentation index at: https://docs.aura.markets/llms.txt > Use this file to discover all available pages before exploring further. # Aggregated content-report queue. > Reads the admin_report_queue view (open reports grouped per object; muted reporters count zero, serial-dismissed reporters are down-weighted) and joins in a best-effort object preview. Escalated rows (weighted score ≥ 3) sort first. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/admin/moderation/reports openapi: 3.1.0 info: title: Aura API description: >- Public REST API for Aura — prediction markets on Alephium. This API exposes everything a user can see or do in the app: markets, prices, orderbook, trades, vault state, oracle and governance, plus build-tx endpoints that return unsigned transactions for the client to sign with its own wallet. Interactive reference: https://docs.aurabets.io/api-reference/introduction ## Discovery Built for integrators, not for lazy implementers: - **Faceted lists** — every list endpoint accepts `?facets=true` and returns category / tag / status counts in the same response, so a UI can render filter chips without a second request. - **Cursor pagination** — stable across inserts and fast at depth. Offset paging via `?page=` is still supported for compat. - **Rich filters** — `?q=`, `?category=`, `?tags=`, `?status=`, `?creator=`, `?minVolume=` on `/v1/markets`. Tag matching is AND (all listed tags must be present). - **Sortable** — `?sort=created-at|volume|best-bid-yes|recently-traded` with `?order=asc|desc`. Use `/v1/trending` for the composite-score sort. - **Field projection** — `?fields=id,question,bestBidYes` trims the wire weight for thin clients. - **Unified search** — `/v1/search?q=` runs a strict tsquery first with a fuzzy trigram fallback when nothing matches; result type is a discriminated union so adding events / users later is non-breaking. - **Transparent trending** — `/v1/trending` returns the full algorithm + per-market component scores so the ranking is auditable. - **Categories + tags as first-class** — `/v1/categories` and `/v1/tags` enumerate the taxonomy with market counts. ## Authentication Aura uses passkey-backed account sessions delivered as an HttpOnly cookie. Sign in by signing a one-time challenge with your passkey: ``` POST /v1/auth/challenge { "address": "..." } POST /v1/auth/session { "address": "...", "publicKey": "...", "signature": "...", "passkey": { ... } } ``` The `session` call sets the `aura_session` cookie and returns a CSRF token; send it back in the `x-csrf-token` header on every mutating request. `POST /v1/auth/logout` clears the session. Reads are accessible anonymously with low IP-based rate limits; write endpoints (`/v1/tx/*`, social writes) require a valid session. ## Rate limits | Tier | Reads (req/min) | Writes (req/min) | |-----------|----------------:|-----------------:| | Anonymous | 60 per IP | 10 per IP | | Signed-in | 600 per wallet | 60 per wallet | Standard `RateLimit-*` response headers are returned on every request (IETF `draft-ietf-httpapi-ratelimit-headers`). ## Write endpoints Aura is non-custodial — the API never holds private keys. Endpoints under `/v1/tx/*` return an *unsigned* transaction that the caller must sign with its own wallet (passkey, mobile wallet, hardware wallet, etc.) and submit to an Alephium node. A typical "place order" flow: 1. `POST /v1/tx/markets/{address}/orders` → server returns `{ unsignedTx, gasEstimate, ... }`. 2. Wallet signs `unsignedTx`. 3. Wallet submits the signed tx to any Alephium node. version: 0.1.0 license: name: MIT contact: name: Aura url: https://docs.aurabets.io servers: - url: / description: this server security: - SessionCookie: [] - {} tags: - name: Health description: Liveness + version info. - name: Auth description: Passkey account sessions (sign in, sign out). - name: Markets description: Browse and look up prediction markets. - name: Categories description: Top-level market taxonomy with counts. - name: Tags description: Free-form market tags with counts. - name: Events description: Linked-market groups (multi-leg events). - name: Search description: Full-text + fuzzy search across markets. - name: Orderbook description: Live order book + recent fills. - name: Prices description: Latest prices and historical price series. - name: Orders description: Build unsigned tx to place / cancel orders. - name: Vault description: AURA token vault — build unsigned deposit / unlock / withdraw txs. - name: Disputes description: Optimistic oracle disputes — read-side state and votes. - name: Oracle votes description: Build unsigned oracle txs (submit / dispute / commit / reveal). - name: Voting description: Governance proposals + voting period state. - name: Vote description: Build unsigned governance vote tx. - name: Proposals description: Validate + build market-proposal txs (single-leg, linked, parlay). - name: Drafts description: Wallet-private market-proposal drafts (never on chain). - name: Users description: Wallet-scoped reads — profile, positions, orders, parlays. - name: Account actions description: Aggregated "what does this wallet need to do" views. - name: Leaderboard description: Top traders by composite score. externalDocs: description: Full Aura documentation (guides + interactive API reference) url: https://docs.aurabets.io paths: /v1/admin/moderation/reports: get: tags: - Admin summary: Aggregated content-report queue. description: >- Reads the admin_report_queue view (open reports grouped per object; muted reporters count zero, serial-dismissed reporters are down-weighted) and joins in a best-effort object preview. Escalated rows (weighted score ≥ 3) sort first. parameters: - schema: type: string enum: - comment - proposal_comment - outcome_comment - market - proposal - user in: query name: type required: false - schema: default: 50 type: integer minimum: 1 maximum: 200 in: query name: limit required: false responses: '200': description: Default Response content: application/json: schema: type: object properties: rows: type: array items: type: object properties: objectType: type: string enum: - comment - proposal_comment - outcome_comment - market - proposal - user objectId: type: string reporters: type: number weightedScore: type: number escalated: type: boolean reasons: type: object propertyNames: type: string additionalProperties: type: number sampleDetails: type: array items: type: string firstReportedAt: type: string lastReportedAt: type: string preview: anyOf: - type: string - type: 'null' subjectAddress: anyOf: - type: string - type: 'null' hidden: anyOf: - type: boolean - type: 'null' required: - objectType - objectId - reporters - weightedScore - escalated - reasons - sampleDetails - firstReportedAt - lastReportedAt - preview - subjectAddress - hidden additionalProperties: false required: - rows additionalProperties: false '401': description: Default Response content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Machine-readable error code (snake_case). message: type: string description: Human-readable error message. details: {} required: - code - message additionalProperties: false required: - error additionalProperties: false '403': description: Default Response content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Machine-readable error code (snake_case). message: type: string description: Human-readable error message. details: {} required: - code - message additionalProperties: false required: - error additionalProperties: false '503': description: Default Response content: application/json: schema: type: object properties: error: type: object properties: code: type: string description: Machine-readable error code (snake_case). message: type: string description: Human-readable error message. details: {} required: - code - message additionalProperties: false required: - error additionalProperties: false components: securitySchemes: SessionCookie: type: apiKey in: cookie name: aura_session description: >- HttpOnly session cookie set by POST /v1/auth/session. Mutating requests must also send the CSRF token (returned by that call) in the x-csrf-token header. ````