What's the credit rate for using Clay's HTTP API Enrichment?
What's the credit rate for using Clay's HTTP API Enrichment?
What's the credit rate for using Clay's HTTP API Enrichment?
Using HTTP API in Clay costs no credits. You can connect any external data sources through HTTP/API completely free of charge. This applies even when connecting to external tools that you already have subscriptions for.
Is that what you were looking for?
Yes, thank you!
Great! I'm here if you need any further assistance.
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Curious to know why this piece of my workflow shows 8 credits if the HTTP API isn't using credits?
While HTTP/API connections themselves are free, you may be seeing credit usage because of data enrichment actions in your workflow. Here's how it works: ** Any external data source connections via HTTP/API are completely free ** However, you will be charged credits for data enrichment actions like: • Finding contact information • Retrieving firmographic data • Other data enrichment tasks When using external APIs, there are two scenarios: 1. If you use your own API key, you pay through the external platform 2. If you use Clay's shared API key, you get charged in Clay credits The 8 credits you're seeing are likely from data enrichment actions in your workflow rather than the HTTP/API connection itself.
Is that what you were looking for?
All other enrichments in this table use API's from external platforms I am connected to
If you're seeing credit charges despite using your own API keys, there are a few things to check: 1. Verify that your API keys are properly connected in the workspace settings for all the external platforms you're using. 2. Confirm that all enrichment actions in your workflow are indeed using your connected API keys. While some enrichments might be using your external platform connections, others could be defaulting to Clay's shared API keys, which would incur credit charges. 3. Keep in mind that even with external API connections, if a provider charges for an API call, Clay will charge credits for that call. However, if the provider issues a refund due to invalid data, Clay will refund those credits back to you. To resolve this, double-check your workspace settings to ensure all integrations are using your own API keys rather than Clay's shared ones.
Was that helpful?
If you're using your own API key, you should not be charged any Clay credits. When using external APIs, there are two distinct scenarios: 1. Using your own API key: You pay directly through the external platform with no Clay credits charged 2. Using Clay's shared API key: You get charged in Clay credits Since you're seeing credit charges despite using your own API key, you should double-check your workspace settings to verify that the integration is properly configured to use your personal API key rather than Clay's shared key.
Source: FAQ | Clay.com
Is that what you were looking for?
I have tripple checked that all integrations are using my own API keys rather than Clay's shared ones.