Create a new event
Creates a new event in the system. The behavior depends on the event_type provided:
- register_resource: Registers a new resource (robot/bot) in the system
- task_start: Creates a new task run
- task_end: Completes an existing task run
- task_validate: Validates a completed task run and awards VRW points
- points_grant: Grants uncapped Subnet Points to a user. The grant is recorded in the current open distribution window; the server assigns the timestamp and epoch, so callers cannot specify them.
- points_revoke: Revokes previously granted Subnet Points from a user. A revoke that identifies the user by
recipientdebits their unconverted Subnet Points (points not yet converted to BitRobot Bolts) immediately. A revoke that names a grant byoriginal_client_reftakes exactlypointsfrom that grant, up to what’s left of it: right away if the grant hasn’t converted to Bolts, or, if it has, through a reversal request the API files for exactlypoints, responding202 Accepted. A BitRobot admin reviews the request, and nothing is debited unless they approve it.
Authorizations
API key authentication. Your API key should start with brb_.
Example: Authorization: Bearer brb_1234567890abcdef
Headers
Optional replay key, unique per event attempt. Repeating a request with the same key within 24 hours replays the stored response (with an Idempotency-Replayed: true header) instead of creating a second event; a different body under the same key answers 409.
255Path Parameters
The unique identifier of the subnet (ULID format)
^[0-9A-HJKMNP-TV-Z]{26}$Body
- Register Resource Event
- Task Start Event
- Task End Event
- Task Validate Event
- Points Grant Event
- Points Revoke Event
The type of event
register_resource The name of the resource to register. ENT resource names are limited to 32 characters (on-chain NFT name limit); longer names are rejected with 422.
32"bot_001"
The subtype of the resource (e.g., 'frodobot', 'delivery-drone', etc.)
"frodobot"
The Solana wallet address of the resource owner. Used to create a wallet record in the system and associate it with the resource for reward tracking. Required.
"HN7cABqLq46Es1jh92dQQisAq662SmxELLLsHHe4YWrH"
The type of resource to register. Use 'ent' (default) for full ENT NFT resources, or 'resource' for lightweight non-NFT participants that still earn rewards.
ent, resource Email address of the resource owner. Required on subnets that pay VRW points to email identities whenever the resource is created by name, or is referenced by resource_id but has no owner yet; a resource that already has an owner needs no identity. Optional on other subnets (recorded for attribution). Mutually exclusive with ent_owner_discord_id. The address is resolved to a BitRobot account (a placeholder is created for an unknown address) and VRW points for this resource go to that account.
Discord user ID (snowflake) of the resource owner. Required on subnets that pay VRW points to Discord identities, under the same rules as ent_owner_email. Mutually exclusive with ent_owner_email.
"1471164890898104436"
Metadata for the ENT (Entity NFT) that represents this resource on-chain, following the Metaplex token standard. Provide this alongside ent_owner (on task_start) or owner (on register_resource) to mint a named, attributed NFT. If omitted, a placeholder metadata URI is used.
Show child attributes
Show child attributes
{ "name": "Frodobot #001", "symbol": "FRODO", "description": "Autonomous delivery robot with advanced navigation capabilities", "image": "https://example.com/images/frodobot-001.png", "external_url": "https://example.com/ents/frodobot-001", "attributes": [ { "trait_type": "Model", "value": "X-2000" }, { "trait_type": "Generation", "value": 2 } ], "properties": { "category": "robot", "files": [ { "uri": "https://example.com/images/frodobot-001.png", "type": "image/png" } ] } }
Response
Event created successfully. The response data contains different fields depending on the event type - see examples for details. A points_revoke event that files a reversal request instead of revoking, or finds one pending, returns 202. Sending a points_revoke again with the client_ref of a reversal request a BitRobot admin has decided returns 200 with outcome reversal_approved or reversal_rejected.