Caller identity
By default, every call to your data source looks like it came from incident.io. Turn on Share caller identity and each call tells your server who actually made it, so you can:- Apply access controls per caller.
- Rate-limit each caller separately.
- Restrict what automated callers, such as investigations, can do.
- Log who made each call.
Turn it on
Open the data source’s settings and turn on Share caller identity. You need the Manage Nexus sources permission. We record the change in your audit log. From then on, every call to that source carries the caller, whether it comes from Investigations, Chat, a workflow or the incident.io MCP.What your server receives
Each request gets two extra headers:X-Incident-Actorsays who the caller is. It matches the actor on the call’s audit log entry.X-Incident-Actor-Assertionis a signed JWT that proves it. Verify it before you trust the header.
What’s in the assertion
Here’s a decoded assertion for a user who asked Chat a question during an incident, where someone had to approve the call first:ctx.surface is always set, for example chat, investigation or mcp_client. The other keys only appear when they apply:
Verify the assertion
Fetch our public keys fromhttps://app.incident.io/.well-known/jwks.json, pick the one matching the assertion’s kid, and check the signature, issuer, audience and expiry. Then check sub matches X-Incident-Actor.
For example, in Node.js with jose:
kid: we rotate them.