How to Post Leads to Buyers Who Require OAuth 2.0

OAuth 2.0 is the industry-standard protocol for authorization. Modern web services will use this protocol to validate web requests are coming from a legitimate source. Typically these systems will require two separate web requests in order to submit the lead, one call to get an access token, and another web request to submit the lead information with the access token collected from the previous web request.  

The Access Token is required in order to submit the lead. This endpoint is typically dedicated to receiving access tokens only.  Follow the steps below to set up your access token endpoint:

1. Navigate to the Buyer Contract Card
2. Click on the Delivery Method Tab
3. Paste the Ping URL of the Access Token Endpoint
4. Click the Save button
5. Click Add  button in the Response Section
6. Add the Text and Interpret As
7. Click the Save button
8. Click in the Session ID field and Map the Regex statement to match the Access Token
9. Click the Save button to save changes

Once you have completed step 1 above, the delivery method will have access to use the #ping_session_id# token as a Post Header. Follow the steps below: 

1. Navigate to the Buyer Contract Card
2. Click on the Delivery Method tab
3. Paste the Post URL of the End Point that Accepts the leads and access token
4. Click the Save button
5. Click the Add button on the Responses tab
6. Add the Text and Interpret As option
7. Click Update to save changes
8. Click on the Post Headers
9. Click the Add button to add a post header
10. Enter the Header Name
11. Enter the Header value as #ping_session_id# 
12. Click Update to save changes

In order for the ping to occur you need to enable the offer level setting Ping First. Follow the steps below to enable Ping First: 

1. Navigate to the Offer Card
2. Click on the Lead Gen tab
3. Enable the Ping First setting
4. Click the Save button to save changes