How to load data from New York Times to Databricks Lakehouse
Learn how to use Airbyte to synchronize your New York Times data into Databricks Lakehouse within minutes.


Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
Building in-house pipelines
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
After Airbyte
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Streamline AI workflows with Airbyte: load unstructured data into vector stores like Pinecone, Weaviate, and Milvus. Supports RAG transformations with LangChain chunking and embeddings from OpenAI, Cohere, etc., all in one operation.
Move Large Volumes, Fast
Quickly get up and running with a 5-minute setup that enables both incremental and full refreshes for databases of any size, seamlessly scaling to handle large data volumes. Our optimized architecture overcomes performance bottlenecks, ensuring efficient data synchronization even as your datasets grow from gigabytes to petabytes.
An Extensible Open-Source Standard
More than 1,000 developers contribute to Airbyte’s connectors, different interfaces (UI, API, Terraform Provider, Python Library), and integrations with the rest of the stack. Airbyte’s AI Connector Builder lets you edit or add new connectors in minutes.
Full Control & Security
Airbyte secures your data with cloud-hosted, self-hosted or hybrid deployment options. Single Sign-On (SSO) and Role-Based Access Control (RBAC) ensure only authorized users have access with the right permissions. Airbyte acts as a HIPAA conduit and supports compliance with CCPA, GDPR, and SOC2.
Fully Featured & Integrated
Airbyte automates schema evolution for seamless data flow, and utilizes efficient Change Data Capture (CDC) for real-time updates. Select only the columns you need, and leverage our dbt integration for powerful data transformations.
Enterprise Support with SLAs
Airbyte Self-Managed Enterprise comes with dedicated support and guaranteed service level agreements (SLAs), ensuring that your data movement infrastructure remains reliable and performant, and expert assistance is available when needed.
What our users say

Raman Singh
Predictable, straightforward pricing model that simplified budgeting and significantly reduced overall spend

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
How to Sync to Manually
Step 1: Access New York Times Data
Begin by identifying the data you wish to move. The New York Times offers data via their public APIs, such as the Article Search API or the Most Popular API. Sign up for an API key on The New York Times Developer Network to access these APIs.
Step 2: Configure API Requests
Use a programming language like Python to make HTTP requests to the New York Times API. Utilize libraries such as `requests` to handle these requests. Construct the API endpoint URLs with appropriate parameters (e.g., date range, query terms) to retrieve the desired data.
Step 3: Extract Data from API
Execute the API requests and extract the data. Parse the JSON response using Python's `json` library to transform the API response into a manageable data structure, such as a list or dictionary. Ensure to handle pagination if the API returns large datasets in multiple pages.
Step 4: Normalize and Clean Data
Process the extracted data to ensure consistency and cleanliness. Normalize the data by selecting relevant fields, handling missing values, and correcting data types as needed. This step prepares the data for efficient storage and analysis in Databricks.
Step 5: Save Data Locally
Convert the cleaned data into a format suitable for transfer, such as CSV or Parquet. Use Python libraries like `pandas` to create DataFrames and then export these DataFrames to local storage on your machine. This intermediate step ensures data integrity before loading it into Databricks.
Step 6: Transfer Data to Databricks Lakehouse
Upload the data from your local machine to your Databricks Lakehouse. Utilize Databricks' web interface or Databricks CLI to move the files into your cloud storage (e.g., AWS S3, Azure Blob Storage) that is configured with your Databricks environment.
Step 7: Load Data into Databricks Lakehouse Tables
Once the data is in your cloud storage, use Databricks' capabilities to load it into Delta Lake tables. You can use Spark SQL within Databricks to create tables and insert data. For example, utilize the `CREATE TABLE` and `COPY INTO` commands to organize and store your data appropriately for future analysis.
By following these steps, you can efficiently move data from The New York Times to a Databricks Lakehouse without relying on third-party connectors or integrations.