Answered

Why isn't the response id available in the webhook payload?

  • 8 November 2022
  • 3 replies
  • 110 views
P

It seems rather odd to me that the response_id is not sent in the webhook payload.  Is this intentional, or am I missing something?


In my webhook, I want to save a local copy of the response and associate with its response_id so that I can also uses the responses API and not count any response twice.  I could use some other value, such as submitted_at to infer when a response is the same, but it seems cleaner to simply use the response_id.  Is there some reason that value is not sent in the webhooks payload?

icon

Best answer by Scot 8 November 2022, 22:27

View original

3 replies

Scot
Rank
Userlevel 3
Badge +3

Hi @plujon !

 

I can’t speak to why there isn’t a matching label for this token/id across api to webhook payload, but the token of a webhook payload should actually match to the API response_id, so you can cross-reference those hopefully! 😀

“I'm not superstitious, but I am a little stitious.”
P

Ah, silly me.  Yes, the token will do; thanks!

picsoung
Rank
Userlevel 7
Badge +5

Exactly like @Scot suggested the form_response.token should be the same as the response id.

For the longest time, we used to call it a “response token”, and we just kept it because of legacy.

Reply


Still need help?

Don't be shy and ask the community.

Ask your question here!
Community T&Cs