Custom Events

What Plutus imports

• Any event you add — deploys, incidents, feature launches, whatever you annotate

Connecting

Method: Manual entry, or a Plutus-issued API key for scripted/bulk pushes

Adding an event by hand

Use this for a one-off annotation that isn’t worth scripting.

1. In Plutus, go to Event Sources → Custom Events.
2. Under Add an event manually, fill in a title, when it occurred, and an optional category.
3. Click Add.

Manually added events show up alongside pushed ones and can be deleted from the same panel. An account can hold up to 1,000 custom events between the two methods combined.

Pushing events via API

Use this to send events from your own systems or scripts.

1. In Plutus, go to Event Sources → Custom Events and click Generate API Key.

2. Copy the key now — it won’t be shown again.

3. POST to /api/ingest/events with an Authorization: Bearer <key> header and a JSON body of:

   {
     "events": [
       {
         "title": "...",
         "occurred_at": "2026-01-01T00:00:00Z",
         "external_id": "your-own-stable-id",
         "category": "marketing"
       }
     ]
   }

4. external_id is your own stable identifier for the event — posting the same one again updates nothing and creates no duplicate.

Notes

Unlike every other event source, Custom Events is push-based rather than polled — there’s no sync schedule to wait on, and no connection to go stale. Events appear on the timeline as soon as they’re added or posted.

category is optional and free-form — set it to whatever grouping makes sense to you (e.g. marketing, ops, product). Event Explorer’s source filter lets you narrow the timeline down to one category, the same per-source facet mechanism used to filter GitHub events down to one repo.