Information on Content Marketing Platform (CMP) API endpoints that are available in Collaboration.
Collaboration helps Optimizely Experimentation customers manage experiment and campaign ideation, planning, and hypothesis creation.
Certain endpoints are available for Content Marketing Platform (CMP) and Collaboration. These endpoints include the following callout in the API documentation:
Note
This API endpoint is available for hypotheses in Collaboration.
Tasks
endpoints
Tasks
endpointsThe endpoints listed for Tasks
are available for Collaboration. A task
in CMP is equal to a hypothesis
in Collaboration at the application level and data level. Because of this, you can use the Tasks
endpoints to interact with hypotheses in Collaboration just as you would with tasks in CMP. See the Collaboration documentation on Hypotheses.
These APIs let you retrieve task details, manage custom fields, and handle assets like comments and attachments
Tasks
Tasks
Use these endpoints to create, update, and manage hypotheses in Collaboration. See the following Task
endpoint reference documentation:
- GET /tasks
- GET /tasks/{task_id}/assets/{asset_id}/drafts
- POST /tasks
- PUT /tasks/{task_id}/assets/{asset_id}/drafts/{draft_id}/brand-compliance
- GET /tasks/{id}
- PATCH /tasks/{id}
- GET /tasks/{id}/brief
Custom fields endpoints
These endpoints let you interact with custom fields associated with a hypothesis. You can retrieve available fields, update values for specific hypotheses, and customize how data is structured within a hypothesis. See the following custom-fields
endpoint reference documentation:
- GET tasks/{id}/custom-fields
- GET /tasks/{task_id}/custom-fields/{custom_field_id}
- PATCH /tasks/{task_id}/custom-fields/{custom_field_id}
- GET /tasks/{task_id}/custom-fields/{custom_field_id}/choices
Fields endpoints
Use these endpoints to manage standard fields within a hypothesis. You can retrieve, create, update, and delete fields to ensure the hypothesis contains all necessary information. See the following fields
endpoint reference documentation:
- GET tasks/{task_id}/fields
- POST tasks/{task_id}/fields
- PUT tasks/{taks_id}/fields/{field_id}
- DELETE tasks/{task_id}/fields/{field_id}
Steps endpoints
Steps represent distinct phases within a hypothesis workflow. These endpoints let you retrieve, update, and manage steps, sub-steps, external work, and related comments to track progress effectively. See the following steps
endpoint reference documentation:
- GET /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}
- PATCH /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}
- GET /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/external-work
- PATCH /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/external-work
- GET /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/comments
- POST /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/comments
- GET /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/comments/{comment_id}
- PATCH /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/comments/{comment_id}
- DELETE /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/comments/{comment_id}
Assets endpoints
Assets are files or structured content attached to a hypothesis. These endpoints let you upload, retrieve, and manage different types of assets, including comments and metadata. See Manage hypotheses. See the following assets
endpoint reference documentation:
- GET /tasks/{id}/assets
- POST /tasks/{id}/assets
- POST /tasks/{task_id}/assets/{asset_id}/drafts
- GET /tasks/{task_id}/assets/{asset_id}/drafts
- GET /tasks/{task_id}/assets/{asset_id}/comments
- POST /tasks/{task_id}/assets/{asset_id}/comments
- GET /tasks/{task_id}/assets/{asset_id}/fields
- PUT tasks/{task_id}/assets/{asset_id}/fields
Attachments endpoints
These enpoints let you retrieve various types of attachments related to a hypothesis, such as articles, images, videos, and raw files. You can also post comments on attachments to facilitate collaboration. See Manage hypotheses. See the following endpoint reference documentation:
- GET /tasks/{id}/attachments
- GET /tasks/{task_id}/articles/{article_id}
- GET /tasks/{task_id}/images/{image_id}
- GET /tasks/{task_id}/videos/{video_id}
- GET /tasks/{task_id}/raw-files/{raw_file_id}
- POST /tasks/{task_id}/comments
Structured content endpoints
These endpoints let you create, retrieve, update, and delete structured content associated with hypotheses. These endpoints facilitate the management of content in a structured manner, ensuring consistency and ease of collaboration across teams. See the following structured-contents
endpoint reference documentation:
- POST /tasks/{task_id}/structured-contents
- GET /tasks/{task_id}/structured-contents/{content_id}
- PATCH /tasks/{task_id}/structured-contents/{content_id}
- DELETE /tasks/{task_id}/structured-contents/{content_id}
- POST /tasks/{task_id}/structured-contents/{content_id}/drafts
Campaigns
endpoints
Campaigns
endpointsUse these endpoints to create, update, and manage campaigns in Collaboration. A campaign represents a collection of related hypotheses and assets, helping teams organize and track work across multiple initiatives. These APIs let you retrieve campaign details, manage campaign-related fields, and handle attachments or comments.
See the following Campaign
endpoint reference documentation:
- GET /campaigns
- POST /campaigns
- GET /campaigns/{id}
- PATCH /campaigns/{id}
- POST /campaigns/{id}/comments
- GET campaigns/{id}/fields
- GET /campaigns/{id}/brief
- POST /campaigns/{id}/attachments
- PUT /campaigns/{campaign_id}/fields/{field_id}
Templates
endpoints
Templates
endpointsThese endpoints let you retrieve details about campaign templates, which provide predefined structures for organizing hypotheses within campaigns. Templates help standardize workflows by ensuring consistent field configurations and processes.
See the following Templates
endpoint reference documentation:
Work Requests
endpoints
Work Requests
endpointsWork requests serve as structured intake forms for new hypotheses or campaigns. These endpoints let you create, update, and manage work requests, retrieve related assets, and handle comments and approvals. Work requests ensure all necessary information is collected before a hypothesis or campaign is initiated.
See the following Work Requests
endpoint reference documentation:
- GET /work-requests
- POST /work-requests
- GET /work-requests/{id}
- PATCH /work-requests/{id}
- GET /work-requests/{id}/comments
- POST /work-requests/{id}/comments
- GET /work-requests/{work_request_id}/comments/{comment_id}
- POST /work-requests/{id}/attachments
- DELETE /work-requests/{work_request_id}/attachments/{attachment_id}
- POST /work-requests/{id}/creative-assets
- DELETE /work-requests/{work_request_id}/creative-assets/{creative_asset_id}
- GET /work-requests/{id}/approved-assets
- POST /work-requests/{id}/campaigns
- POST /work-requests/{id}/tasks
- GET /work-requests/{id}/related-resources
- PUT /work-requests/{work_request_id}/form-fields/{form_field_identifier}
Settings
endpoints
Settings
endpointsThese endpoints let you retrieve and modify Collaboration settings to customize how the system operates. Organizational settings may include default configurations, permissions, or workflow rules that apply across hypotheses, campaigns, and work requests.
See the following Settings
endpoint reference documentation:
Workflows
endpoints
Workflows
endpointsUse these endpoints to retrieve details about Hypothesis workflows in Collaboration. A workflow defines the steps a hypothesis must go through, including approvals, reviews, and completion stages. Workflows help teams standardize processes and track the progress of hypotheses.
See the following Workflows
endpoint reference documentation:
Fields
endpoints
Fields
endpointsThese endpoints let you Manage fields in Collaboration. Fields define structured data points for hypotheses, campaigns, and other objects, letting you capture relevant details. You can retrieve, create, update, and delete fields and field choices to customize data entry.
See the following Fields
endpoint reference documentation: