Home & Global Resources
Blueprint Assess
Getting Started
Settings & Administration
Analyze
Overview
Scenario Demonstration
Features
Process Details
Blueprint Migrate
Getting Started
The Blueprint User Interface
Change Your Password
Open a Project
Organize Artifacts and Assets
Close a Project
Status Indicators
Jobs
Exporting from Source RPA Tools
How to export a UiPath Automation Project from UiPath Orchestrator
How to export .bprelease files from Blue Prism
Blue Prism VBO Matching on Import
How to Export .zip files from Automation A360 Control Room
Importing
Exporting
RPA Export from Blueprint
Variable Prefixing
Why We Create Multiple Similar Subflows During Migration
Understanding Wrapper Flows in Power Automate Desktop
Setting up defaultRunDotNetScriptReferences
AsEnumerable Support
XmlDocument Support
Bulk Reimport/Recalculate
Metabot Migration - Best Practices
Artifacts Management
Base Artifact Types
Creating and Managing Artifacts
View and Edit Artifacts in the Utility Panel
Concurrent User Activity in Artifacts (Steal Lock)
Using Descendants View
Global Actions
Rules
Introduction to Rules
Using Rules
Using Rules CSV
Common Procedures
Custom Action Mapping
Reuse Mapping to Power Automate Desktop
Manual Reuse
TODO, Error, and Robin Mapping
Script Mapping
Variable Name Dependency Mapping
Variable Renaming and Initialization
DLL/Method Invocation Mapping
Unresolved References
AA Metabots
Work Queues Mapping
Rules Wizard
Solutions & Best Practices
Working with Migration Output in Power Automate Desktop (PAD)
Blueprism to PAD Migration Output Details
UiPath to PAD Migration Output Details
AA to PAD Migration Output Details
RPA Value-Mapping Assessments
Why Choose Blueprint Cloud vs. On Premise ?
Setting up SAP for RPA
API & Developer Resources
REST API Request Header and Parameters
REST API Request Body and Parameters
REST API - Listing Artifacts in the Request Body
REST API - Defining an Artifact in the Request Body
REST API - Defining a Comment in the Request Body
REST API - Defining a Reply in the Request Body
REST API - Defining a Trace in the Request Body
REST API - Filter Parameter
REST API - Defining a User in the Request Body
REST API Requests
REST API - Add Attachment to Subartifact Request
REST API - Get Artifact Request
REST API - Add Traces Request
REST API - Get Project by Id Request
REST API - Update Custom Choice-Property Type Request
REST API - Publish Comments Request
REST API - Publish Artifact Request
REST API - Update Comment Request
REST API - Delete User Request
REST API - Add Comment Request
REST API - Close Review Request
REST API - Get Discussion Status Request
REST API - Update Reply Request
REST API - Get Attachment Request
REST API - Delete Comment Request
REST API - Create Project Request
REST API - Get Group Request
REST API - Rate Comment Request
REST API - Get Child Artifacts of Artifact Request
REST API - Discard Artifacts Request
REST API - List Artifacts Request
REST API - Rate Reply Request
REST API - Move Artifact Request
REST API - Delete Attachment Request
REST API - List Projects Request
REST API - Get Blueprint Product Version Request
REST API - Update Standard Choice Property Request
REST API - Get Review Request
REST API - Reply to Comment Request
REST API - Update User Request
REST API - Get Collection Request
REST API - Delete Artifact Request
REST API - List Collections Request
REST API - Authenticate Request
REST API - Get Artifact Type Request
REST API - List Artifact Types Request
REST API - Delete Reply Request
REST API - Get Root Artifacts of Project Request
REST API - Add Attachment Request
REST API - Create User Request
REST API - List Reviews Request
REST API - List Groups Request
REST API - Get User Request
REST API - Delete Traces Request
REST API - Add Artifact Request
REST API - List Users Request
REST API - Get Artifact Image Request
REST API - Update Artifacts Request
REST API - List Unpublished Artifacts Request
REST API HTTP Methods
REST API - HTTP HEAD Method
REST API - HTTP DELETE Method
REST API - HTTP GET Method
REST API - HTTP POST Method
REST API HTTP Status Codes
REST API - HTTP PATCH Method
Blueprint REST API
REST API Quick Start Example
REST API Requests and Responses
REST API Security and Authentication
REST API Known Issues & Constraints
REST API Requests
REST API Resources
REST API - Defining an ALM Job in the Request Body
Dashboards & Reports
Statistics Report Options
Using Scope and View
Statistics Dashboard
Statistics Reports
Applications Dashboard
Applications Report
Estimator Dashboard
Estimator Reports
How to Change the Main Process Label for Estimations
Bulk Reporting
Call Trees
Blueprint + PowerBI Dashboards
How to Create Microsoft Power Automate RPA Migration Estimates with Blueprint
Licensing
Settings & Administration
Overview of Blueprint Settings
System Reports
System Reports
License and Activity Reporting
User List
Project Activity
User Roles
Artifact Map
Project Usage
User Activity Report
Audit Log
System Logs
User Management
Creating and Managing Users
Creating and Managing Groups
Creating and Managing Instance Administrator Roles
Creating and Managing Project Administrator Roles
RPA Management
Microsoft 365 Authentication Settings
Integration Reporting
Migrate - Import/Export
Migrate - Dashboards
Migrate Settings
Advanced Settings
Projects
Installation
Blueprint Installation Guide
System Requirements
Supported Third-Party Components
Azure App Registration (Power Automate Export)
Release Notes
- All Categories
- Blueprint Migrate
- API & Developer Resources
- REST API Request Body and Parameters
- REST API - Defining a Trace in the Request Body
REST API - Defining a Trace in the Request Body
How to define a trace in the request body using the Blueprint API.

