Here's what's new with the TeamForge 21.0 REST APIs as compared to TeamForge 20.3.
GET /fields/{trackerId}/parentfields
—API description changed in Swagger API docs.GET /approval-requests/summary
- Removed the “403” response code from Swagger API docs.
- Added 401 response code to the Swagger API docs.
- Added a token validation check.
GET /projects/{projectId}/teams/tree
—Removed theOffset
andCount
parameters as they are not required.PATCH /packages/{packageid}
—Added the 304 response code to Swagger API docs.POST /files/chunks/{fileStorageId}
—Removed 201 response code from Swagger API docs.- Removed 403 response code from File storage REST APIs as they do not perform RBAC validations.
GET /users/myself/groups
- Removed the “403” response code from the API’s swagger documentation.
- Added a token validation check.
GET /groups
—Updated the Swagger API docs to have 400 as the response code forInvalid sort by column name
.PATCH /appconfiguration
- API checks if there is a change in name, value, or application. Returns the 304 response code if it finds no changes.
- Returns a message,
Invalid Input
, if name, value, or application is empty.
- Updated Swagger API docs for the following APIs, These APIs return a 400 response code when you pass an invalid column name to sort by.
GET /projects/{projectId}/repositories
GET /repositories
GET /servers/{serverId}/repositories
- Updated Swagger API docs for the following APIs. These APIs return a 400 response code when you pass an invalid column name to sort by.
GET /projects/{projectid}/subproject
GET /projects
- Removed the Delivery Info API used to show Continuum data in TeamForge.
PATCH /documents/{docfolderid}/defaultreviewers
—Added input validations to check if the given user ID is valid or not.- Added a user friendly error message for the
com.fasterxml.jackson.core.JsonParseException
exception (for response code 400). GET /objects/{objectid}/permissions
—Removed the “403” response code from Swagger API docs.PATCH /clients/{id}/clientSecret
- Removed the “304” response code from Swagger API docs.
- Updated the Swagger API docs—returns 200 response code if the client secret is updated successfully.
- Removed 500 response code from Swagger API docs for the IDP Configuration APIs.
Related Links
- TeamForge
- TeamForge Baselines
- TeamForge Baselines API Documentation
- TeamForge Webconnect (also known as Webhooks-based Event Broker—WEBR)
- TeamForge WEBR API Documentation