How to use Webhook with OAuth token? | Community
Skip to main content
Devendra_Chauha
Devendra_Chauha
Level 2
May 23, 2019
Question

How to use Webhook with OAuth token?

  • May 23, 2019
  • 3 replies
  • 7607 views

How to use Webhook with OAuth token for JSON Exchange?

Do we need to create two Webhooks, First to get Authentication Token and Second to Get data from the service and exchanging the token in every call? Or it is possible with one webhook?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Jay_Jiang
Jay_Jiang
Level 10
May 23, 2019

Write your own endpoint to auth, get the data and return the data to marketo

Devendra_Chauha
Devendra_ChauhaAuthor
Level 2
May 23, 2019

So mean create a new service layer(custom code) between Marketo Webhook and Third party service?

SanfordWhiteman
SanfordWhiteman
Level 10
May 23, 2019
So mean create a new service layer(custom code) between Marketo Webhook and Third party service?

Of course.

Your 3rd-party service has not been designed to be called via webhook: it's not a webhook-compatible endpoint, and you should assume that was deliberate.

SanfordWhiteman
SanfordWhiteman
Level 10
May 23, 2019

Webhooks aren't designed to be used this way. They are intended to be single requests.

You should use a webhook gateway (a stateless endpoint that internally manages OAuth without exposing anything like that to the caller).

You may try to populate a lead field with the access_token. But I consider this terrible design and not acceptable in a professional environment.

    Devendra_Chauha
    Devendra_ChauhaAuthor
    Level 2
    May 23, 2019

    @Sanford Whiteman‌ - Thanks for reply, But it will not resolve my issue.

    Webhooks are stateless, so they will never save token for next service call, So OAuth is seems not possible, we need to send every time uid/pwd with the service call? That what you are suggesting here?

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    May 23, 2019

    Thanks for reply, But it will not resolve my issue.

    Of course it will. You're not understanding the answer.

    Webhooks themselves do not (by design) maintain state across invocations.

    That has nothing to do with whether the service they're calling maintains internal state.For example, if you use a webhook to call a service, and that service queries a database, it's natural (in fact good design) for it to keep alive a pool of database connections. The platform that makes the initial HTTP request has no idea about the connection pool. The service is internally stateful. The webhook invocations are stateless.

    Likewise, if you need to call a service that in turn calls an OAuth-protected service, you may cache the access_token for as long as you want.  The webhook doesn't need to, and shouldn't need to, know about it.

    Devendra_Chauha
    Devendra_ChauhaAuthor
    Level 2
    May 24, 2019

    Thanks  @Jay Jiyang and @Sanford Whiteman, your answer helped.

    Terms & ConditionsAccessibility statement

    Loading footer...