The DQE One API is the backend API exposed by the DQE One package for Salesforce. The Custom UI Management endpoints on this page reset and import the rules that drive the package's embedded custom UI for a given session.
Different from most One endpoints: both endpoints on this page authenticate with a standard Bearer JWT in the Authorization header (Authorization: Bearer {JWT_TOKEN}), not the DQE-Authorization API-key header used by most other DQE One API endpoints. See Authentication & Session for how this token is issued.
Send a JSON body to this endpoint with the Authorization header set to a Bearer token.
Different from most One endpoints: this endpoint (and its sibling, customUI/importRules) authenticates with a standard Bearer JWT in the Authorization header (Authorization: Bearer {JWT_TOKEN}), not the DQE-Authorization API-key header used by most other DQE One API endpoints. See Authentication & Session for how this token is issued.
{DOMAIN} is the domain of the server where your organization's own instance of the DQE One backend is installed — since this backend runs in your own infrastructure, this value is determined by your deployment, not issued by DQE.
using var client = new HttpClient();
var json = "{\"uuidToken\":\"550e8400-e29b-41d4-a716-446655440000\"}";
var content = new StringContent(json, Encoding.UTF8, "application/json");
using var request = new HttpRequestMessage(HttpMethod.Post, "https://{DOMAIN}/customUI/resetRules");
request.Headers.Add("Authorization", "Bearer {JWT_TOKEN}");
request.Content = content;
var response = await client.SendAsync(request);
var body = await response.Content.ReadAsStringAsync();
Console.WriteLine(body);
All fields are sent as a single JSON request body.
Note on Mandatory/Optional: the source OpenAPI specification does not declare a required array for this request body (only the body as a whole is marked required). The field below is shown as Mandatory based on this project's documentation convention — confirm actual optionality with DQE engineering before publishing.
Field
Description
Type
Mand / Opt
uuidToken
Identifier of the custom UI session token to reset the rules for — the same uuidToken value returned by customUI/createTokenSession (see Authentication & Session).
String
Mandatory
Response
Returns a JSON object confirming the outcome of the reset operation.
Key
Description
Type
status
Outcome status of the reset operation.
String
Response example
Example reset response
{
"status": "success"
}
The source specification gives no example value for this schema. The value above is an illustrative placeholder only.
Errors
The source specification does not define any error responses (4xx/5xx) for this endpoint — only the 200 success response is documented. Confirm actual error behavior with DQE engineering before publishing.
Test the API
Click the button below to test this endpoint live in your browser.
Open console
Import Rules - DQE One API
Imports a custom UI rules payload into a given custom UI session.
Send a JSON body to this endpoint with the Authorization header set to a Bearer token.
Different from most One endpoints: this endpoint (and its sibling, customUI/resetRules) authenticates with a standard Bearer JWT in the Authorization header (Authorization: Bearer {JWT_TOKEN}), not the DQE-Authorization API-key header used by most other DQE One API endpoints. See Authentication & Session for how this token is issued.
{DOMAIN} is the domain of the server where your organization's own instance of the DQE One backend is installed — since this backend runs in your own infrastructure, this value is determined by your deployment, not issued by DQE.
using var client = new HttpClient();
var json = "{\"uuidToken\":\"550e8400-e29b-41d4-a716-446655440000\",\"importRules\":\"{RULES_PAYLOAD}\"}";
var content = new StringContent(json, Encoding.UTF8, "application/json");
using var request = new HttpRequestMessage(HttpMethod.Post, "https://{DOMAIN}/customUI/importRules");
request.Headers.Add("Authorization", "Bearer {JWT_TOKEN}");
request.Content = content;
var response = await client.SendAsync(request);
var body = await response.Content.ReadAsStringAsync();
Console.WriteLine(body);
All fields are sent as a single JSON request body.
Note on Mandatory/Optional: the source OpenAPI specification does not declare a required array for this request body (only the body as a whole is marked required). All fields below are shown as Mandatory based on this project's documentation convention — confirm actual optionality with DQE engineering before publishing.
Field
Description
Type
Mand / Opt
uuidToken
Identifier of the custom UI session token to import the rules into — the same uuidToken value returned by customUI/createTokenSession (see Authentication & Session).
String
Mandatory
importRules
The custom UI rules payload to import.
The source specification does not define the expected format of this payload — described generically here pending confirmation from DQE engineering.
String
Mandatory
Response
Returns a JSON object confirming the outcome of the import operation.
Key
Description
Type
status
Outcome status of the import operation.
String
Response example
Example import response
{
"status": "success"
}
The source specification gives no example value for this schema. The value above is an illustrative placeholder only.
Errors
The source specification does not define any error responses (4xx/5xx) for this endpoint — only the 200 success response is documented. Confirm actual error behavior with DQE engineering before publishing.
Test the API
Click the button below to test this endpoint live in your browser.