# Start DNB Lookup Job Initialisation of a DNB lookup job. The job will be executed asynchronously. The response contains the job ID which can be used to poll for the status of the job. Endpoint: POST /dnb/lookupjobs Version: 3 Security: apiKey ## Request fields (application/json): - `storageId` (string) Unique identifier of the Storage. Example: "72d6900fce6b326088f5d9d91049e3e6" - `dnbUser` (string) Optional if credentials are available in user or organization settings. Example: "myDnbUser" - `dnbPassword` (string) Optional if credentials are available in user or organization settings. Example: "myDnbPassword" - `mode` (string) MATCH contains just the match results while EXTENDED_MATCH also includes D&B products (attention increased costs) Enum: "EXTENDED_MATCH", "MATCH" - `featuresOn` (array) List of features to be activated in the lookup. Enum: "INCREMENT", "ENABLE_PARTIAL_QUOTA_CONSUMPTION", "ACTIVATE_MASTER_DATA_EXTENDED", "SKIP_DNB_IMPORT", "ENRICH_COMMERCIAL_ULTIMATE" - `featuresOff` (array) List of features to be deactivated in the lookup. Enum: "INCREMENT", "ENABLE_PARTIAL_QUOTA_CONSUMPTION", "ACTIVATE_MASTER_DATA_EXTENDED", "SKIP_DNB_IMPORT", "ENRICH_COMMERCIAL_ULTIMATE" - `dnbDataSource` (string) D&B name of the product to be used in the job. Enum: "DNB", "DNB_MASTER_DATA_BASIC", "DNB_MASTER_DATA_MGMT", "DNB_MASTER_DATA_LINKAGE", "DNB_MASTER_DATA_EXTENDED", "DNB_LINKAGE_LNKELI" - `dataSources` (array) IDs of Data Sources in specified Data Mirror to be included during lookup. Leave empty to include all Data Dources. Example: ["648824a691d8d2503d65103e"] ## Response 200 fields (application/json): - `id` (string) Unique identifier of a job. Example: "35f23c03-1c22-45fe-9484-3ffe769325de" - `storageId` (string) Unique identifier of the Storage. Example: "72d6900fce6b326088f5d9d91049e3e6" - `status` (string) Job execution status. Enum: "UNKNOWN", "CANCELED", "CREATED", "PERSISTED", "SCHEDULED", "WAITING", "COULDNT_START", "RUNNING", "FINISHED", "DIED", "FAILED" - `createdAt` (string) Date of creation (ISO 8601-compliant). Example: "2025-09-12T14:57:59Z" - `createdBy` (string) Creator of a resource. Example: "76248934691294444" - `progress` (integer) Progress (%) of the job. Example: "77" - `result` (object) Lookup Job result for D&B data. - `result.statistics` (object) Contains statistics about a DNB lookup job like number of records, number of failed records, etc. - `result.statistics.numberOfRecords` (integer) Number of records in the input storage. Example: "10" - `result.statistics.numberOfFailed` (integer) Number of records updates / retrieves fails. Example: "0" - `result.statistics.numberOfInserts` (integer) Number of successfully retrieved data. Example: "10" - `result.statistics.numberOfQuotaExceeded` (integer) Number of not processed records which exceeded defined quota limit. Example: "10" - `result.statistics.numberOfUnknown` (integer) Number of non-retrieved records from DNB service. Example: "0" - `modifiedAt` (string) Date of modification (ISO 8601-compliant). Example: "2025-09-12T14:57:59Z" - `statusMessage` (string) Additional information to explain the status. Example: "The job failed because storage is empty." ## Response 400 fields (application/json): - `path` (string) Requested path which caused this error. Example: "/v2/businesspartners/lookup" - `id` (string) Unique identifier of an error, usually in a format of . Example: "REF_VIES_SERVICE_UNAVAILABLE_300" - `timestamp` (string) ISO 8601 representation of the timestamp. Example: "2025-09-12T14:57:59Z" - `message` (string) Details about the error. Example: "This user is not allowed to access this service." - `error` (string) RFC 7231 error which belongs to the status code. Example: "BAD_REQUEST" - `status` (integer) RFC 7231 status code for this error. Example: "400"