Announcing Fresh Facebook and X/Twitter Profile Data in Person Profile Endpoint

In the heels of our recent announcement of the all-new Customer API, I am happy to share that we will now return fresh profile data for Facebook or Twitter/X profiles via the Person Profile Endpoint (provided that the use_cache=if-recent parameter is included).

Here is a quick demo of myself enriching our Twitter/X profile of https://twitter.com/proxycurl:

$ curl --location 'https://nubela.co/proxycurl/api/v2/linkedin?twitter_profile_url=https%3A%2F%2Ftwitter.com%2Fproxycurl&use_cache=if-recent' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <API_KEY>'

Here is the profile data:

{
    "public_identifier": "https://www.twitter.com/in/proxycurl",
    "profile_pic_url": "https://pbs.twimg.com/profile_images/1394135315959353345/y4KnR6HH_normal.jpg",
    "background_cover_image_url": "https://pbs.twimg.com/profile_banners/1390489918120488960/1679300989",
    "first_name": "Proxycurl",
    "last_name": null,
    "full_name": "Proxycurl",
    "follower_count": 139,
    "occupation": null,
    "headline": null,
    "summary": "Proxycurl is a B2B enrichment API to fetch fresh and rich data on People and Companies 🚀",
    "country": null,
    "country_full_name": null,
    "city": "",
    "state": null,
    "experiences": null,
    "education": null,
    "languages": null,
    "accomplishment_organisations": null,
    "accomplishment_publications": null,
    "accomplishment_honors_awards": null,
    "accomplishment_patents": null,
    "accomplishment_courses": null,
    "accomplishment_projects": null,
    "accomplishment_test_scores": null,
    "volunteer_work": null,
    "certifications": null,
    "connections": null,
    "people_also_viewed": [
        {
            "link": "https://www.twitter.com/in/RuangHealing",
            "name": "Ruang Healing",
            "summary": null,
            "location": null
        },
        {
            "link": "https://www.twitter.com/in/ReceinAja",
            "name": "Recein Aja",
            "summary": "Apa aja ada. | kerjasama WA 📩 https://t.co/jQCywcTUTo | Submit DM",
            "location": "Indonesia"
        }, ... // truncated
    ],
    "recommendations": null,
    "activities": null,
    "similarly_named_profiles": null,
    "articles": null,
    "groups": null,
    "skills": null,
    "inferred_salary": null,
    "gender": null,
    "birth_date": null,
    "industry": null,
    "extra": null,
    "interests": [],
    "personal_emails": [],
    "personal_numbers": []
}

What is different?

We first announced support for a user to provide for a facebook_profile_url or a twitter_profile_url input in the Person Profile Endpoint in August 2023. Until this change, what we did was that when a Facebook or Twitter/X profile URL is provided, we tried to match it to a corresponding LinkedIn member profile, and then returned profile data for that LinkedIn profile.

The problem was that:

• not everyone on Twitter/X/Facebook has a LinkedIn profile
• we were not able to match a lot of Twitter/X/Facebook profiles to their LinkedIn profiles

For these cases for which we were not able to match a LinkedIn profile, we had to return an error of 404 -- which was just not good user experience.

With this update, we will now be able to enrich all profiles with fresh publicly available data even if we are not able to match a Twitter/X/Facebook profile to a LinkedIn profile.

Give it a spin!

Throw in your personal Facebook or Twitter/X profile and see how our Person Profile Endpoint handles it! Do not be surprised if we return more data than what you have publicly available because we do mix and match data across sources.

If you have any questions at all, send us an email at [email protected]!