GuidesAPI DocsChangelogMy AppsSeismic Exchange
API Docs

Create a new content request

post
https://api.seismic.com/programs/v2/spaces//requests

Creates a new content request within the specified space to track work items and content production workflows.
The request will be associated with the authenticated user as the creator and can include assignees, priorities,
custom properties, and associations to programs or content.

Key Features:

  • Creates requests with complete metadata including title, description, and dates
  • Supports assigning requests to specific users for workflow management
  • Enables setting priorities (critical, high, medium, low) for request tracking
  • Allows associating requests with content items only
  • Validates assignee user IDs to ensure valid assignments
  • Returns complete request object with generated IDs and timestamps

Authorization Logic:

  1. User must have a valid JWT token with program management scopes
  2. User must have permission to create requests in the specified space
  3. Assignee user must exist and be valid within the tenant

Usage Example:

Create a content request for a marketing campaign with assigned team members and associated program tracking.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length between 7 and 22

The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

Body Params

The request data

string | null

User identifier of the person to assign this new request to upon creation. This is a stable string ID in base64url or GUID format representing the user account (example u7YtMp2kQxRvN9LmW4HzAg). Set to null to create an unassigned request that can be assigned later. The specified user must have access to the space and appropriate permissions to work on requests. Assigning a request during creation triggers notifications to the assignee and sets the assignerId field to track who made the initial assignment. Use this field to immediately route new requests to the appropriate team member or to create a request pool for later assignment.

string

Human-readable title or name for the new request that concisely describes what is being requested. This is a required field that will be displayed prominently in request lists, dashboards, and notifications. Use clear, descriptive titles such as Content Review for Q4 Campaign or New Sales Deck Design Request to help users quickly identify requests without needing to read detailed notes. The title should summarize the request purpose in a few words and is searchable for request discovery and filtering. Choose titles that remain meaningful when viewed in isolation from other request details.

string | null

Status schema identifier that defines the workflow and available status transitions for this new request. This is a stable string ID in base64url format referencing a StatusSchema resource (example statusSchema_abc123xyz). Set to null to use the default status schema for the request type in the space. The status schema determines which status values are valid and which transitions are allowed between statuses. Choose a status schema that matches your approval workflow requirements, such as simple two-step approval or complex multi-stage review processes. The schema must exist in the space and be of type request to be used for request creation.

string | null

Program identifier to link this new request to a parent program for portfolio management and organizational hierarchy. This is a stable string ID in base64url format (example xH75yTE6xmz6MUvcTDxIRi). Set to null if the request is not part of any program. Associating requests with programs enables program-level reporting, resource allocation tracking, and strategic initiative management. The specified program must exist in the same space as the request. Use this field to group related requests under common initiatives or projects, enabling program managers to monitor all requests contributing to specific business goals.

string | null
enum

Priority classification indicating the urgency and importance of this new request. Valid values are low (routine, non-urgent work), medium (normal priority with standard turnaround), high (important, requiring expedited handling), or critical (urgent, demanding immediate attention). Set to null to create a request without explicit priority, which may default to medium in some UI contexts. Priority affects how requests are sorted in work queues, which notifications are triggered, and how resources are allocated. Choose priority levels that align with organizational SLAs and escalation policies to ensure appropriate handling and response times.

Allowed:
date-time | null

Target start date and time when work on this new request should begin, in ISO 8601 format with timezone (example 2025-01-20T00:00:00Z). Set to null if no start date has been planned at creation time. Use this field to schedule request work, coordinate with resource availability, and establish timeline expectations with stakeholders. The planned start date helps with capacity planning and ensures requests are tackled at the appropriate time. Can be combined with plannedEndDate or plannedDuration to define the complete expected timeline for request completion.

date-time | null

Target completion date and time when this new request should be finished, in ISO 8601 format with timezone (example 2025-01-25T00:00:00Z). Set to null if no end date has been planned at creation time. Use this field to establish deadlines, set stakeholder expectations, and enable deadline-based prioritization and reporting. The planned end date creates accountability for timely completion and helps identify potential scheduling conflicts or resource constraints. Essential for time-sensitive requests with fixed delivery requirements or external dependencies.

int32 | null

Expected duration for completing this new request measured in calendar days (example 5 for a five-day turnaround). Set to null if duration has not been estimated at creation time. Use this field for workload estimation, capacity planning, and setting realistic completion expectations. When combined with a planned start date, the system can calculate the expected end date automatically. Planned duration helps identify resource bottlenecks, balance workloads across team members, and improve estimation accuracy over time by comparing planned versus actual durations. Typical values range from 1 day for simple requests to 30+ days for complex initiatives requiring multiple reviews or approvals.

customProperties
array of objects | null

List of custom properties

customProperties
contentRefs
array of objects | null

List of content references (DocCenter and Workspace associations)

contentRefs
associations
array of objects | null

List of associations (Library content)

associations
formRef

Optional reference to a request form template to apply when creating this request, establishing which custom properties, validation rules, and field layouts should be used. Provide a FormReference object containing the form's unique identifier (formId) to create a form-based request with predefined structure. When supplied, the form determines which custom properties are required, their allowed values, display order, and validation constraints. Leave null to create an unstructured request without form template requirements. Use form references to standardize request intake processes, ensure consistent data collection, and guide users through structured request submission workflows. Obtain valid form IDs from GET /spaces/{spaceId}/forms endpoint before creating form-based requests.

Responses

Updated 8 days ago

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 8 days ago