Get a specific comment on one entity (program, task, or request)

get

https://api.seismic.com/programs/v2/spaces/{spaceId}/nodes/{nodeId}/comments/{commentId}

Retrieves a single comment with complete details including content, author information, timestamps, and metadata.
This endpoint is useful for direct comment access, deep linking, and detailed comment display in user interfaces.

Key Features:

Retrieves complete comment details with all metadata
Includes author information and creation/modification timestamps
Validates user access permissions before returning comment data
Returns structured comment object suitable for UI display
Supports direct comment linking and reference resolution

Authorization Logic:

User must have a valid JWT token with viewing or management scopes
Token is valid for this operation
User must have access to the comment and its parent entity
User must have access to the space containing the entity

Usage Example:

Retrieve specific comment details for display in notification systems or direct comment references.

Path Params

spaceId

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".

nodeId

string

required

The unique identifier of the entity (program, task, or request) containing the comment. This entity must exist
within the specified space and be accessible to the authenticated user.

commentId

string

required

The unique identifier of the comment to retrieve. The comment must exist on the specified entity and be
accessible to the authenticated user.

Responses

200Comment retrieved successfully. Response includes the complete comment object with all metadata.

400Invalid request parameters. Common causes include malformed comment ID, node ID, or space ID.

401Authentication failed due to missing, invalid, or expired JWT token. Obtain a valid token with required permission scopes.

403Access denied due to insufficient permissions to access entity or perform the requested action. Contact your administrator for assistance.

404Entity not found. Verify the entity ID exists to ensure proper permissions are granted.

500Internal server error during entity retrieval, mutation, or deletion.