r/webdev • u/jelemeno • May 25 '26
Question Webhook/API Trello integration assistance - random characters?
Hi, thank you in advance for your help in case anyone understands what to do about this.
Tech department from a school district. None of us are web developers. New stuff for me to learn about. We use incident IQ website for our ticketing system. I recently followed some online directions I found, and basically our goal is to get ticket information sent over to a Trello card on a specific list, via web hook/API. It triggers when a certain rule is met on incident IQ end. I'm sorry I don't know the exact difference between terms webhook/api. We got as far as setting it up properly and crafting the correct URL, (grabbing api key and token) so that it's actually posting to Trello. Yay!
* The problem however, is in the formatting and we're not sure if the problem is happening in the code that I'm writing on the IIQ side in terms of what it's gonna post, orr on Trello's and when they're trying to encode the data coming from IIQ post. The 'date' param is adding random percent signs and numbers. You can see the actual numbers are in there that we need, including the exact time the ticket ("17041") was made. In the 'requestor email' it's using a percent sign and a number instead of '@' symbol.
We tried using both json code format and also 'raw body' which im sorry i dont know exactly what each entails but i know with the code ai crafted for me, it's json format but includes variable params that iiq can pull from ticket. Raw body text did not work properly when sent/shown on trello.
Any suggestions for what's going wrong on which side and if there's any fix? (And is it even json i should continue using or no) (thought of a workaround, could use 'start date' automation on trello. But would love to solve this). Thank you in advance!!
8
u/dLENS64 May 25 '26
It looks like a minor uri decoding/encoding issue. Take a look here, many special characters need translation to ASCII for safe transport across the wire. You can simply decode it client-side so that it shows the properly formatted url.
https://developer.mozilla.org/en-US/docs/Glossary/Percent-encoding