API Terms of Service

PropContact is not a consumer reporting agency and the data is notFCRA-compliant. You may not use the data, in whole or in part, as a “consumer report” or for any purpose regulated by the Fair Credit Reporting Act (FCRA) - including decisions about credit, insurance, employment, or tenant screening.

You agree not to:

• Use the data for any FCRA-regulated decision (see §1).
• Contact individuals in violation of the TCPA, the federal or state Do-Not-Call registries, CAN-SPAM, or any wireless-consent or telemarketing law. You are solely responsible for your outreach and for scrubbing against DNC.
• Resell, sublicense, redistribute, or publicly post the raw data, or build a competing data product from it, except for the narrowly defined embedded/end-customer use expressly authorized in a signed Enterprise Order Form. No Enterprise Order Form permits public posting, unrestricted further resale, dataset reconstruction, or a competing data product unless it says so expressly.
• Exceed rate limits, share or expose API keys, circumvent metering, deduplication, or credit accounting, or attempt to extract the dataset in bulk.
• Use the data to harass, dox, stalk, discriminate against, or otherwise harm any person, or in violation of CCPA/CPRA or other privacy laws (including honoring any consumer opt-out / deletion obligations that apply to you).

Keep your keys secret; you are responsible for all activity under your keys. Test keys (pc_test_) return sandbox data and never spend credits. Live keys (pc_live_) bill real credits. Revoke a key any time from your dashboard; we may revoke keys for suspected abuse, non-payment, or security reasons.

• Search, preview, property-detail, and dropdown calls are free but rate-limited. Building a list spends one credit per eligible record, settled when the build completes; reading the results costs nothing extra.
• Credits are governed by our general Terms and Refund Policy. A call that can't be covered by your balance returns HTTP 402.
• Per-key rate limits and per-build caps protect service stability; we may adjust them to prevent abuse. Higher limits are available by agreement.

Address enrichment may place a maximum hold when a batch is accepted and settle a lower amount after processing. Unless an Enterprise Order Form says otherwise, invalid, not-found, ambiguous, and matched-with-no-requested-usable-contact rows are not base-billable. Optional email, line-status, reassigned-number, DNC, or other provider checks may use separately disclosed units. An API response or source signal is not proof of consent or legal permission to contact a person.

The data is provided “as is” from public records and licensed third-party sources. We do not warrant its accuracy, completeness, or fitness for a particular purpose. You are responsible for verifying data before relying on it.

A “verified” source match does not mean a phone is currently connected; a CLEC classification does not prove a mobile line; an email verification does not guarantee inbox placement; and a missing or unknown DNC, reassigned-number, or litigator signal does not mean the number is clear. Match, provider, and freshness fields must be interpreted according to the applicable API documentation.

If you use the PropContact Actor on Apify, these API Terms apply in addition to Apify's own Store and platform terms. The same prohibited-use rules in §2 apply to data obtained through Apify.

We may suspend or terminate API access for breach of these terms, suspected abuse, non-payment, or legal/security reasons. You will indemnify PropContact for claims arising from your use of the data or API, including your outreach and FCRA/TCPA/privacy compliance. To the maximum extent permitted by law, our aggregate liability is limited as set out in our general Terms of Service, and we are not liable for indirect or consequential damages.

We may update these API Terms; when the version changes you will be asked to re-accept before creating new keys. Questions? Email support@propcontact.net.