The following services require you to define/specify a trace in the request body:
In the request body you must specify:
- The other artifact in the trace relationship (for Add Traces and Delete Traces requests)
OR - The new parent trace (for Change Parent Trace)
Parameters
You must specify a Traces
element first to contain any individual traces you want to specify by using the Trace
element. Here is an example in XML:
<Traces>
<Trace>
</Trace>
<Trace>
</Trace>
</Traces>
The following parameters can be specified within each <Trace> element you are specifying:
ArtifactId
: The ID of the artifact whose trace relationship is being defined.SubArtifactId
: The ID of the sub-artifact whose trace relationship is being defined.ProjectId
: The ID of the project of the artifact whose trace relationship is being defined.Type
: Defines the type of trace. The valid values are the following:Manual
: Only applicable when adding or deleting a trace.Parent
: Only applicable when moving an artifact.
Direction
: The direction of the trace. The valid values are the following:To
: From the artifact in the URI request to the artifact in the request body.From
: To the artifact in the URI request from the artifact in the request body.TwoWay
: The artifacts have a bi-directional trace.
IsSuspect
: Marks the trace as suspect.
Depending on the request, you are adding a trace relationship to, removing a relationship from, or establishing a new child-parent relationship with the artifact in the request body. In each context, some parameters are mandatory, while others are optional or ignored:
- Adding a Trace:
- Required:
direction
,type
(set to Manual), one ofartifactId
orsubArtifactId
(the other is optional) - Optional:
projectId
andisSuspect
- Required:
- Deleting a Trace:
- Required:
type
(set to Manual), one ofartifactId
orsubArtifactId
(the other is optional),direction
(if the query is using thereconcileWithTwoWay
parameter, which is set to true) - Optional:
projectId
- Ignored:
isSuspect
- Required:
- Changing a Parent Trace:
- Required:
type
(set to Parent), one ofartifactId
orprojectId
The artifact in the request body must belong to the same project as the artifact in the URI request. - Ignored: All other properties are ignored.
- Required:
Examples
AddTrace Example
Here is an example of a request body in XML format:
<?xml version="1.0" ?>
<Traces xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.blueprintsys.com/blueprint/api/v1">
<Trace>
<ArtifactId>888020</ArtifactId>
<Direction>To</Direction>
<IsSuspect>false</IsSuspect>
<ProjectId>847739</ProjectId>
<Type>Manual</Type>
</Trace>
</Traces>
Here is an example of a request body in JSON format:
[
{
"Type": "Manual",
"ProjectId": 123456,
"ArtifactId": 123,
"IsSuspect": false
},
{
"Type": "Manual",
"ProjectId": 123456,
"ArtifactId": 456,
"IsSuspect": false
},
{
"Type": "Manual",
"ProjectId": 789,
"ArtifactId": 789,
"SubArtifactId": 789,
"IsSuspect": false
}
]
Delete Traces Example
Here is an example of a request body in XML format:
<?xml version="1.0" ?>
<Traces xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.blueprintsys.com/blueprint/api/v1">
<Trace>
<ArtifactId>843925</ArtifactId>
<Type>Manual</Type>
</Trace>
</Traces>
Here is an example of a request body in JSON format:
[
{
"Type": "Manual",
"ArtifactId": 847750
}
]
ChangeParentTrace Example
Here is an example of a request body in XML format:
<?xml version="1.0" ?>
<Traces xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.blueprintsys.com/blueprint/api/v1">
<Trace>
<ArtifactId>999666</ArtifactId>
<Type>Parent</Type>
</Trace>
</Traces>
Here is an example of a request body in JSON format:
[
{
"Type": "Parent",
"ArtifactId": 999666
}
]
How did we do?
REST API - Defining a Reply in the Request Body
REST API - Filter Parameter