Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guide iconUser guide
Developer guide iconDeveloper guide
Admin guide iconAdmin guide
English
  • Русский
  • English
Login
    Getting StartedAdministrator documentationFunctional characteristics
      Technology descriptionarrow
    • Architecture OverviewComponent Description
        Deployment schemesarrow
      • Basic schemeFail-safe schemeTypical Placement in Infrastructure
    System requirements
      Admin Panelarrow
      • Account areaarrow
        • Accountsarrow
        • Account UsersAccount Virtual SendersAccount Database Indexes
        TariffsExternal data configurationLDAPTasksSchedule JobsGlobal Stop ListsWebversion Store Policies
        Settingsarrow
      • Databases
          Accessarrow
        • AdminsAPI tokens
        Notifiers
          MTAarrow
        • Default rulesRetry rulesLock rulesBounce patternsStrategiesKeysISPsPools
      Nodes
        Sendersarrow
      • EmailSMSEvent generatorIntegration with Altcraft Cloud SMTPIntegration with Sendsay
        Reportsarrow
      • Audit JournalData Usage
        Toolsarrow
      • ARF decoderURL decoderSMID decoderLicense
      Platform installationarrow
    • Automatic installationManual installationRunning the platform in a Docker container
      Platform configurationarrow
    • Configuration fileDomain settingsLDAP access configurationSending Email via SMTP relayPixel and push domain configurationCluster and Replication SetupSystem notifications configurationProcesses UNIX sockets configurationHTTPS ConfigurationMigrating from MongoDB Community Edition to Percona Server for MongoDBAdding sender IP addressesDeduplication request settingsPostgreSQL database for Market dataProxy server settingsKeycloak Integration with AltcraftGetting HTTP service statusesConfiguring MongoDB log rotation
        Configuration of system constants and directoriesarrow
      • Filtering bot actionsDirectory of gender markers
      Custom Channelsarrow
    • Creating a Channel
        Pipelinesarrow
      • MessageScheduleListenerModerateStop
          Pipesarrow
        • HTTP RequestPackUnpackEventerSchedulerSelectorSQLStore SetStore GetLogResultError
      External Objects (Entities)Templating LanguageSending FilesPresets (Field Sets)DebuggingTechnical Limitations
      Platform maintenancearrow
    • Personnel requirementsPlatform maintenance processesPlatform updatingBackup and recoveryTransferring the platform to a new serverCreating, deleting, and populating tables for statistics in ClickHouseUsing the aktool utilityUsers and directories engaged by the platformPlatform service monitoringProcess and mailing monitoring via Prometheus
      Extraarrow
    • System page customizationSend Message IDClickHouse History Migration GuideInstructions for migrating history to ClickHouseUtility for importing push subscriptions to Firebase projectUtility for importing push subscriptions to Firebase projectENS: настройка интеграции
    Processing HTTP/HTTPS traffic
      Administrator APIarrow
      • Accounts admin apiarrow
        • Restricted accessarrow
        • Account Activation and DeactivationAccount Freeze and Unfreeze
        Get accounts listAdd a new accountDelete the account
        Account usersarrow
      • Update an Existing AccountAdd a new userDelete a userGet a list of usersSending a Welcome Email
        Nodesarrow
      • Synchronize node MTA configurationGet nodes listGet node MTA statusActivate node MTADeactivate node MTA
        Senders admin apiarrow
      • Create or update AKMTA senderGet AKMTA sender informationAssign account to senderGet senders listDelete senderRestore sender
          Sender queuearrow
        • Get sender queue informationHold sender queueRelease sender queueClear sender queue
        Virtual sendersarrow
      • Get virtual senders listGet virtual sender informationCreate virtual senderUpdate virtual senderClone virtual senderDelete virtual sender
    Documentation Archive
  • Custom Channels
  • Pipelines
  • Pipes
  • Eventer

Eventer

Eventer is a Pipe for registering channel events in the platform. It is used to record sending, delivery, non-delivery events, as well as to manage moderation and stopping of placement mailings.

Parameters​

FieldTypeRequiredDefaultDescription
event_typestringNo—Event type. Required for stop, moderate_pass, moderate_error. Not used for other event types
channel_idintNo—Numeric channel identifier. If not set, taken from the event context. Not required for stop, moderate_pass, moderate_error
action_typeintNo—Numeric event identifier within the channel (Event ID). Required for all event types except stop, moderate_pass, moderate_error
eventobjectYes—Event parameters (see below)

Event Parameters (event)​

FieldTypeRequiredDescription
send_message_idstringYesMessage identifier in the platform. Supports templating
timestringNoEvent time in RFC3339 format (e.g., 2024-05-15T10:30:00Z). If specified, the event is assigned this date instead of the current time
messagestringNoText message attached to the event. Supports templating. Useful for recording error text in a bounce: "message": "$error.code $error.message"
caution

In the Schedule Pipeline, $origin.send_message_id may be missing because $origin is replaced with the params.template value of the Scheduler pipe. In this case, send_message_id must be passed explicitly through the Scheduler pipe's template and accessed as $origin.<field_name>.

Possible Errors​

  • Template processing error in params.event.send_message_id
  • Invalid format of params.event.send_message_id

Examples​

Send Event Registration​

{
"id": 100,
"type": "event",
"params": {
"channel_id": 10001,
"action_type": 100021,
"event": {
"send_message_id": "$origin.send_message_id"
}
},
"outs": {
"error": 101
}
}

Stop Placement Mailing​

{
"id": 150,
"type": "event",
"params": {
"event_type": "stop",
"event": {
"send_message_id": "$origin.send_message_id"
}
}
}

Moderation Error​

{
"id": 18,
"type": "event",
"params": {
"event_type": "moderate_error",
"event": {
"send_message_id": "$origin.send_message_id"
}
},
"outs": {
"success": 19,
"error": 20
}
}

Recording Error in Bounce​

The message field allows saving the error text from a previous pipe (e.g., HTTP code and description from http_request) into the event:

{
"id": 4,
"type": "event",
"params": {
"channel_id": 10001,
"action_type": 100003,
"event": {
"send_message_id": "$origin.send_message_id",
"message": "$error.code $error.message"
}
}
}
Last updated on Jul 21, 2026
Previous
Unpack
Next
Scheduler
  • Parameters
    • Event Parameters (event)
  • Possible Errors
  • Examples
    • Send Event Registration
    • Stop Placement Mailing
    • Moderation Error
    • Recording Error in Bounce
© 2015 - 2026 Altcraft, LLC. All rights reserved.