Batch data versus API requests

Why use batch data uploads?

Our Batch API allows you to upload millions of records with a single upload. There are lots of  reasons you might want to use this instead of our standard API requests. The main function is pretty simple, if you don’t have the capability to provide events in real time, batch uploads might be a more effective solution for you.

 

Batch

API

Frequency

Usually once a day but can occur a few times a day.

Carried out in real time.

Volume

Allows millions of records to be imported with a single upload.

It varies, you can find more information about our rate limits here.

Data types

NDJSON

JSON

Implementation 

Lower effort required.

Higher capability required to provide event bundles in real time.

Feedback

Slower feedback loop. 

Much shorter feedback loop allowing identification of malformed data very quickly.

NDJSON formatting 

The preference for formatting is Newline delimited JSON (NDJSON). We prefer this format for a few reasons. It helps with validation of your data, and allows for some amount of malformed data without completely rejecting the file. This provides a great redundancy. The specification for NDJSON formatting can be found on Github

For more information about the formatting requirements for your data, have a look at our Data section on Learn. The Data formatting and validation page would be a great place to start. 

File zipping and upload

Our file preference is a Gzipped NDJSON file. Gzip is a free compression software that has a great compression ratio, making your files smaller, and reducing the time to transfer your data. To learn more about Gzip and access the free software, check it out here. We will also accept regular NDJSON files if you’d prefer. 

Get your batch data uploaded into the Hub

Throughout the process you will need to work closely with the Lexer team in order to get everything uploaded and ready to go. 

The process you will need to follow:

  1. Create an .ndjson file that abides by the NDJSON formatting. Other formatting requirements for the file can be found in our Data section on Learn. 
  2. Ensure the file is Gzipped. 
  3. Once your file is Gzipped and ready to send to the team, follow either the SFTP, or AWS S3 process to upload your file. 
  4. Please make sure to let your Success Manager know you would like to batch upload as part of the onboarding process. 
  5. If this data transfer is part of a regular process, set up a schedule to transfer the deltas. This schedule should be outlined in your solution design.

Where to from here?

Batch data uploads could be the perfect solution to help you upload large volumes of data infrequently, but there might be an option that fits your business even better. Make sure you have a chat with your Success Manager so they can help you find the best solution. This helps you get the most out of your data as quickly as possible.

Updated:
October 14, 2022
Did this page help you?
Thank you! Your feedback has been received!
Oops! Something went wrong while submitting the form, for assistance please contact support@lexer.io
Welcome to Lexer!
Fundamentals
Getting started
Our glossary
Fundamentals
Getting started
Integrations
Fundamentals
Setup
My account
Fundamentals
Setup
Manage team
Fundamentals
Setup
Group permissions
Fundamentals
Setup
Classifications
Fundamentals
Setup
Out of the box segments
Fundamentals
Setup
Browser guide
Fundamentals
Security
Corporate networks
Fundamentals
Security
Emergency contact
Fundamentals
Security
Multi-factor authentication
Fundamentals
Security
Single sign-on
Fundamentals
Security
Trust and compliance
Fundamentals
Security
Lexer's Identity Resolution
Fundamentals
Identity Resolution
Troubleshooting tech issues
Fundamentals
Troubleshooting
Error code: 503 Service Unavailable
Fundamentals
Troubleshooting
Error code: 401 Unauthorized
Fundamentals
Troubleshooting
Error code: 403 Forbidden
Fundamentals
Troubleshooting
Troubleshooting Activate
Fundamentals
Troubleshooting
Troubleshooting Respond
Fundamentals
Troubleshooting
Help! My data is missing from the Hub
Fundamentals
Troubleshooting
Understanding APIs at Lexer
Data
Data Onboarding
Providing JSON data to Lexer
Data
Data Onboarding
Providing CSV data to Lexer
Data
Data Onboarding
Upload using SFTP
Data
Data Onboarding
Upload using S3
Data
Data Onboarding
Lexer data specification
Data
Lexer Data Specification
Customer data specification
Data
Lexer Data Specification
Commerce data specification
Data
Lexer Data Specification
Marketing data specification
Data
Lexer Data Specification
Compliance data specification
Data
Lexer Data Specification
Data Formatting and Validation
Data
Getting Started with APIs
Authentication and API token creation
Data
Getting Started with APIs
Rate Limits
Data
Getting Started with APIs
Response codes and common errors
Data
Getting Started with APIs
Product imagery
Data
Getting Started with APIs
Currency conversion
Data
Getting Started with APIs
Lexer’s APIs overview
Data
Lexer’s APIs
Dataset management in the Hub
Data
Dataset management
Chatbox user API
Data
Lexer’s APIs
Activity API
Data
Lexer’s APIs
Visualize API
Hidden from nav
Profile Read API
Data
Lexer’s APIs
Lexer Javascript Tag basics
Data
Lexer Javascript Tag
Lexer Javascript Tag technical guide
Data
Lexer Javascript Tag
Lexer Javascript Tag use cases
Data
Lexer Javascript Tag
dataLayer configuration: Shopify
Data
Lexer Javascript Tag
Customer segment CSV export
Data
Data off-boarding
Export to CSV
Data
Data off-boarding
Data in Lexer's CDXP
Understand
Customer Data
Lexer's attributes
Understand
Customer Data
Attribute value types
Understand
Customer Data
Data source - CRM
Understand
Customer Data
Data source - Transactions
Understand
Customer Data
Data source - Email
Understand
Customer Data
Partner data - Experian
Understand
Customer Data
Partner data - Mastercard
Understand
Customer Data
Partner data - Roy Morgan
Understand
Customer Data
GDPR and CCPA requests
Understand
Customer Data
Upload data files
Understand
Customer Data
File upload API
Understand
Customer Data
Data provision and schemas
Understand
Customer Data
Segment overview
Understand
Segment
Creating segments
Understand
Segment
Smart Search
Understand
Segment
Export attribute results
Understand
Segment
Contact a customer
Understand
Segment
Fixing a disabled segment
Understand
Segment
Profile tab
Understand
Segment
Compare segments
Understand
Compare
Compare attributes
Understand
Compare
Activate overview
Engage
Activate
Ongoing activations
Engage
Activate
Audience splits
Engage
Activate
A/B splits
Engage
Activate
Control group splits
Engage
Activate
Inbox filtering
Engage
Respond
Ignored Senders
Engage
Respond
Forms for service
Engage
Respond
Workflow states
Engage
Respond
Bulk changes
Engage
Respond
Scheduled replies
Engage
Respond
Message templates
Engage
Respond
Customer profiles
Engage
Respond
Grouped messages
Engage
Respond
Automation rules
Engage
Respond
Redact messages
Engage
Respond
Track overview
Measure
Track
Activity overview
Measure
Activity
Team report
Measure
Activity
Cases report
Measure
Activity
Listen overview
Measure
Listen
Searching in Listen
Measure
Listen
Tier filters
Measure
Listen
Boolean search
Measure
Listen
Saved dives
Measure
Listen
Email notifications
Measure
Listen
Twitter data
Measure
Listen
Facebook data
Measure
Listen
Instagram data
Measure
Listen
Visualize overview
Measure
Visualize
Curate feed
Measure
Visualize
Report overview
Measure
Report