Deleting a link between entities

The request allows you to delete a link between two entities.

DELETE

https://api.tracker.yandex.net/v3/entities/<entity_type>/<entity_ID>/links

Query format

Before making a request, get permission to access the API.

To delete a link, use an HTTP DELETE request. The link will be deleted between the current entity (ID specified in the request <entity_ID>) and the entity whose ID is specified in the right parameter of the request.

DELETE /v3/entities/<entity_type>/<entity_ID>/links
Host: api.tracker.yandex.net
Authorization: OAuth <OAuth_token>
X-Org-ID or X-Cloud-Org-ID: <organization_ID>
Headers
  • Host: Address of the node that provides the API.

  • Authorization: Authorization token about these formats:

    • OAuth <OAuth_token>: For authorization using the OAuth 2.0 protocol. Learn more

    • Bearer <IAM_token>: For authorization using an IAM token, if a Yandex Cloud Organization organization is linked to Tracker. Learn more

  • X-Org-ID or X-Cloud-Org-ID: Organization ID.

    • Use the X-Org-ID header if a Tracker organization is linked to Yandex 360 for Business.

    • Use the X-Cloud-Org-ID header if a Tracker organization is linked to Yandex Cloud Organization.

    To get the organization ID, go to AdministrationOrganizations and copy the value from the ID field.

Resource
Parameter Description Data type
<entity_type> Entity type:
  • project
  • portfolio
  • goal
String
<entity_ID> Entity ID. To get the ID, see the entity list. You can use the id or shortId parameter as the ID. String
Request parameters

Required parameters

Parameter Description Data type
right ID of the entity whose link is deleted String

Example: Delete a link between entities

  • An HTTP DELETE method is used.
DELETE https://api.tracker.yandex.net/v3/entities/project/<project_ID>/links?right=<entity_ID>

Response format

If the request is successful, the API returns a response with code 200 OK.

If the request is processed incorrectly, the API returns a response with an error code:

400
One or more request parameters have an invalid value.
404
The requested object was not found. You may have specified an invalid object ID or key.
422
JSON validation error, the request is rejected.