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_ parameter is included).
Here is a quick demo of myself enriching our Twitter/X profile of https://twitter.com/Enrich Layer:
\$ curl --location ' platform?twitter_profile_ \ --header 'Accept: application/json' \ --header 'Authorization: Bearer \<API_KEY\>'
Here is the profile data:
\{ "public_identifier": "https://www.twitter.com/in/Enrich Layer", "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": "Enrich Layer", "last_name": null, "full_name": "Enrich Layer", "follower_count": 139, "occupation": null, "headline": null, "summary": "Enrich Layer 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 \}, , ... // 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 the platform member profile, and then returned profile data for that professional networks profile.