Legacy Webhooks
You'll notice there are two different groups of webhooks available to you when creating your app.
This first group of events are powered by our Legacy webhooks services, known internally as Webhooks v1. As the name suggests, this was our first pass at allowing apps to subscribe to events within Seismic.
Interaction Session Summary (Legacy)
Q&A
Should I be using these legacy webhooks or not?
Yes. This is the only way to receive the data for these events at this time...
with 1 exception: Don't use livesend_summary, instead use interaction_session_summary
Do I need to be concerned about changing over to newer versions of these webhooks in the future?
TBD, but hopefully not. We are planning a seamless upgrade to these webhooks that will convert them to our newer (and better) webhook service. This is under development now. Unless there ends up being a significant, unforeseen blocker developers should be OK to use these events and should not notice a difference after the upgrade.
Are there any downsides to these webhooks?
- Structure - The payload for these webhooks differs from our modern webhooks. Specifically they are all missing the webhook parent object.
- Speed - While we typically see events flowing through these webhooks within a few minutes, there have been many instances of these taking several hours to come through.
- No new features - As we continue to upgrade our new webhooks services, new features and capabilities will not be available to these webhooks until they are upgraded to the new service. An example would be Webhooks filtering.
What is different for the "_enriched" versions of these events?
These events contain an object under the recipients object called "context". This contains data from your CRM to provide additional context about the recipient.
This first group of events are powered by our Legacy webhooks services, known internally as Webhooks v1. As the name suggests, this was our first pass at allowing apps to subscribe to events within Seismic.
Interaction Session Summary (Legacy)
Q&A
Should I be using these legacy webhooks or not?
Yes. This is the only way to receive the data for these events at this time...
with 1 exception: Don't use livesend_summary, instead use interaction_session_summary
Do I need to be concerned about changing over to newer versions of these webhooks in the future?
TBD, but hopefully not. We are planning a seamless upgrade to these webhooks that will convert them to our newer (and better) webhook service. This is under development now. Unless there ends up being a significant, unforeseen blocker developers should be OK to use these events and should not notice a difference after the upgrade.
Are there any downsides to these webhooks?
- Structure - The payload for these webhooks differs from our modern webhooks. Specifically they are all missing the webhook parent object.
- Speed - While we typically see events flowing through these webhooks within a few minutes, there have been many instances of these taking several hours to come through.
- No new features - As we continue to upgrade our new webhooks services, new features and capabilities will not be available to these webhooks until they are upgraded to the new service. An example would be Webhooks filtering.
What is different for the "_enriched" versions of these events?
These events contain an object under the recipients object called "context". This contains data from your CRM to provide additional context about the recipient.
Updated 3 days ago