Skip to main content
To view SignalHire’s pricing plans, visit the pricing page.

Credit Usage by Endpoint

Person API — with contacts

Each successful person lookup consumes standard SignalHire credits. These are the same credits used across the SignalHire website, browser extension and api — the balance is shared between all three.

Person API — without contacts

Retrieving profiles without contact details requires a separate credit type, independent of the standard balance. To purchase without-contacts credits, contact support@signalhire.com.

Search API

Search requests are not billed per credit — instead, they count against a daily search quota. This quota is shared between the SignalHire website and the API, so searches made in either place consume from the same daily limit.
  • The quota covers both the number of search queries and the total number of profiles returned — both are tracked separately against daily limits
  • The quota resets daily
  • The quota varies by plan and is set individually — trial accounts have a significantly lower limit than paid accounts
  • When the daily quota is exhausted, the API returns HTTP 402

Summary

Tracking Usage

To check remaining credits at any time, use the Get Remaining Credits endpoint or check the X-Credits-Left header included in every API response.

Company API

The Company API uses one purchasable credit type, separate from Person API credits:
  • Company data credits — consumed by the /company/info endpoint. Each successful call consumes one credit. Contact support@signalhire.com to purchase.
/company/getProfiles does not consume a purchasable credit. Instead, each profile delivered counts against the same daily profile-view quota shared with the SignalHire website. The quota varies by plan, up to 2000 profiles/day. The /company/findById and /company/getCount endpoints do not consume any credits or quota. The Company API is available on request — contact support@signalhire.com to enable access.