LinkedIn removes the location field from /v2/me and /v2/people: use geoLocation

AnnouncedAug 2026

EffectiveNot stated

PlatformLinkedIn

What changed

In the reminders of its August 2026 release notes (version 202608), LinkedIn says the top-level location field is being removed from /v2/me and /v2/people responses. Partners relying on it may begin to receive an empty or null value. The replacement, geoLocation, is already available on both endpoints. LinkedIn gives no final removal date, so the effective date is not stated.

What it means

Apps that read a member's location text (such as "San Francisco Bay Area") from the Profile API may start getting an empty or null value and need to switch to the geoLocation field.

Who is affected

Tools that call /v2/me or /v2/people and show or store the connected member's location, for example on a connected account card or in a CRM sync.

What to do

Request geoLocation with the geo~ projection instead of location, and handle an empty location value from now on.

What this means for you

Apps can ask LinkedIn for basic facts about your profile, like where you live. LinkedIn is taking away the old box that held your location as plain words. Apps that still read that old box may suddenly show nothing where your city used to be. Your profile itself does not change. Apps just have to read your location from a newer box instead.

The details

What goes away: the top-level location field in responses from GET /v2/me and GET /v2/people/(id:...). LinkedIn's example value is "San Francisco Bay Area".
When: listed under Reminders in the August 2026 release (version 202608). LinkedIn says partners "may begin receiving" an empty or null value and gives no cutoff date. These are /v2 endpoints, so the Linkedin-Version header does not protect you.
The replacement: geoLocation, already on both endpoints. Request it with the projection projection=(geoLocation(geo~,autoGenerated)) to get the display name in the same call, or resolve the geo URN with the Geo API.
autoGenerated: when true, LinkedIn generated the location and the member may not have confirmed it. When false, the member picked it.
Terms: the Profile API page notes that geoLocation uses Bing Maps location data, which comes with Microsoft's Bing Maps terms.

What to do next

Business owners: Nothing. If an app shows your LinkedIn location wrongly or not at all, tell the app's support.
Marketers and agencies: Nothing, unless a reporting or CRM tool fills a location column from LinkedIn profiles; check that it still does.
Developers: Search your code for the location field on /v2/me and /v2/people, switch to geoLocation(geo~,autoGenerated), and treat a missing value as normal.

Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.