Webhook integration between Podio and Zoho people - podio

I'm trying to automate my workflow between Podio and Zoho People. For example, when an Employee is added in my HR app, I want to call the Zoho People API to add it there too.
However, I get stuck in the validation phase. I don't get what's the validation process needs to be? What the endpoint I must call? I don't have control over what the Zoho API returns, obviously.
I never worked with webhooks before so I'm probably missing something obvious.

Related

How to integrate Google business messaging through API

Problems:
I am unable to enable Business Messages API, Because "Business Messages API" is not showing API list, While i am going to enable the API through the
https://console.cloud.google.com/apis/dashboard
I want to use auth token, while hitting the API, but the document is saying use the service.json for the credentials. i am following these doc. I am using "Google\Client()" with Laravel application.
https://developers.google.com/business-communications/business-messages/guides/how-to/agents?method=api
I am following these steps:
Login with google business account in the Dashboard
App taking multiple permissions as I have attached the permissions list and taking the auth token.
Open the chat box for the Business.
So please guide me, where i am going wrong. What is correct way to implement this.
Requirement:
I want to create a custom chat box for google businesses, Where business owner will login into the web app and He can easily manage the multiple business chats in one dashboard.
As per your given information, you have to be a partner of Google. As per google documentation, you need to be a partner of google and then you can create the agent and can send and receive messages. You can integrate the business messages API by following this documentation:
https://developers.google.com/business-communications/business-messages/guides
In this process, you need to be a partner of Google. The complete process is given on the link. If you follow this link, then you can use their built-in libraries easily and can send messages easily.
So far the permission for API, it might not be found for you because you might have to take permission for the particular project that is registered on google and then you will see the business messages API and you can enable it and use it. The reason as per the basic step:
https://developers.google.com/my-business/content/basic-setup
Sometimes, you have to submit the request form to take the API access for particular APIs. Or Share how are you using that API.
If you do not find a form for business messages API then you can ask for the information from bm-support#google.com. they mostly respond on a working day.

Mailchimp Surveys - Webhooks or API?

Mailchimp seems to have "Surveys" -- which are nicely integrated (so it is claimed!) with their own database, so that the subscriber gets updated/added in the audience as appropriate when a survey is filled, etc.
I have a client who is interested in using these but also would like to integrate the survey response data into Salesforce.
I tried looking into Mailchimp API reference and cannot find anything related to surveys. Ideally, it would be best if they were supported by the Webhooks, since that is the functionality the client is interested in, however, I am open to using polling-based method if that's the only way available.
Thank you in advance!!

Check paypal donation thought API access

Reading almost the whole API reference of paypal, i am almost sure that they do not provide any kind of API method regarding donations. However i would like to check whether someone donates something to my paypal account and get some details of this transaction.
I thought of using the Activities Search REST API, however it was responding with -> "No permission for the requested operation" while i was testing it with my sandbox business account.
Anyone got any idea of how to claim this details? Do i missing something?
My last thought, was to use gmail API's to read the incoming emails that i am receiving (from paypal) when i got a donation, however i believe it's not a good solution, so its my last choice.

Podio API - webhooks insights

Since apparently you're not reachable for API questions via email, I guess I'd have to put all the questions in here since it would be tedious to create one for each of them.
So we're planning on creating a webhooks system for our integrations to create a better experience for our users. There are a few pieces that are missing for our end to support having a Podio integration that runs 100% on webhooks.
Support organization level webhooks instead at the space level.
Send full object payload in the webhooks push so we don't need to fetch the resource again. Or at least provide a delta of changes.
Have a secret token header that you send with each request so we can assure the authenticity of the data (that it's actually from Podio and it's not someone trying to hack our system).
Github does a great job with this: https://developer.github.com/webhooks/#delivery-headers.
Ability to unsubscribe from a webhook if the client revokes the OAuth credentials. Do you automatically delete that webhook or do we need to contact the user or you guys to get rid of it?
Trello for instance deletes all webhooks associated with a token if it's revoked or a second option is our server sends a 410 Gone back and the webhook, well you guessed it, it's gone.
Do you think something like this is feasible in the near future?
Thanks for your insights :)
Seems pretty valid point. Are there any particular org operations that you are interested to have webhooks for? Can you also describe some use-cases for org level webhooks?
Sending full object payload is pretty complicated because items in Podio can be extremely big and it might be not needed for webhook to get all details. That's why we keep it small and tiny and let Podio partners build own complicated solutions based on webhooks.
Secret token is not much needed if there is only item_id sent in webhook. Let's review it on item modified scenario.
1) User (or anything else) modifies item
2) item.modified webhook is triggered with item_id
3) 3rd party app receives webhook
4) 3rd party app makes a call to Podio API (if it's needed) and gets all required information from Podio API
So, if webhook request is fake, then Podio API will return same item details and nothing is affected. If you want to have some extra layer of security: why not making webhook URL unique and specific to webhook? Then only Podio will know which URL to use to trigger this webhook.
Ability to unsubscribe from a webhook if the client revokes the OAuth credentials.
Sorry, but I don't understand your question. Can you please re-phrase it as new StackOverflow question?

How to "settle" AVS transactions via the SOAP API?

I integrated our site with Cybersource using the SOAP API.
Everything works perfectly but I am trying to see if I am able to settle an AVS transaction via the API. In the Cybersource Business Center you are able to view an AVS transaction. There is the ability to "settle" the transaction from that view.
How can I use this via the SOAP API?
The reason I need this is I'm building the Cybersource integration with our CRM so our staff doesn't have to log into 2 different systems to do their work. The thinking is that they would process all transactions on the CRM with the integration. Since I would be saving transaction data on my end as well, I am able to create custom reports for them. One of them is an AVS report in which it was requested that they have the ability to "settle" the transaction just like how they are able to from the Cybersource Business Center.
I found this document helpful in creating my own SOAP API integration:
http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SO_API/Credit_Cards_SO_API.pdf
The fieldnames for CyberSource's "Simple Order API" are the same as the ones you need to use for the "SOAP Toolkit API". So, in order to settle a an authorization that failed its AVS check, you simply need to provide the authorization request ID to settle it like you would any other authorization. Do this in the ccCaptureService_authRequestID field along with all of the other required fields. As long as the authorization in question has an authorization code, you should be able to settle it.