Can we mark some variables in journey webhook as required? Will it work while sending API requests through journey webhook?
{ "type": "object", "properties": { "name": { "type": "string" }, "age": { "type": "integer" } }, "required": ["name"]}
Can we mark some variables in journey webhook as required? Will it work while sending API requests through journey webhook?
{ "type": "object", "properties": { "name": { "type": "string" }, "age": { "type": "integer" } }, "required": ["name"]}
From @Heather Spoelstra Hi there,
While there's not currently an option in Iterable to designate webhook fields as required, we can absolutely log a feature request for this ask. If you'd like to create a support ticket by emailing support@iterable.com with more details about your use case, they may be able to come up with a workaround for you. Offhand I'm thinking that if you're using this in a journey webhook, you can have a journey filter that first checks for the existence of that field, but with more details our support team can offer a more personalized recommendation.
**This response has been manually added from our former community platform to ensure the full conversation is captured. Please note that the date of this post will appear significantly later than the original.
Already have an account? Login
Not a customer? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.