Retrieve Session Response

Retrieve the cached webhook payload for an authentication session using sessionId.
This is useful when your backend receives or tracks a session and later needs to fetch the same auth-init payload (challenge + redirect metadata) in a pull-based way.

Example auth URL with session id:
https://auth.blockpeer.finance/auth?sessionId=f07aa200-a027-4e13-9142-2f0e897a7eea
From this URL, the sessionId is:
f07aa200-a027-4e13-9142-2f0e897a7eea

Quick Integration Notes

  • Call this endpoint when your client/MCP flow needs latest cached response for a session.
  • Always store sessionId from earlier auth/register initiation APIs.
  • Handle 404 as expired/invalid session and restart the relevant auth flow if needed.
Query Params
string
required

Unique session identifier returned by auth-init endpoints and used in the auth URL

Headers
string

Unique external ID for tracking purposes, can be used for debugging and analytics.

string

Unique key to ensure idempotency for API requests.

Responses
200

Session information retrieved successfully

401

Token is absent or invalid

404

Wallet not found

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here!