Skip to content
Last updated

2026-04-10

Changed Endpoints

For You

Feed posts: new for_you feed option.

The GET /v2/feed/posts endpoint now supports for_you as a valid value for the name query parameter.

This allows callers to request the user’s personalized “For You” feed through the existing Feed Posts endpoint.

This endpoint is in the Feeds section. It requires oauth2_as_a_user with the required scope feeds.read.

Optional profile user targeting

The profile feed endpoints now support an optional user_id query parameter. When provided, the endpoint returns profile information for the specified user. When omitted, the endpoint defaults to the authenticated user.

These endpoints are in the Feeds section. They require oauth2_as_a_user with the required scope feeds.read.

Endpoints changed:

GET /v2/feed/profile/submitted

GET /v2/feed/profile/channels

Schema Change

SCIM user pronouns

The Scim.User.SocialChorusExtension schema now supports the pronouns string attribute.

This enables SCIM user records to include a user’s pronouns through the Firstup SocialChorus user extension. The value is nullable.

This impacts SCIM user create, read, update, and patch workflows where the SocialChorus user extension is used.

SchemaAdded attribute
Scim.User.SocialChorusExtensionpronouns

Example

{
  "urn:SocialChorus:1.0:User": {
    "pronouns": "they/them"
  }
}

Removed Endpoint

Bookmarked profile feed endpoint removed

The GET /v2/feed/profile/bookmarked endpoint has been removed from the OpenAPI specification.

Bookmarked feed content should now be requested through GET /v2/feed/posts?name=bookmarked.