Skip to main content

Overview

The Bulk Retrieve API provides a way to retrieve multiple profiles using the Person Retrieve API in one request.
Bulk Person Retrieve API Summary.svg

Request Format

The endpoint for the Bulk Person Retrieve API is POST https://api.peopledatalabs.com/v5/person/retrieve/bulk. You must use POST requests. You can retrieve up to 100 persons in a single HTTP request. The request body must contain an array called requests with 1-100 individual request objects, each containing a valid PDL ID.
JSON

Response Format

The bulk response is a JSON Array of objects with the following fields: Note: Metadata is on a per-request basis and generally you should use it to connect requests to responses within an API call. See this section for more information. The order the objects appear in the response list is the same as the order of the IDs in the input requests array. Each response contains an individual status code that shows whether the retrieval for that particular request was successful (200) or not. See Errors for a detailed breakdown on all possible status codes.

Example

JSON

Tracking Responses

The API always return response objects in the same order as they were defined in the requests array. However, you can also add a metadata object to each request, containing any information specific to that request. If you define metadata in a request object, the API will return it unchanged in that request’s corresponding response object:
Expected Output:
JSON

Usage Notes

Any response object in a /v5/person/retrieve/bulk response will either have a status code of 200, 404 or 400. Any valid /v5/person/retrieve/bulk will return with a status code of 200. We will deduct the number of 200 responses to a bulk retrieve request from the number of remaining retrieve matches in your account as though each request was made individually.

Malformed, Unauthenticated or Throttled Requests

Any malformed, unauthenticated or throttled requests will return errors in the same format as documented in the Errors page.
JSON

Bulk Request Limitations

Currently, due to infrastructure constraints, there is a 1MB limit on API responses. Most bulk requests will not hit this limit. However, an 80-100 record bulk request that returns rich records may approach or go over this limitation. Here are some ways to ensure that you don’t run into this limitation:
  1. Add the Accept-Encoding: gzip header to your request headers. We will gzip-compress the responses, which will be around five times smaller.
  2. Retrieve less records per call. Enriching around 50 records instead of 100 should bypass this limitation.