Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guideDeveloper guideAdmin guide
Company siteHelp center
English
  • Русский
  • English
v74
  • v74
  • v73
  • v72
Login
  • User documentation
  • FAQ
  • Altcraft glossary
  • Profiles and databases
  • Communication channels
    • Email channel
    • Push channel
      • Mobile Push
        • Settings & implementation
        • Integrate your app with Altcraft
          • Providers: push message structure
          • Processing and adding a subscription
          • Event registration
      • Web push
    • SMS channel
    • Creating mailing from scratch
    • Communication Channels Workflow
    • Руководство: SMS-рассылка через УТШ
    • Руководство: push-рассылка через сервис от "Согласие"
  • Segmentation
  • Message templates
  • Mailings
  • Campaigns
  • Automation scenarios
  • Market
  • Loyalty programs
  • Reports and analytics
  • Integrations
  • Weblayers
  • Settings
  • API requests: where to start
  • Changelog
  • library
  • Communication channels
  • Push channel
  • Mobile Push
  • Integrate your app with Altcraft
  • Event registration
Documentation for version v74

Event registration

There are two ways to register delivery events and open push messages in Altcraft MP:

  1. Directly from the app.
  2. Through a third-party service.

Registering events directly from the app​

By default, when sending a push message, the "hub_link" object is sent in the payload:

{
"hub_link" : {
"ack" : "http://your.domain.com/api/v1.1/pushes/crypto_post_events?/2ab9162159..." ,
"open" : "http://your.domain.com/api/v1.1/pushes/crypto_post_events?/555fbe0b9..."
}
}

The application must execute a GET request using the rack and open links to register the delivery and open the push, respectively.

Registering events through a third-party service​

caution

This method requires the presence of Extra UID in the user data of the push message (configurable on request).

The application informs the third-party service about the event and at the same time transfers Extra UID from the push.

The gateway must send this event to Altcraft MP via API.

URL​

Method: POST

https://example.com/api/v1.1/pushes/post_events

Request parameters​

ParameterTypeExampleRequiredDescription
tokenstring"abcdefghijklmnqrstuvwxyz"YesAPI token
eventsint1 — delivered
2 — opened
3 — delivered and opened
YesEvent
uidstring"uid"YesComes along with a push message from Altcraft in the Data payload.

Request example​

{
"token" : "abcdefghijklmnqrstuvwxyz" ,
"events" : 1,
"uid" : "e|2_4S_4HFn8RDhhmA|w4HFn8RPDFUi_2_4S_S_3___6.2NvyN8Hb67wmzJshM_6BuFTt|ios-apns"
}

Response example​

{
"error" : 0,
"error_text" : "Successful operation"
}

Response parameters​

ParameterTypeDescription
errorintError code
error_textstringError text
Last updated on Jul 24, 2023
Previous
Processing and adding a subscription
Next
Web push
  • Registering events directly from the app
  • Registering events through a third-party service
    • URL
    • Request parameters
    • Request example
    • Response example
    • Response parameters
© 2015 - 2025 Altcraft, LLC. All rights reserved.