Client configurations
Your Emporix tenant name.
Note: The tenant should always be written in lowercase.
OK
Your Emporix tenant name.
Note: The tenant should always be written in lowercase.
Desired client's unique identifier.
OK
Configuration key.
Configuration value. It can be any valid JSON object.
Configuration version.
Describes purpose of the configuration.
Flag indicating whether the configuration should be encrypted. It works only if value field is of string type.
falseFlag indicating whether the configuration should be restricted. When configuration is rectricted then it cannot be deleted. When this property is set to true then it cannot be unset.
falseFlag indicating whether the configuration should be readOnly. When configuration is readOnly then it cannot be updated.
falseURL of Json Schema for validation purpose. When configuration is created this value can be provided and then each update operation will be validated against this schema. This property cannot be updated so once set it cannot be unset. The Json Schema should contain one root property named value in order to work correctly. An example of a valid schema: { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "required": ["value"], "properties": { "value": { "type": "boolean" } } }
The client configuration unique identifier.
The client to which the configuration applies.
OK
Your Emporix tenant name.
Note: The tenant should always be written in lowercase.
Desired client's unique identifier.
Configuration key.
Configuration value. It can be any valid JSON object.
Configuration version.
Describes purpose of the configuration.
Flag indicating whether the configuration should be encrypted. It works only if value field is of string type.
falseFlag indicating whether the configuration should be restricted. When configuration is rectricted then it cannot be deleted. When this property is set to true then it cannot be unset.
falseFlag indicating whether the configuration should be readOnly. When configuration is readOnly then it cannot be updated.
falseURL of Json Schema for validation purpose. When configuration is created this value can be provided and then each update operation will be validated against this schema. This property cannot be updated so once set it cannot be unset. The Json Schema should contain one root property named value in order to work correctly. An example of a valid schema: { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "required": ["value"], "properties": { "value": { "type": "boolean" } } }
The client configuration unique identifier.
The client to which the configuration applies.
Created
Bad Request
Conflict
Your Emporix tenant name.
Note: The tenant should always be written in lowercase.
Desired client's unique identifier.
Desired configuration key.
OK
Configuration key.
Configuration value. It can be any valid JSON object.
Configuration version.
Describes purpose of the configuration.
Flag indicating whether the configuration should be encrypted. It works only if value field is of string type.
falseFlag indicating whether the configuration should be restricted. When configuration is rectricted then it cannot be deleted. When this property is set to true then it cannot be unset.
falseFlag indicating whether the configuration should be readOnly. When configuration is readOnly then it cannot be updated.
falseURL of Json Schema for validation purpose. When configuration is created this value can be provided and then each update operation will be validated against this schema. This property cannot be updated so once set it cannot be unset. The Json Schema should contain one root property named value in order to work correctly. An example of a valid schema: { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "required": ["value"], "properties": { "value": { "type": "boolean" } } }
The client configuration unique identifier.
The client to which the configuration applies.
Your Emporix tenant name.
Note: The tenant should always be written in lowercase.
Desired client's unique identifier.
Desired configuration key.
Configuration key.
Configuration value. It can be any valid JSON object.
Configuration version.
Describes purpose of the configuration.
Flag indicating whether the configuration should be encrypted. It works only if value field is of string type.
falseFlag indicating whether the configuration should be restricted. When configuration is rectricted then it cannot be deleted. When this property is set to true then it cannot be unset.
falseFlag indicating whether the configuration should be readOnly. When configuration is readOnly then it cannot be updated.
falseURL of Json Schema for validation purpose. When configuration is created this value can be provided and then each update operation will be validated against this schema. This property cannot be updated so once set it cannot be unset. The Json Schema should contain one root property named value in order to work correctly. An example of a valid schema: { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "required": ["value"], "properties": { "value": { "type": "boolean" } } }
The client configuration unique identifier.
The client to which the configuration applies.
OK
Configuration key.
Configuration value. It can be any valid JSON object.
Configuration version.
Describes purpose of the configuration.
Flag indicating whether the configuration should be encrypted. It works only if value field is of string type.
falseFlag indicating whether the configuration should be restricted. When configuration is rectricted then it cannot be deleted. When this property is set to true then it cannot be unset.
falseFlag indicating whether the configuration should be readOnly. When configuration is readOnly then it cannot be updated.
falseURL of Json Schema for validation purpose. When configuration is created this value can be provided and then each update operation will be validated against this schema. This property cannot be updated so once set it cannot be unset. The Json Schema should contain one root property named value in order to work correctly. An example of a valid schema: { "$schema": "http://json-schema.org/draft-07/schema#", "type": "object", "required": ["value"], "properties": { "value": { "type": "boolean" } } }
Bad Request
Conflict
Your Emporix tenant name.
Note: The tenant should always be written in lowercase.
Desired client's unique identifier.
Desired configuration key.
No Content
Bad Request
Not found
No content
Last updated
Was this helpful?

