Skip to main content
GET
/
x402
/
v1
/
events
/
{eventId}
Get event
curl --request GET \
  --url https://gateway.sanfoundation.com/x402/v1/events/{eventId} \
  --header 'Payment-Signature: <api-key>'
{
  "event": {
    "eventId": "<string>",
    "title": "<string>",
    "summary": "<string>",
    "firstSeenAt": "2023-11-07T05:31:56Z",
    "lastUpdatedAt": "2023-11-07T05:31:56Z",
    "primaryAgent": "<string>",
    "eventType": "<string>",
    "status": "<string>",
    "tags": [
      "<string>"
    ],
    "sourceCount": 123,
    "entities": [
      {
        "name": "<string>",
        "type": "<string>",
        "role": "<string>"
      }
    ],
    "locations": [
      {
        "name": "<string>",
        "country": "<string>"
      }
    ],
    "sources": [
      {
        "url": "<string>",
        "publication": "<string>",
        "publishedAt": "2023-11-07T05:31:56Z"
      }
    ],
    "occurredAt": "2023-11-07T05:31:56Z"
  }
}

Authorizations

​
Payment-Signature
string
header
required

Base64-encoded signed payment payload as defined by the x402 protocol. Omit on the first attempt to receive the 402 challenge in the PAYMENT-REQUIRED response header; include it on the retry to settle payment and receive the resource.

The legacy header name X-PAYMENT is also accepted by the server for backward compatibility — clients may send either, but Payment-Signature is preferred.

See x402.org for the on-the-wire shape of the PaymentRequired challenge and the settlement receipt returned in the PAYMENT-RESPONSE response header.

Path Parameters

​
eventId
string
required

Stable canonical event id (e.g. evt_d62a81a5e8b2366027fbaf6b).

Pattern: ^evt_[a-z0-9]{16,}$

Response

OK — single canonical event envelope.

​
event
object
required