Source
Message logs, events & webhooks — found from sitemap — SocketLabs Email Delivery
Checked for SocketLabs Email Delivery on 17 Nov 2026
- Page
- https://help.socketlabs.com/docs/event-webhooks-data-attributes
- Checked
- 17 Nov 2026, 15:04 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f479d58a205623bb62d28926ee25a5c4650fb635fd57ff7e86bd1239928fa119
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Webhook event types Report an error
“Current responses include: "Queued", "Deferred", "Delivered", "Failed", "Tracking", or "Complaint"”
-
Webhook data fields Report an error
“The data fields that may be included currently included are: Type DateTime ServerID SubaccountID IPPoolID SecretKey Address FromAddress Subject MessageSize DeferralCode Response LocalIp Reason BounceStatus DiagnosticCode FailureCode FailureType RemoteMta TrackingType UserAgent ClientIp Url Tag FblType From To Length MailingId MessageId Data Meta Tags”
-
Webhook future fields Report an error
“It is important that your applications can handle additional undocumented values in the PostBody as we will add additional attributes in future versions of this webhook.”
-
Datetime format Report an error
“DateTime -> STRING This is a timestamp for the event in ISO 8601 format.”
-
Failure types Report an error
“FailureType -> STRING Current responses include: "Permanent", "Temporary", "Suppressed"”
-
Permanent failure suppression Report an error
“Permanent failure: The message failed to be delivered and SocketLabs believes the error indicates the address will NOT be able to accept future messages. Assuming the Suppression List feature is enabled, the recipient address will be added to prevent future delivery attempts.”
-
Temporary failure no suppression Report an error
“Temporary failure: The message failed to be delivered and the error does NOT indicate that the recipient address is permanently invalid. SocketLabs will NOT add the recipient address to a suppression list to prevent future delivery attempts.”
-
Failure code format Report an error
“FailureCode -> INT The Failure Code is a 4 digit ID that we provide as a more human friendly interpretation explaining why a message failed to be delivered.”
-
Tracking type values Report an error
“TrackingType -> INT Current responses include: 0, 1, 2 This is how open, click, and unsubscribe events are delineated within the tracking events category: 0: Click 1: Open 2: Unsubscribe”
-
Mailingid aggregated reporting Report an error
“MailingID -> STRING An optional identifier that can be added to messages that will persist across all aspects of reporting data. The MailingID is meant to be used to categorize batches or groups of messages. SocketLabs will provide aggregated reporting data across this field.”
-
Messageid no aggregated reporting Report an error
“MessageID -> STRING An optional identifier that can be added to messages that will persist across all aspects of reporting data. The MessageID is designed to be unique for each message. SocketLabs does not provide aggregated reporting statistics on this field.”
-
Async event enrichment window Report an error
“Data enrichment for asynchronous events only occurs for messages processed by SocketLabs within the last 16 days.”
-
Async metadata toggle Report an error
“To enable data enrichment for asynchronous events, slide the toggle on for 'Include metadata and tags' when configuring your endpoint.”
-
URL tag limits Report an error
“Valid characters for a tag include 0-9, A-Z, a-z, and hyphen. Tags can be up to 64 characters in length.”
-
Fbl type values Report an error
“FBLType -> STRING Current response is only: “abuse””
-
Localip mapping Report an error
“The SocketLabs IP range uses the first two octets of 142.0, so if the IP address provided is 10.50 176.1, than the public facing address that performed delivery will be 142.0.176.1”
-
Deferral code beta Report an error
“This is a BETA field intended to help make deferrals easier to understand to humans and less technical users.”
-
Subaccountid v1 v2 Report an error
“SocketLabs Simple (V1) customers should rely on the ServerID field for identifying the SocketLabs resources associated with a message. SocketLabs Complex (V2) customers should rely on SubaccountID and IPPoolID.”
Scores citing this record
- The Agency Lead Message logs, events & webhooks
- The Data Protection Officer Message logs, events & webhooks
- The Shop Operator Message logs, events & webhooks
- The Platform Engineer Deliverability & sender reputation
- The Platform Engineer Message logs, events & webhooks
- The SaaS Developer Deliverability & sender reputation
- The SaaS Developer Message logs, events & webhooks
- The Skeptic Deliverability & sender reputation
- The Skeptic Message logs, events & webhooks