Registering or unregistering multiple entities

Using this API you can register or remove multiple DUNS numbers in/from the DnB monitoring registration using an export file.

Only entities with DUNS numbers will pass to processing.

Request

POST {DnBConnectorUri}/monitoring/batch

Table 1. Parameters
Parameter	Name	Required	Description
Headers	`Content-Type`	Yes	Must be `Content-Type: application/json`.
	`EnvironmentUrl`	Yes	Environment URL of the tenant. For example: https://dev.reltio.com
	`Authorization`	Yes	Reltio access token in the form `Bearer: <<token>>`, see Authentication API.
	`TenantId`	Yes	Tenant ID.
	`DnB-User`	Yes	DnB Direct+ multiprocess username.
	`DnB-Password`	Yes	DnB Direct+ multiprocess password.
	`DnB-Registration`	Yes	DnB registration identifier.
	`DnB-Registration-Op`	No	Registration operation. Value can be `add` or `remove`. Note: If the value is `add`, the system registers multiple entities. If the value is `remove`, the system unregisters multiple entities. The default value is `add`.
	`cronExpression`	No	DnB connector provides ability of scheduling batch jobs using standard cron expressions. Note: Expression is available in the UTC time zone. Please convert it to your local time before you start the job. Limits: You cannot create a schedule which runs batch jobs too often - configured in instance parameter `cron.job.min.interval` in seconds. You cannot schedule jobs per tenant as configured in the connector instance environment variable `cron.jobs.tenant.limit`.
Body		Yes	Defines the body of the JSON format that you use for creating batch jobs. A batch job contains two main tasks. These are as follows: Export task Put files task

Getting job status can be done using batch GET job requests.

Example:

POST http://localhost:8080/b2bIntegration/dnb/monitoring/batch

Request body

Different sample requests are given below.

If the export is initiated by the connectors


    {
    "exportTask": {
        "filter": "(startsWith(attributes.Name,'R')))"
    }
}

If you use additional parameters

{
  "exportTask": {
    "filter": "(startsWith(attributes.Name,'T')))",
    "distributed": true,
    "taskPartsCount": 300
  }
}

If you use a request body from a previous export

{
    "putFilesTask": {
        "exportTaskIds": ["41949723-470b-4d4d-9c9f-4fa35de0447d"],
        "processedEntities": 1000
    }
}

Response:

{
    "jobId": 5677455771697152,
    "success": "OK",
    "message": "Scheduled"
}

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2024 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms, Privacy Policy, and

Unify and manage your data

Registering or unregistering multiple entities

Footer