{"id":18484,"date":"2025-07-29T16:11:14","date_gmt":"2025-07-29T20:11:14","guid":{"rendered":"https:\/\/www.iri.com\/blog\/?p=18484"},"modified":"2025-09-03T17:02:08","modified_gmt":"2025-09-03T21:02:08","slug":"iri-darkshield-rest-api","status":"publish","type":"post","link":"https:\/\/www.iri.com\/blog\/data-protection\/iri-darkshield-rest-api\/","title":{"rendered":"IRI DarkShield REST API"},"content":{"rendered":"

Version 6 of the IRI DarkShield<\/strong><\/a> data masking tool now features a self-hosted (on-premise) REST API for PII (Personally Identifiable Information) data masking in structured, semi-structured, and unstructured data sources.\u00a0<\/span><\/p>\n

In previous articles, we have covered the related topics of DarkShield API <\/span>Text<\/span><\/a>, <\/span>Files<\/span><\/a>, <\/span>NoSql<\/span><\/a>, and <\/span>RDB<\/span><\/a> Remote Procedure Call (RPC) endpoints. In this article, we cover a single new endpoint that enables statelessness, providing easier integration with data masking and test data pipelines, as well as load balancing and other applications. <\/span><\/p>\n

The Previous DarkShield RPC APIs<\/b><\/h5>\n

If you review previous articles on the various DarkShield RPC APIs, you will find sections that describe the steps for creating a Search and Mask job. These steps had often required anywhere from 5-13 separate http(s) requests to DarkShield from the client to perform a single search and masking job.\u00a0<\/span><\/p>\n

As an RPC, each request to DarkShield provides individual pieces\/instructions that, when aggregated over multiple requests, provide the full context necessary for a Search and Mask Job. This form of client interaction with the API stands in contrast to the tenants of statelessness.<\/span><\/p>\n

Why Use a REST API?<\/b><\/h5>\n

With the format of an RPC API, there were some potential benefits in reusability and speed improvements in this method, thus DarkShield was initially built in this fashion. But as more use cases for DarkShield were presented to us by clients, we found the RPC format was no longer as beneficial. Furthermore, in certain scenarios, such as load balancing, which requires a stateless approach to communication, an RPC API was far more unwieldy.<\/span><\/p>\n

\"\"<\/p>\n

What is Stateless?<\/b><\/h5>\n

According to Lokesh Gupta, \u201cStatelessness means that every HTTP request happens in complete isolation. When the Client makes an HTTP request, it includes all information necessary for the server to fulfill the request\u201d. In the context of a DarkShield task, this means that the client sends all relevant information in a single http request to DarkShield to perform a single search\/mask job.\u00a0<\/span><\/p>\n

In this way, DarkShield can achieve statelessness to perform a Search and Mask on either files, relational databases, or NoSQL databases ,instead of previously requiring 5-13 separate HTTP\/s requests!<\/span><\/p>\n

\"\"<\/p>\n

REST vs. RPC tables courtesy of <\/span><\/i>https:\/\/patrickkarsh.medium.com\/<\/span><\/i><\/a><\/p>\n

How to Configure a Request to the DarkShield REST API<\/b><\/h5>\n

\"\"<\/p>\n

The REST endpoint is defined as <\/span>\u00a0%baseapiurl%<\/span>\/api\/darkshield\/all\/allContext.searchAndMask<\/span>.<\/span><\/p>\n

The contents of the context stored in your JSON file vary depending on whether you are searching and masking files or databases.<\/span><\/p>\n

\"\"<\/p>\n

Summary Pieces of DarkShield JSON Request Body<\/b><\/h5>\n