I would like to get the CRM card ID at the webhook/Data fetch url end so that I can process request accourding to source card id and return json accourdingly. Currently we can get query string as following:
My first thought, @dennisedson and @EkramulHuq is that each Card is set up with it's own data fetch URL, so you should be able to pass along whatever you want to the URL. I haven't tried having the URL end in query params... try throwing a `?card_id=1234` at the end of your data fetch URL and see if that works?
But otherwise, depending on what you're using to manage your data fetch URL endpoint, you should be able to pass whatever you want into the URL string itself so that you can parse it out. We use node.js and express for everything, and it's fairly straightforward for us to pass in and pull out from the URL param.
Example would be: https://example.com/crm-extensions /{{card_id}} (https://example.com/crm-extensions/1235)
And then in your route logic, you would be able to parse the card id from the route param.
Also, I personally would go with a unique name, mostly because if you're like us and use multiple OAuth Apps to manage different environments (we have an OAuth App for local dev, dev, staging, and prod)then the CRM card IDs change per app. In that case, we usually pass in some identifier like:https://example.com/crm-extension/contact-ticketswhere "contact-tickets" is the string we're looking for in our route determine what data to return.
My first thought, @dennisedson and @EkramulHuq is that each Card is set up with it's own data fetch URL, so you should be able to pass along whatever you want to the URL. I haven't tried having the URL end in query params... try throwing a `?card_id=1234` at the end of your data fetch URL and see if that works?
But otherwise, depending on what you're using to manage your data fetch URL endpoint, you should be able to pass whatever you want into the URL string itself so that you can parse it out. We use node.js and express for everything, and it's fairly straightforward for us to pass in and pull out from the URL param.
Example would be: https://example.com/crm-extensions /{{card_id}} (https://example.com/crm-extensions/1235)
And then in your route logic, you would be able to parse the card id from the route param.
Also, I personally would go with a unique name, mostly because if you're like us and use multiple OAuth Apps to manage different environments (we have an OAuth App for local dev, dev, staging, and prod)then the CRM card IDs change per app. In that case, we usually pass in some identifier like:https://example.com/crm-extension/contact-ticketswhere "contact-tickets" is the string we're looking for in our route determine what data to return.
