- Schema
- Authentication
- Response Format
- Pagination
- Request by ID
- Filters
- Includes
- Optional Fields
- Ordering
- Searching
- Errors
- Rate Limits
- Participations
- Project Accounting Records
- Status Reports
- Workspace Allocations
- Workspace Baselines
- Workspace Groups
- Workspace Invoice Preferences
- Workspace Resource Skills
- Workspace Resources
- getFetching a list of Workspace Resources
- postCreating a new Workspace Resource
- postCreating Allocations from Scheduled Hours for Resources
- getFetching a single Workspace Resource
- putUpdating an existing Workspace Resource
- delDeleting an existing Workspace Resource
- postCreating Allocations from Scheduled Hours for Resources
- Workspace Status Changes
- Workspaces
- getFetching a list of Workspaces
- postCreating a new Workspace
- getFetching a single Workspace
- putUpdating an existing Workspace
- delDeleting an existing Workspace
- putApply a Project Template to an existing Workspace
- postCreating a Workspace Invitation
- getFetch permissions in a Workspace
- putToggle expense approval setting
- putToggle time approval setting
- putUnarchive Workspace with Approvals
- Assignments
- Daily Scheduled Hours (Story Allocation Days)
- getFetching a list of Daily Scheduled Hours (Story Allocation Days)
- postCreating a new Daily Scheduled Hours (Story Allocation Day)
- delDelete multiple Daily Scheduled Hours (Story Allocation Days)
- getFetching a single Daily Scheduled Hours (Story Allocation Day)
- putUpdating an existing Daily Scheduled Hours (Story Allocation Day)
- delDeleting an existing Daily Scheduled Hours (Story Allocation Day)
- Followers
- Stories
- Story Dependencies
- Story State Changes
- Story Tasks
Fetching a list of Story Follows
By default, you will get all story follows that you are permitted to see. If you are an Administrator, you will see every story follow on your account. Otherwise you will see every story follow in projects in which you are participating.
Bad Request
Unauthorized request
Forbidden request
Page Not Found
Unprocessable Entity
Service is unavailable
- curl
- Ruby
- JavaScript
- Python
- C#
- Go
- 400
- 401
- 403
- 404
- 422
- 503
{- "errors": [
- {
- "type": "string",
- "message": "string"
}
]
}Following a story
Bad Request
Unauthorized request
Forbidden request
Page Not Found
Unprocessable Entity
Service is unavailable
- Payload
- curl
- Ruby
- JavaScript
- Python
- C#
- Go
{- "story_follow": {
- "story_id": 0,
- "user_id": 0
}
}- 400
- 401
- 403
- 404
- 422
- 503
{- "errors": [
- {
- "type": "string",
- "message": "string"
}
]
}Retrieving a single Story Follow
Bad Request
Unauthorized request
Forbidden request
Page Not Found
Unprocessable Entity
Service is unavailable
- curl
- Ruby
- JavaScript
- Python
- C#
- Go
- 400
- 401
- 403
- 404
- 422
- 503
{- "errors": [
- {
- "type": "string",
- "message": "string"
}
]
}Unfollowing a story
The response will contain no content and an HTTP 204 status code if the request was successful, or a standard Kantata OX error message explaining why the object could not be deleted.
object has been deleted.
Bad Request
Unauthorized request
Forbidden request
Page Not Found
Unprocessable Entity
Service is unavailable
- curl
- Ruby
- JavaScript
- Python
- C#
- Go
- 400
- 401
- 403
- 404
- 422
- 503
{- "errors": [
- {
- "type": "string",
- "message": "string"
}
]
}