The DataSift API is built for integrations, scripts and agentic tools that work with your own account's data. This page sets out what the Open API key may and may not be used for. It applies together with Rate limits and Bulk operations, and is part of the DataSift Terms & Conditions.
Every integration, script or agentic tool must authenticate with an Open API key from Settings → Integrations (see Authentication).
Do not build on a bearer token copied from a signed-in browser session (for example from the browser console). That path is being restricted, it is not supported for integrations, and its throughput will be significantly lower than an Open API key.
Use SiftMap to find properties, then use the DataSift API to work with records in your account:
- Search with SiftMap filters.
- Drill into property details for some of the results.
- Optionally fetch more data on those properties.
- Decide whether to add each property to your account.
Pulling large volumes of property details without adding the corresponding records to your account is scraping and is not allowed, even when every request stays within the rate limits.
Some endpoints exist for the DataSift app, for partner integrations, or for manual use only. Calling them from a customer integration, script or agentic tool is a breach of the Terms & Conditions.
These namespaces serve specific partner integrations and the DataSift app. They are not a general-purpose API, even where an Open API key can reach them:
calltools, launch-control, reirail, smarter-contact, smrtphone, smrtdialer, xencall, kixie, aircall, twilio, plivo, dataflik
Use the /api/internal/ endpoints instead.
GET /properties/images/?address=... (the nationwide image lookup) is reserved for the DataSift app. Any programmatic use with an Open API key is prohibited.
Don't drive volume through the SiftMap autocomplete (type-ahead) endpoints. If you already know the counties, ZIP codes or other areas you want, call the search endpoint directly:
POST /properties/search/The following are manual only. Do them in the app, or ask DataSift support:
- Signup and account information changes (creating accounts or trials, changing account details)
- Billing, plan changes, and freezing or deleting an account
- Credits, invoices and payments (credit balance changes, invoices, payment methods)
- Affiliate rewards (referral tracking, payouts, affiliate accounts)
- Creating, changing or deactivating users. Reading user information through the API is allowed.
Some operations change billing, delete data other records depend on, or can't be undone. In the app they show the amount or ask you to type a confirmation first. They aren't part of the Open API, so they can't run without that confirmation:
- Integration and webhook setup: connecting email and calendar accounts, DataFlik, and creating or changing webhooks.
- Addon settings: changes that can turn on automatic, billable actions (for example automatic skip tracing).
- Owner merge and swap: combining or reassigning owner records can't be reversed.
- Deleting SiftLine boards: removes the board with all its columns and cards.
- Deleting custom fields and field groups: removes the field's value from every record.
Do these in the DataSift app. Endpoints that serve only the app's screens (table views, record navigation, column settings) aren't part of the Open API either.
Rate limits are enforced automatically (see Rate limits). DataSift also reviews API usage regularly and may restrict keys whose usage doesn't match this page. These rules may be updated as usage patterns evolve; changes are announced in the changelog.
If your use case doesn't fit these rules, contact DataSift support before you build it. We'd rather adjust a limit than have your integration blocked.