Skip to main content
7-Bedrock
April 15, 2026
Question

Lock tracker via REST API

  • April 15, 2026
  • 3 replies
  • 42 views

In the UI a tracker can be locked by a user for exclusive access, but this is not possible via REST API.

Use case:

The items of a tracker are modified outside the UI, e.g. to generate a item skeleton. This operation must be performed atomic, i.e. it must be prevented that someone else modifies any item of the tracker while the external modifications are done.

3 replies

BKampling_SAI
12-Amethyst
May 12, 2026

@M a r k u S A tracker can be locked via the REST API:
 

 

7-Bedrock
May 13, 2026

@BKampling_SAI :Unfortunatelly, it is a different lock. 

The Codebeamer UI and documentation are a mess.

There seems to be at least three different “locks”:

  1. Tracker configuration lock
    This is what your screenshot shows
  2. Tracker lock
    This enables “exclusive” access to the tracker items and can be obtained via (but there is no REST API):
  3. Tracker Item lock
    This is done, when you enter the “deailed view” of an item and prevents, that during this time any field of the item is modified by someone else.
    This can also be done via REST API:

 

 

BKampling_SAI
12-Amethyst
May 15, 2026

@M a r k u S , thanks for the clarification.
Would you be willing to provide some additional context around what you are trying to accomplish?

7-Bedrock
May 18, 2026

We do have external Generators that create the basic structure of some trackers. During the run of a Generator we must ensure, that no user will modify any items of the tracker - i.e. we need something like a “exclusive access” for a tracker.