Every component in a workspace, from applications and environments to ad-hoc test runs, has a unique ID known as a mabl resource ID.
In requests
Most endpoints require providing a mabl resource IDs in the request. For example, the get application endpoint uses the application ID as a path param:
https://api.mabl.com/applications/{application-id}
In responses
Many endpoints return mabl resource IDs in the response. For example, the get test metadata endpoint returns the workspace ID, user IDs, and the test ID in the response:
{
"workspace_id": "{workspace-id}",
"created_time": 0,
"last_updated_time": 0,
"last_updated_by_id": "{user-id}",
"id": "{test-id}",
"created_by_id": "{user-id}",...
For more information on the different types of mabl resource IDs and where you can obtain them, check out this article.