You should be able to pull down the full list of properties metadata using a get request to
{dev-env-url}/api/external/v1/settings/GetPropertySchemaDetailsRecords?format=camel



If you also pull the same list of properties from your new instance, you can programmatically compare them. Then one at a time, for the custom properties you want to add to the new box, make post requests to
{}/api/external/v1/settings/addOrUpdatePropertyScehmaRecords?format=camel
with the post request payload being the schema item copied from
GetPropertySchemaDetailsRecords
, but popping the following fields that I’ve seen cause siemplify to error:
id
,
creationTimeUnixTimeInMs
,
modificationTimeUnixTimeInMs
,
product
,
valueForImportanceLevel
,
importanceLevel
,
orderNum
,
forDBMigration
.

Hope this helps

Thanks! I will give it a try

On the other hand, I've found in the API documentation the endpoint
/api/external/v1/ontology/GetMappingRules
. It seems it can allow accessing mapping rules applicable to an alertIdentifier. I've tried using the
Alert_id
field fetched from the alert in Siemplify with no success. Has anybody used this particular endpoint?



The error delivered by the endpoint is the following:




{"ErrorCode":2000,"ErrorMessage":"Should be in the request Source\\\\Product\\\\EventName.","InnerException":null,"InnerExceptionType":null}



I've tried to use the format depicted by the message with no success.





Thanks for your help!

This comment was originally sent by Tom Fridman


Hi
@aarguelles



Unfortunately this is an outdated endpoint that is not used anymore in the system.


We recommend using an alternative endpoint - /api/external/v1/ontology/GetMappingRulesForSettings,


which requires the following syntax in the request:


{


"source": " ... ",


"product": " ... ",


"eventName": " ... "


}