ArchitectArchitect

WebHooks

February 4, 2026|

Architect supports WebHooks for different events. You are able to send fully customizable payload structures to any specified URL.

Once a WebHook has been created, the specified URL will be contacted once such an event occurs.

WebHook deliveries

All WebHook events are sent from the Agent directly. You are able to customize the amount of retries, the HTTP timeout and supply custom headers for all deliveries of any WebHook.

Deliveries are individually tracked and contain a unique delivery id. A record about all deliveries is kept for 7 days.

In case any specific delivery fails, it will be retried based on your configured retry counter.

All delivers carry certain technical headers that allow you to identify an Architect WebHook event:

KeyDescription
X-WebHookStatic string: "Architect Agent"
X-WebHook-IdUnique id of the WebHook registration
X-WebHook-EventEvent type of the delivery
X-Event-IdempotenceIdempotence token that is static for each delivery to catch double deliveries in case of retries

You are able to access the WebHooks your agent has executed from WebHooks, Deliveries:

Templating

WebHook payloads can be templated. Different events have different templating values available that carry information about that specific event.

Parameters can be embedded in the format `{{parameter}}` where parameter represents the individual values name.

Events

agent.ready

General event, not specific to any reference entity

Sent when an Agent has started.

ValueDescription
dateUTC Unix timestamp of event occurrence

session.begin

General event, not specific to any reference entity

Sent when a user connects to an Agent.

ValueDescription
dateUTC Unix timestamp of event occurrence
userUsername
ip_addressIP address used to connect
sessionUnique session id

session.ended

General event, not specific to any reference entity

Sent when a user disconnects from an Agent.

ValueDescription
dateUTC Unix timestamp of event occurrence
userUsername
ip_addressIP address used to connect
sessionUnique session id

server.started

Filtered event, only applies to specific entities or all

Sent when a server starts.

ValueDescription
dateUTC Unix timestamp of event occurrence
serverServer identifier

server.stopped

Filtered event, only applies to specific entities or all

Sent when a server stops.

ValueDescription
dateUTC Unix timestamp of event occurrence
serverServer identifier
reasonReason code for server stop: - requested - killed

server.updated_title

Filtered event, only applies to specific entities or all

Sent when a server is updated (after update completes).

ValueDescription
dateUTC Unix timestamp of event occurrence
serverServer identifier
titleTitle id

server.updated_mod

Filtered event, only applies to specific entities or all

Sent when a mod update is applied to the server (after update completes).

ValueDescription
dateUTC Unix timestamp of event occurrence
serverServer identifier
modMod name (depending on modding ecosystem)
mod_idMod id (depending on modding ecosystem)

title.updated

General event, not specific to any reference entity

Sent when a title update has been discovered.

ValueDescription
dateUTC Unix timestamp of event occurrence
titleTitle id

mod.updated

General event, not specific to any reference entity

Sent when a mod update has been discovered.

ValueDescription
dateUTC Unix timestamp of event occurrence
modMod name (depending on modding ecosystem)
mod_idMod id (depending on modding ecosystem)
Was this article helpful?
Back to Architect