Dynamic Signal API
Dynamic Signal API as documented publicly: 94 operations. Contract generated from the documentation by API Evangelist (2026-10-24); not the provider's own document.
Operations 94
PATCH
/scim/v2/Groups/{groupId}
Update an audience in the Program with partial changes using SCIM PatchOp.
#
GET
/scim/v2/ResourceTypes
Returns available Resource Types configuration as per SCIM 2.0 Specification. Additional references: SCIM 2.0 Protocol Spec Section 4SCIM 2.0 Spec Section 8.5
#
GET
/scim/v2/ResourceTypes/{resourceId}
Returns the requested Resource Type SCIM 2.0 Specification. Additional references: SCIM 2.0 Protocol Spec Section 4SCIM 2.0 Spec Section 8.5
#
GET
/scim/v2/Roles
Returns a list of all accessible roles in the actor's program. Only primary roles are currently available.
#
GET
/scim/v2/Schemas
Returns a list of the schemas in use by this SCIM API. Implements SCIM 2.0 Specification.
#
GET
/scim/v2/Schemas/{schemaId}
Returns the specified schema used by this SCIM API. Implements SCIM 2.0 specification.
#
GET
/scim/v2/ServiceProviderConfig
Returns the Schema Provider configuration as per SCIM 2.0 Specification. Additional references: SCIM 2.0 Spc Section 8.5SCIM 2.0 Spec Section 8.7.2
#
GET
/scim/v2/Users
This endpoint allows you to retrieve information about all or some of the users stored in the Firstup application and adheres to the SCIM 2.0 Section: 4.1
#
POST
/scim/v2/Users
Create and provision a new user. The request should include any properties to be set on the user, and leaving any out will leave those values blank, or will use defaults. New users
#
DELETE
/scim/v2/Users/{userId}
Permanently remove a User and their details from the authenticated program.
#
PATCH
/scim/v2/Users/{userId}
Update a user in the program with partial changes using SCIM PatchOp.
#
PUT
/scim/v2/Users/{userId}
To update or replace user information, ensure that your request includes a comprehensive set of user attributes.
#
GET
/v2/Groups/JobReport/{jobid}
The calls to the POST, PUT or PATCH `Groups Managements` endpoints trigger a series of asynchronous jobs to create or update the list of the Group's members.
#
POST
/v2/Users/{userId}/forget
Permanently remove a User and their details from the authenticated program.
#
PUT
/v2/assistant/notifications/acknowledge_all
Mark all program user's notifications acknowledged.
#
PUT
/v2/assistant/notifications/{notificationId}/acknowledge
Mark the program user's notification acknowledged.
#
POST
/v2/channels
Creates new topic in the program. A topic holds campaigns and users, organizing content for user consumption.
#
GET
/v2/channels/{channelId}/followers
Returns a list of all users who follow the topic, and allows for pagination of the records. Response body is an array of records.
#
GET
/v2/comment_aliases
Returns the comment aliases the authenticated user is allowed to comment as, scoped to their program and roles.
#
GET
/v2/content
Returns a list of content records and allows for sorting, filtering, and pagination of the records. This list can be used to pass into a topic. Response body is an array of records
#
POST
/v2/content
Create a new content item and select what topics will include the content. The new content will be created in the “draft” state. This endpoint only creates the post.
#
GET
/v2/content/{contentId}
Read an existing content record. Returns a single record by identifier or by the content UUID.
#
PUT
/v2/content/{contentId}
Update an existing content record. Content can be updated in any state, but some states have different validations.
#
PUT
/v2/content/{contentId}/archive
Archive an existing content post. Transition the content state from any state directly to "archived". Response body contains the latest version of the content record.
#
PUT
/v2/content/{contentId}/draft
Transition the content state of an existing content post to draft.
#
GET
/v2/content/{contentId}/reach/unique_user_count
Fetch the content reach, the unique user count for audiences, topics, and both.
#
POST
/v2/feed/posts/{contentId}/acknowledge
Acknowledges a feed post for a scoped user. The post must be visible to the user or a 404 Not Found response will be returned; for example, if the content is published to a targete
#
PUT
/v2/feed/posts/{contentId}/bookmark
Creates a “bookmark” engagement of a specific feed post for a scoped user.
#
DELETE
/v2/feed/posts/{contentId}/comments/{commentId}
Allows an authenticated user to delete a comment or reply they authored.
#
GET
/v2/feed/posts/{contentId}/comments/{commentId}/replies
List the replies to a comment on a content post.
#
PUT
/v2/feed/posts/{contentId}/comments/{commentId}/report
Creates a Report for a specific comment (or reply) to a post for a scoped user.
#
POST
/v2/feed/posts/{contentId}/comments/{commentId}/{postNumber}/replies
Create a reply to a comment on a content post.
#
GET
/v2/feed/posts/{contentId}/engagement
Displays the user’s engagements related to a single feed post, including a timestamp for each type of engagement.
#
PUT
/v2/feed/posts/{contentId}/like
Creates a "like" engagement of a specific feed post for a scoped user.
#
GET
/v2/feed/posts/{contentId}/rendered
Provides the rendered content for a single post in a user’s feed.
#
PUT
/v2/feed/posts/{contentId}/report
Creates a Report for a specific feed post for a scoped user.
#
GET
/v2/feed/posts/{contentId}/share/trackable_url
Get the trackable URL for a feed post for a scoped user.
#
PUT
/v2/notification_center/notifications/{notificationId}/read
Mark the program user's notification read.
#
GET
/v2/settings/user_generated_content
Returns which attachment types (images, videos, files, links) users may attach when submitting user generated content in your program.
#
PATCH
/v2/settings/user_generated_content
Toggles which attachment types (images, videos, files, links) users may attach when submitting user generated content in your program.
#
GET
/v2/ugc/audiences
Returns a paginated list of the audiences available to the authenticated user for targeting User Generated Content.
#
GET
/v2/ugc/contents
Returns a paginated list of the User Generated Content items submitted by the authenticated user in their program.
#
POST
/v2/ugc/contents
Creates a new User Generated Content item authored by the authenticated user. The item may be created as a `draft` or submitted directly as `published`, depending on the `publicati
#
PUT
/v2/ugc/contents/{id}
Updates the attributes of a User Generated Content item. Set `publication_state` to `published` to publish a draft, or to `archived` to archive the item (there is no separate destr
#
POST
/v2/ugc/contents/{id}/copy
Creates a new draft User Generated Content item that duplicates the attributes of the given item.
#
GET
/v2/ugc/contents/{id}/preview
Returns a rendered preview of the User Generated Content item, including its current moderation status, so a consuming application can display it prior to publication.
#
GET
/v2/ugc/metadata
Returns configuration and metadata (such as submission limits and available options) needed by a consuming application to build a User Generated Content submission experience.
#
GET
/v2/webhooks/subscriptions
Fetches multiple subscription records at a time, and can be paginated using cursor pagination.
#
POST
/v2/webhooks/subscriptions
Subscriptions are configurations that define what events you want to receive webhooks for.
#
DELETE
/v2/webhooks/subscriptions/{subscriptionId}
Deactivate a webhook subscription and remove the record permanently.
#
PUT
/v2/webhooks/subscriptions/{subscriptionId}
After creation, subscriptions can be updated to change what events are subscribed to, what url to send the payloads to, and other settings such as whether the subscription is activ
#
POST
/v2/webhooks/subscriptions/{subscriptionId}/ping
More information about testing webhook subscriptions is available on the Testing Webhook Subscriptions page.
#