Skip to content

query-requests.mdx

Latest commit

 

History

History
88 lines (63 loc) · 3.06 KB

query-requests.mdx

File metadata and controls

88 lines (63 loc) · 3.06 KB
title Query Requests
description Request status monitoring, lifecycle management, and information retrieval

Overview

Use query endpoints to retrieve the latest status for a specific request.

These endpoints are the main reconciliation surface for request-level state (paid/not paid, payment references, transaction hash, and optional metadata).

Core Endpoints

How It Works

Call [GET /v2/request/{requestId}](https://api.request.network/open-api/#tag/v2request/GET/v2/request/{requestId}) to get current request-level status fields.

Typical fields include:

  • hasBeenPaid
  • paymentReference
  • txHash
  • isListening
  • requestAmount — the original requested amount in invoice currency
  • detectionSource — how the payment was confirmed ("request-network" or "lifi")
  • note — additional context for non-standard settlements (e.g., LiFi fallback)
  • optional metadata such as customerInfo and reference
Use [Webhooks & Events](/api-features/webhooks-events) for push updates, and use query endpoints as source-of-truth reads. For wallet-level reconciliation views, use [GET /v2/payments](https://api.request.network/open-api/#tag/v2payments/GET/v2/payments).

Request Status Query

GET /v2/request/{requestId} is the canonical request-level status endpoint for:

  • request payment completion checks (hasBeenPaid)
  • transaction linkage (txHash)
  • request identification (requestId, paymentReference)
  • conversion-related status fields when applicable (amountInUsd, conversionRate, conversionBreakdown)

Reconciliation Pattern

React to events in real time and update app state immediately. Use query endpoints to confirm latest status and backfill missed events.

Practical Notes

  • Use requestId for deterministic lookup.
  • Keep idempotent reconciliation logic in case the same request is processed multiple times by your workers.

Related Pages

Understand automatic detection and status updates. Search and reconcile payment-level events. Build real-time event-driven reconciliation.

API Reference

For full schemas and examples, see Request Network API Reference.