Event Forwarding

Endpoints for forwarding events from external sources

Forward Explorer Events

post
/forward

Forwards events from the Decentraland Explorer client. This endpoint processes and validates client-side events such as user movement, emotes, login events, and other in-world interactions.

Events are validated for:

  • Signature authenticity using HMAC-SHA1

  • AuthChain validation for user authentication

  • Event structure and content validation

  • User address verification

Supported event types:

  • move_to_parcel: User movement between parcels

  • used_emote: Emote usage events

  • passport_opened: Passport interaction events

  • walked_distance: Movement tracking

  • vertical_height_reached: Height-based achievements

  • logged_in: User login events

  • logged_in_cached: Cached login events

Authorizations
x-signaturestringRequired

HMAC-SHA1 signature for event validation

Body

Explorer client event data

eventstringOptional

Event type identifier

Example: move_to_parcel
messageIdstringOptional

Unique message identifier

Example: msg_123456789
anonymousIdstringOptional

Anonymous user identifier

Example: anon_abc123
userIdstringOptional

User identifier (if available)

Example: 0x1234567890abcdef
timestampstring · date-timeOptional

Event timestamp

sentAtstring · date-timeOptional

When the event was sent

receivedAtstring · date-timeOptional

When the event was received

Responses
chevron-right
200

Event successfully processed and forwarded

application/json
post
/forward

Forward Web Events

post
/forward-web

Forwards events from web applications and analytics platforms. This endpoint processes web-based events such as page views, user interactions, and analytics data.

Events are validated for:

  • Signature authenticity using HMAC-SHA1

  • Event structure validation

  • User context validation (if Ethereum address is present)

  • Anonymous ID validation and flagging

This endpoint supports Segment-compatible web events and includes special handling for authentication events that link anonymous IDs to Ethereum addresses.

Authorizations
x-signaturestringRequired

HMAC-SHA1 signature for event validation

Body

Web event data

typestringOptional

Event type

Example: track
messageIdstringOptional

Unique message identifier

Example: msg_web_123456
anonymousIdstringOptional

Anonymous user identifier

Example: anon_web_abc123
userIdstringOptional

User identifier (if available)

Example: 0x1234567890abcdef
timestampstring · date-timeOptional

Event timestamp

sentAtstring · date-timeOptional

When the event was sent

receivedAtstring · date-timeOptional

When the event was received

originalTimestampstring · date-timeOptional

Original event timestamp

integrationsobjectOptional

Integration settings

projectIdstringOptional

Project identifier (for specific event types)

Responses
chevron-right
200

Event successfully processed and forwarded

application/json
post
/forward-web

Last updated