Glossary · Data and enrichment

What is data as a service (DaaS)?

The short answer

Data as a service (DaaS) is a way of delivering data in which the provider hosts it, keeps it current and serves it on request, through an API or a cloud connector, on a subscription or usage plan. The customer asks for the records it needs when it needs them, instead of buying a file once and storing it.

Updated
Read
4 min
Written by
Antoine Blitz
On this page7 sections
  1. Real data
  2. How does data as a service work?
  3. Data file, data as a service and SaaS: what is the difference?
  4. Why do B2B teams use data as a service?
  5. How do you get B2B data as a service?
  6. Related terms
  7. Questions people ask

Real data

What data on demand returns on the day of the call

Two things a file exported last month cannot hold: the job postings published since, and a company's figures as of today. US job postings by publication window, then Datadog, starting from its domain datadoghq.com, all on October 28, 2026.

Returned by the BlitzAPI API on

POST/v2/jobs/search

US job postings, by how recently they were published

Last day
115,350
Last 7 days
778,948
Last 30 days
3,796,897

One request per window (date_posted.last_days set to 1, 7 and 30), read from total_results; the windows overlap. These are postings, not companies. The newest one in the response was dated 16:58 UTC that day, about three hours before the call.

POST/v2/enrichment/company

Datadog, as the company record returned it

Company
Datadog
Domain
datadoghq.com
Industry
Software Development
Headquarters
New York, New York, United States
Employees on LinkedIn
10,333

The domain was first resolved to the company page with Domain to LinkedIn URL. The employee count is the approximate number of employees on LinkedIn, as BlitzAPI held it on the day of the call.

POST/v2/jobs/company

Datadog job postings, by publication window

Last 7 days
43
Last 30 days
290

Read from total_results: the postings Datadog published in the 7 and the 30 days through October 28, 2026.

How does data as a service work?

In data as a service, the provider does the heavy work once, for every customer: it gathers the data from its sources, cleans and matches it, stores it and keeps it current. Customers never hold a copy of the whole dataset. They ask for what they need, when they need it:

  • Through an API. A request names a company, a person or a set of filters, and the response returns structured records, usually as JSON. A B2B data API works this way.
  • Through a cloud connector. The provider shares tables directly into the customer’s data warehouse and refreshes them on its side.
  • Through scheduled feeds. Files delivered every day or every week, halfway between a purchase and a service.

Billing follows the same logic: per call, per record, per row delivered, or a subscription with a monthly volume.

The proof above shows the point of it. On October 28, 2026, one request counted 115,350 US job postings published in the last day, and another counted 3,796,897 in the last 30 days. A file exported a month earlier cannot list any of them.

Data file, data as a service and SaaS: what is the difference?

A data file, data as a service and SaaS differ in what you receive and in who keeps the data current:

Data file Data as a service Software as a service (SaaS)
What you get A copy of a dataset, once Answers to requests, as often as you ask An application to use
Freshness Frozen on the export date As of the provider’s latest update, read at each request Depends on the data you put in
Where the data lives In your CRM or warehouse On the provider’s servers In the vendor’s app, but it is your data
Who keeps it current You The provider You
Typical pricing One-time purchase or license Usage or subscription Per seat or subscription
Example A contact list bought for a campaign A company record fetched when a lead signs up A CRM or an email platform

The lines blur in practice: plenty of SaaS products embed a data service, and data services often come with an app. One question sorts them out. When a fact changes in the world, who updates your copy?

Why do B2B teams use data as a service?

B2B teams use data as a service because the facts they sell on keep moving. People change jobs and titles; companies hire, move and rebrand; a work address stops working when its owner leaves (data decay). A list bought in January describes January.

Three uses follow from that:

  1. Enrichment at the moment of need. A new lead or account gets its company and contact details when it enters the CRM, as they stand that day (data enrichment).
  2. Signals. Job postings, headcounts and the tools named in postings are worth reading while they are recent (technographic data).
  3. Agents and automations. A workflow tool or an AI agent does not open last quarter’s spreadsheet: it calls an endpoint, reads the JSON and acts on it (AI agents guide).
Check yourselfWhich of these is data as a service?
Show the answer key
  1. A spreadsheet of contacts bought once and imported into the CRMThat is a data purchase: the copy is yours, and nothing updates it after the import.
  2. An API your CRM calls for the current company record when a new lead signs upThe provider hosts and refreshes the data, and your system asks for one record at the moment it needs it.
  3. A dashboard your team builds on its own CRM dataThat is analytics on data you already own; no provider serves anything.
  4. An email platform your team subscribes toThat is software as a service: the vendor provides the application, and the contacts in it are yours.

How do you get B2B data as a service?

You get B2B data as a service by calling an API from wherever the work happens: a CRM, a spreadsheet, a workflow tool such as Clay, n8n, Make or Zapier, or an AI agent through an MCP server.

Company Enrichment returns a company’s record from its company page, once Domain to LinkedIn URL has resolved a bare domain, as in the Datadog example above. Jobs Search returns job postings filtered by title, location and date, with a total count. Each call returns the values the provider holds at the time of the request, so the same question asked next month gets next month’s values.

Sources and method

Written by
Antoine Blitz, Founder, BlitzAPI
Published
API calls run on

The calls ran on October 28, 2026 through the BlitzAPI MCP server, which calls the same endpoints; they are shown here as the equivalent REST requests.

Job counts are postings, not companies: one company can publish many roles. Industry is the label the company publishes on its own page, shown as returned.

Employee counts and job postings change every day; the values are those of October 28, 2026.

Questions people ask

What is an example of data as a service?

A weather API that a delivery app calls before planning its routes; a market data feed inside a trading tool; a B2B data API that a CRM calls to fill in a company's industry and size when a lead signs up. In each case the provider keeps the data current on its own servers, and the customer pays to ask it questions.

How is data as a service priced?

In one of four ways, sometimes combined: per call, per record returned, by subscription with a monthly volume, or with prepaid credits spent on each request. Usage pricing suits irregular needs, a subscription suits steady ones. Read what counts as usage: depending on the provider, a call that finds nothing may or may not cost anything.

What are the risks of data as a service?

Dependence, first: when the provider changes its terms, its prices or its data, your workflows feel it at once. Rate limits cap how fast you can ask. And the data still has to be right, since a service delivers whatever its sources hold: check how a provider sources and refreshes its data, and what it returns when it does not know.

With BlitzAPI

Put it to work

For builders

The calls behind the real data on this page, as REST requests. Send them with your API key, from any language or workflow tool.

From the domain to the company page

curl -X POST https://api.blitz-api.ai/v2/enrichment/domain-to-linkedin \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"datadoghq.com"}'

API reference

The company record

curl -X POST https://api.blitz-api.ai/v2/enrichment/company \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"company_linkedin_url":"https://www.linkedin.com/company/datadog"}'

API reference

Datadog postings from the last 30 days (the same request runs with 7)

curl -X POST https://api.blitz-api.ai/v2/jobs/company \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company_linkedin_url": "https://www.linkedin.com/company/datadog",
    "job": {"date_posted": {"last_days": 30}},
    "max_results": 1
  }'

API reference

US job postings from the last day (the same request runs with 7 and 30)

curl -X POST https://api.blitz-api.ai/v2/jobs/search \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 1}
    },
    "max_results": 1
  }'

API reference

Data shouldn't be
the problem

Grab. Connect. Build.