Add one or more Library content items to one or more Sales Enablement profiles in the specified TeamSite. Use this operation to publish content into profile folders so that profile subscribers can access it.
Domain Terms
profileId / profileVersionId: Identifies the target Sales Enablement profile and the specific profile version where content will be referenced.
folderIds: One or more profile folders that should receive the content. Use root for the top-level folder of the profile, or a folder GUID for a nested folder.
contentId / versionId: Identifies the source Library content item and the specific content version to reference from the profile.
shouldSendNotification: When true, profile subscribers and followers receive a notification about the newly added content; when false, no notification is sent.
actionResultDetails: Per-content success or error status returned in the response; inspect this array to handle partial-success (207) cases.
Limits
At most 100 profile entries (actionDetails) per call.
At most 100 content entries across all profile entries per call.
Typical Flow
Resolve the target profile via the Sales Enablement profile APIs to obtain profileId and profileVersionId.
Identify the Library contentId and versionId for each content item to publish.
POST this endpoint with the action details; inspect actionResultDetails for per-item outcomes.
Recent Requests
Log in to see full request history
Time
Status
User Agent
Retrieving recent requests…
Loading…
Responses
400
Bad Request. The request body is invalid, required fields are missing, or limits are exceeded (for example more than 100 profile entries or 100 content entries).
401
Unauthorized. The request is missing a valid authentication token or the token has expired. For backward compatibility, clients should also handle equivalent auth failures returned as 403 in legacy environments.
403
Forbidden. The caller does not have the seismic.library.manage scope or lacks permission to publish content into the target profile. In some legacy environments, expired or missing authentication may also surface as 403; clients should handle both 401 and 403 for auth-related failures.
404
Not Found. The specified TeamSite, target profile, profile folder, or Library content could not be resolved.
500
Internal Server Error. The service failed while adding contents to the requested profiles.
Click Try It! to start a request and see the response here! Or choose an example:
application/json
200 - Example 1207 - Example 1400 - contentsEmpty400 - limitExceeded401 - Example 1403 - Example 1404 - Target profile or profile version does not exist404 - One or more Library content items could not be resolved500 - Example 1