Bulk Create Customizations
POSTOverview
Section titled “Overview”Create multiple customizations in one API call. This endpoint accepts NDJSON, where each line is one customization object.
Each line in the request body must be a valid JSON object. Up to 5000 pin scopes can be sent in a single request.
Request parameters
Section titled “Request parameters”Path parameters
Section titled “Path parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
TRACKER_ID | string | ✓ | Your unique tracker identifier. |
Query parameters
Section titled “Query parameters”| Parameter | Type | Default | Description |
|---|---|---|---|
conflict_strategy | string | raise | Conflict handling mode: raise, ignore, or override. |
Request headers
Section titled “Request headers”| Header | Value | Description |
|---|---|---|
Content-Type | application/x-ndjson | Required. |
Date | HTTP date | Required for HMAC. |
Authorization | ApiAuth {TRACKER_ID}:{SIGNATURE} | Required for HMAC. |
Request body format
Section titled “Request body format”The request body uses NDJSON. Each line must be a valid customization object.
How to Make a Request
Section titled “How to Make a Request”- Build the HMAC string from the method, content type, date, and base resource path.
- Exclude query parameters from the signed path.
- Send the NDJSON body together with
Date,Content-Type, andAuthorization.
Response structure
Section titled “Response structure”Returns 200 OK on success with an empty JSON object.
Error handling
Section titled “Error handling”| HTTP Status | Description |
|---|---|
200 OK | Success. |
401 Unauthorized | Missing or invalid authentication. |
404 Not Found | Tracker not found. |
409 Conflict | Conflict detected when conflict_strategy=raise. |
413 Content Too Large | Too many customizations in one request. |
422 Unprocessable Entity | Invalid pin definition provided. |
Was this page helpful?
Thanks.