X-Forwarded-For API functionality has stopped working

Options
rotholtz
rotholtz Posts: 3 ✭✭
in All Discussions

Hi folks,

I'm trying to leverage the 6Sense API for company detail identification to surface some information. I was able to create a proof of concept a couple months ago, that leveraged the X-Forwardedd-For header (only seen that referenced here for 6Sense: https://support.6sense.com/knowledge-base/360037629753-faq-dynamic-html5-ads/).

Was this functionality intentionally disabled? If so, why and are there are other workarounds? I'm trying to ensure that the client IP address is being passed forward to the request from a middleware request before the page is fully rendered to provide a personalized page without an FOC.

Thanks,

Ben

Tagged:

Comments

  • Rahul
    Rahul Posts: 10 6senser

    Hello Ben,

    Welcome to REVCITY!!

    I apologize for the issue you are experiencing with the Company Details API

    Early last month 6sense made a change in our ongoing effort to ensure our customer's data is secured. The change that was made was to require a company's API token to be whitelisted in order to use the x-forwarded-for header.

    Before we rolled out this change we did extensive analysis to ensure we whitelist tokens for customers/partners who are using x-forwarded-for header implementation. It might be that your token was missed.

    Could you please submit a Support request so that our team will be able to help with whitelisting your token?

    Thanks and have a nice day!

    Rahul Agarwal

  • rotholtz
    rotholtz Posts: 3 ✭✭

    Thanks, @Rahul - I've updated the support ticket I've created with the right token to get that whitelisted.

    Appreciate the response! May be worth adding a note to the Knowledge Base article to provide that as a path for folks looking to do that.

    Thanks again,

    Ben

  • rotholtz
    rotholtz Posts: 3 ✭✭

    Hey @Rahul - I'm communicating with one of the support technicians on a ticket, and they are indicating that it is the IP address that needs to be whitelisted vs. the API token.

    How do you expect that to work, insofar as having the client IP be the lookup method, but only being able to whitelist a single IP address? I'm not sure if that solves my expected use case.

    This was possible and doable before, but seems to now be a broken functionality within 6Sense.

    Thanks,

    Ben

  • Rahul
    Rahul Posts: 10 6senser

    Hello Ben,

    We need the token to be whitelisted. Our team member has responded on the support ticket and we are working internally to get this working for you.


    Best,

    Rahul Agarwal

Categories