Your progress is only saved in this browser. to protect it and pick up on any device.

Connect a Postman API key to check your work

You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.

0 of 3 steps0%

Before anything can be queried, the data has to live somewhere Postman can reach. This part builds a dedicated workspace and your first dataset from two very different files, a CSV and a JSON export.

1

Create Your Datasets Workspace

Everything in this module, the dataset, the collection and the mock, lives in one workspace so the pieces stay together and easy to find.

  1. Open the Postman desktop app. If you don't have it yet, download Postman and sign in. Datasets need a Solo, Team or Enterprise plan.

  2. Click Workspaces in the top navigation → Create.

  3. In Workspace name, enter [Your name] - Datasets (for example Alex - Datasets).

    text
    - Datasets
  4. For Who can access, choose Only you and invited people.

  5. Leave the template on Blank workspace, then click Create Workspace.

Your new workspace opens automatically with an empty sidebar.

Troubleshooting: If validation fails, check that the name ends with - Datasets (with the hyphen) and that you created the workspace yourself rather than joining someone else's.

2

Create Your First Dataset From a CSV

A dataset is a named container of data sources (where the data comes from) and views (SQL queries that decide what you see). You'll start with one source: the account list.

  1. Save this as accounts.csv on your computer. The header row names become your column names:

    accounts.csv5 rows · 4 columns
    Local file
    accountIdcompanyplanregion
    1Northstar LogisticsenterpriseEMEA
    2Bluepeak EnergybusinessAMER
    3Cobalt HealthenterpriseAPAC
    4Lumen RetailstarterAMER
    5Vertex LabsbusinessEMEA
  2. In your Datasets workspace, click + in the left sidebar and select Dataset.

  3. Name the dataset:

    text
    billing-data

    Add a short description if you like.

  4. Choose a source type: Local File keeps the file on your machine, while Postman Cloud Store uploads it to Postman. Pick either, then choose accounts.csv. You can also drag and drop it into the workbench.

  5. Preview the data and click Save.

Postman reads CSV, JSON and spreadsheet files (.xlsx, .xls and .ods), and there is no file size limit like the one data files have. Open the dataset and look at the views: Postman created one automatically that selects everything from your source.

Expected outcome: A billing-data dataset with one data source and one auto-generated view that returns all five accounts.

Tip: Rather than typing data, you can click Add with AI when adding a source. Describe the rows you want, such as "20 invoices with an amount and a status", confirm the proposed schema and Agent Mode generates the rows, shows a preview and saves them as a CSV.
3

Add the Invoices as a Second Source

Real data rarely lives in one place. A dataset can combine many sources, even of different types, and later you'll join them with one query.

  1. Save this as invoices.json. It's a JSON array with one object per invoice:

    invoices.json7 rows · 5 columns
    Local file
    invoiceIdaccountIdproductamountstatus
    INV-10011Platform Annual12000paid
    INV-10022API Gateway4800paid
    INV-10031Premium Support2500refunded
    INV-10043Platform Annual12000paid
    INV-10054Starter Plan600void
    INV-10063Analytics Add-on3000refunded
    INV-10075API Gateway4800paid
  2. If billing-data is still open in the active tab from Step 2, stay there. Otherwise open it from the sidebar. Then click Add source. Select the Local File source type again (or Postman Cloud Store, to match what you chose in Step 2), choose invoices.json, preview the data and click Save.

  3. Each source now has its own auto-generated view, such as source_accounts_default_view, listed under Datasets in the left sidebar. Postman names every source source_ plus the file name, so you now have source_accounts and source_invoices. These names are the tables you query with SQL in the next part.

Files aren't the only option. Here is everything a dataset can read from:

SourceWherePlan
CSV, JSON, spreadsheetLocal file or Postman Cloud StoreSolo, Team, Enterprise
MySQL, Postgres, SQL ServerLive database (optionally via an SSH tunnel)Team, Enterprise
Custom JDBC driverOracle, Snowflake, BigQuery, Redshift, DuckDB and moreEnterprise

Database credentials can be stored as vault secrets, with Link to vault secret on the connection fields, so they never sit in plain text.

Expected outcome: Your dataset has two sources and two auto-generated views.