Add contents to profiles

post

https://api.seismic.com/cm/v1/teamSites/{teamSiteId}/items/referencedProfiles

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

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

teamSiteId

string

required

^(?:1|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$

Identifier of the teamsite context for the request. Depending on API behavior, it may be a GUID-formatted value or a documented special value such as 1.

Body Params

Request body samples

{
    "requestId": "65aad570-bc2e-4398-8d23-c3eafb27acf3",
    "shouldSendNotification": false,
    "actionDetails": [
        {
            "profileId": "1454656e-6412-4c2b-a926-3ddd85397f26",
            "profileVersionId": "909e3fa7-7966-462d-9e56-859966d0b1c7",
            "folderIds": [
                "root"
            ],
            "contents": [
                {
                    "contentId": "6604995b-65c8-460c-abf4-2c0512292aeb",
                    "versionId": "8d8d89bc-3803-409d-9937-2b76f80bafd6"
                }
            ]
        }
    ]
}

Request payload for adding Library content items to one or more Sales Enablement profiles. Up to 100 profile entries and 100 content entries are allowed per call.

requestId

uuid

^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$

Caller-supplied identifier echoed back in the response to correlate asynchronous results with the originating request.

shouldSendNotification

boolean

When true, profile subscribers and followers are notified about the newly added content; when false or omitted, no notification is sent.

actionDetails

array of objects

required

One entry per target profile, specifying the profile, target folders, and the content versions to publish into that profile.

actionDetails*

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

Request body samples

200All content items were successfully added to the specified profiles.

207Partial success. At least one content item encountered an error while being added to a profile. Inspect actionResultDetails for per-item status.

400Bad 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).

401Unauthorized. 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.

403Forbidden. 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.

404Not Found. The specified TeamSite, target profile, profile folder, or Library content could not be resolved.

500Internal Server Error. The service failed while adding contents to the requested profiles.