Skip to main content
POST
Send events to Formo from any source. Sending custom events? See the event specs.
This endpoint is hosted on events.formo.so, a separate service from the main API at api.formo.so.
Sending events from the backend? Use the server-side SDK.

Authorizations

Authorization
string
header
required

Workspace API key (e.g. formo_xxx). Create one in the Formo dashboard under Team Settings > API Keys.

Body

application/json
type
enum<string>
required
Available options:
page,
connect,
disconnect,
chain,
signature,
transaction,
track,
decoded_log,
detect,
identify
channel
enum<string>
required

Source of the event. The Formo Web SDK uses web; mobile SDK uses mobile; server SDK uses server. Use api for direct HTTP submissions and import for backfills.

Available options:
web,
mobile,
server,
api,
import
version
string
required

SDK schema version. Web SDK 1.x emits 1; legacy clients emit 0.

Example:

"1"

anonymous_id
string
required

Anonymous visitor identifier

user_id
string | null

Identified user ID

address
string | null

Wallet address

event
string | null

Event name (for track events)

context
object

Contextual information about the event environment

properties
object

Event-specific properties. Can contain any key-value pairs relevant to the event.

original_timestamp
string<date-time>
sent_at
string<date-time>
message_id
string

Unique ID for deduplication. Optional; a UUID is generated server-side when omitted.

Response

200 - application/json

Events ingested

successful_rows
integer
quarantined_rows
integer