Applications detection rules API - POST a rule

Creates a new application detection rule.

The request consumes and produces an application/json payload.

POST	Managed https://{your-domain}/e/{your-environment-id}/api/config/v1/applicationDetectionRules SaaS https://{your-environment-id}.live.dexp.ae/api/config/v1/applicationDetectionRules

Authentication

To execute this request, you need the Write configuration permission assigned to your API token. See the Authentication page to learn how to obtain and use it.

Parameters

Parameter Type Description In Required

body

Parameter	Type	Description	In	Required
body	ApplicationDetectionRuleConfig	JSON body of the request containing definition of the new application detection rule. You must neither specify ID nor order of the rule.	body	optional
position	string	By default, the new rule will be inserted in an appropriate spot. To customize the ordering of the new rule, set to `PREPEND` to prepend it to the list, `APPEND` to append it. The position element can hold these values.	query	optional

ApplicationDetectionRuleConfig

JSON body of the request containing definition of the new application detection rule.

You must neither specify ID nor order of the rule.

body

optional

position

string

By default, the new rule will be inserted in an appropriate spot. To customize the ordering of the new rule, set to PREPEND to prepend it to the list, APPEND to append it.

The position element can hold these values.

query

optional

Request parameters JSON model

The ApplicationDetectionRuleConfig object

Element	Type	Description	Required
metadata	ConfigurationMetadata	Metadata useful for debugging.	optional
id	string	The unique ID of the rule. When adding a new rule, you can either specify your own ID, or don't specify anything, in that case the ID will be generated automatically.	optional
order	string	The order string. Sorting application detection rules alphabetically by their order string determines their relative ordering. Typically this is managed by DESK internally and will not be present in GET responses.	optional
applicationIdentifier	string	The identifier of the application, for example `APPLICATION-4A3B43`. You must use an existing ID.	required
filterConfig	ApplicationFilter	Defines how to identify an application.	required

The ApplicationFilter object

Defines how to identify an application.

Element	Type	Description	Required
pattern	string	The string to look for.	required
applicationMatchType	string	Defines the matching rule. The applicationMatchType element can hold these values.	required
applicationMatchTarget	string	Defines where to look for the string. The applicationMatchTarget element can hold these values.	required

The ConfigurationMetadata object

Metadata useful for debugging

Element	Type	Description	Required
configurationVersions	integer[]	A Sorted list of the version numbers of the configuration.	optional
clusterVersion	string	DESK server version.	optional

This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request. See the Example expandable section for working sample request.

      
  {
  "metadata": {
    "configurationVersions": [
      4,
      2
    ],
    "clusterVersion": {
      "major": 0,
      "minor": 0,
      "revision": 0,
      "sourceRevision": "",
      "timestamp": ""
    }
  },
  "id": "12345678-abcd-1234-abcd-1234567890ab",
  "applicationIdentifier": "APPLICATION-123456",
  "filterConfig": {
    "pattern": "myapp.example.com",
    "applicationMatchType": "EQUALS",
    "applicationMatchTarget": "DOMAIN"
  }
}

Possible values

Possible values for the position element:

APPEND
PREPEND

Possible values for the applicationMatchTarget element in the ApplicationFilter object:

DOMAIN
URL

Possible values for the applicationMatchType element in the ApplicationFilter object:

BEGINS_WITH
CONTAINS
ENDS_WITH
EQUALS
MATCHES

Response format

Response parameters JSON model

The EntityShortRepresentation object

The short representation of a DESK entity.

Element	Type	Description
id	string	The ID of the DESK entity.
name	string	The name of the DESK entity.
description	string	A short description of the DESK entity.

{}

Validate payload

We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.

The request consumes an application/json payload.

POST	Managed https://{your-domain}/e/{your-environment-id}/api/config/v1/applicationDetectionRules/validator SaaS https://{your-environment-id}.live.dexp.ae/api/config/v1/applicationDetectionRules/validator

Authentication

To execute this request, you need the Write configuration permission assigned to your API token. See the Authentication page to learn how to obtain and use it.

Response codes

Code	Description
204	Validated. The submitted configuration is valid. Response does not have a body.
400	Failed. The input is invalid.