Skip to main content

How Credits Work

BounceWatch uses a credit-based pricing system. Each API request consumes credits based on the data modules you request.
Base data is always included and costs 10 credits. Additional enrichment modules add to this base cost.

Credit Pricing

Maximum cost per request: 60 credits (Base + all enrichment modules)

Enrichment Modules

Base Data (10 credits)

Always included with every request.Data Points:
  • Company name and domain
  • Description and tagline
  • Founded year
  • Employee count
  • Headquarters location
  • Social media links (LinkedIn, Twitter, etc.)
  • Contact information
  • Legal entity details
Company’s business context and market positioning.Data Points:
  • Industry classification
  • Business model
  • Target market
  • Services offered
  • Value proposition
  • Market positioning
Complete technology stack analysis.Data Points:
  • 100+ technology categories
  • Programming languages
  • Frameworks and libraries
  • Cloud infrastructure
  • Analytics tools
  • Marketing tools
  • Security solutions
Investment history and financial data.Data Points:
  • Funding rounds (Seed, Series A, B, C, etc.)
  • Total funding amount
  • Latest valuation
  • Investors list
  • Investment dates
  • Lead investors
Team composition and hiring activity.Data Points:
  • Key team members
  • Leadership profiles
  • Employee growth trends
  • Hiring status
  • Open positions
  • Department breakdown
39 signal types across 8 categories.Some types are unconfirmed — rumours or inferences rather than announcements (fundraising_intent, acquisition_rumor, shutdown_risk, and others). They are flagged as such in the response; report them with that qualification.
Competitive landscape analysis.Data Points:
  • Similar companies
  • Direct competitors
  • Market alternatives
  • Competitive positioning

Use Case Combinations

26 credits
Perfect for:
  • Funding history analysis
  • Team composition review
  • Investment decision support

Checking Your Credits

Response
Credits do not roll over. Each billing period starts at your plan’s limit, whatever was left of the previous one. Plan for the allowance, not for a balance that accumulates.

Credit Best Practices

Request Only What You Need

Start with base data and add enrichments as needed. Don’t request all modules if you only need funding data.

Cache Responses

Company data doesn’t change frequently. Cache responses for 24 hours to save credits.

Monitor Usage

Poll GET /account/credits — it returns balance, used, limit, percentage_used and resets_at. Webhooks fire on enrichment events only; there is no credit-threshold event to subscribe to.

Batch Wisely

Group similar enrichment requests to optimize credit usage.

Insufficient Credits

If you don’t have enough credits for a request, you get 402 Payment Required:
Some responses also carry the older required_credits / available_credits / credits_needed aliases. New integrations should read credits_required and credits_available, which are present everywhere.

Need More Credits?

Upgrade your plan → the new allowance is added on top of what is left of the current one

View Complete Response Structure

See exactly what data each module returns →