POST /v4/leagues/{leagueId}/activitiesFeed/{activityId}/comments
POST
https://api.kickbase.com/v4/leagues/{leagueId}/activitiesFeed/{activityId}/comments
Endpoint
POST {{baseUrl}}/v4/leagues/:leagueId/activitiesFeed/:activityId/commentsAuthentication
Authorization: Bearer {{token}}{{token}} should be set in the active environment (e.g. Kickbase v4).401 Unauthorized.Path variables
leagueId ({{leagueId}}) — League identifier.activityId ({{activityId}}) — Activity-feed item identifier to comment on.Headers
Content-Type: application/jsonAccept: application/jsonRequest body
Schema
{
"comm": "string"
}comm — Comment text.Example
{
"comm": "quis consequat voluptate anim"
}Responses
Response shapes can vary. The examples below illustrate common patterns.
201 Created (success)
{
"id": "<commentId>",
"comm": "<comment text>",
"created": "2026-03-06T12:34:56.000Z",
"userId": "<userId>",
"activityId": "<activityId>"
}400 Bad Request (validation error)
{
"error": "bad_request",
"message": "Invalid request body"
}401 Unauthorized (missing/invalid token)
{
"error": "unauthorized",
"message": "Authentication required"
}404 Not Found
{
"error": "not_found",
"message": "League, activity, or resource not found"
}Notes
leagueId and activityId are valid and belong to the authenticated user’s accessible league.Request
Path Params
Header Params
Body Params application/json
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --globoff 'https://api.kickbase.com/v4/leagues//activitiesFeed//comments' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"comm": "quis consequat voluptate anim"
}'Response Response Example
{}