If you want to use LeadsFriday without manually submitting every request from the dashboard, the API gives you another way to connect. Your API key identifies your LeadsFriday account when your application sends a request. Once it’s set up, you can use supported API endpoints to build LeadsFriday into your own tools, internal systems, or automated data workflows.
What your API key does
Think of an API key as a credential your application uses when talking to LeadsFriday.
Instead of signing in through the website for every action, your application includes the API key with supported requests.
That lets LeadsFriday know which account is making the request and which account should be associated with the usage.
Your API activity uses the same LeadsFriday account and credit balance as your normal platform activity.
You don’t need a separate balance just because you’re using the API.
Create your API key
Sign in to LeadsFriday and open the API section of your account.
From there, create an API key and copy it somewhere secure.
Depending on how your account is configured, you may only be shown the complete key when it’s created.
If that’s the case, save it before leaving the page.
Once you have the key, you can use it with supported LeadsFriday API requests.
Keep your API key private
Treat your API key like a password.
Don’t put it into a public GitHub repository, share it in screenshots, paste it into public documentation, or include it directly in frontend code that anyone can inspect.
If you’re building an application, keep the key on the server side or in a secure environment variable.
Your customers or website visitors shouldn’t be able to see it.
If someone has your API key, they may be able to make requests associated with your account.
Use the key in your requests
Your API key needs to be included with your API requests using the authentication method shown in the LeadsFriday API documentation.
Once authenticated, your application can use the supported endpoints available to your account.
Before building a large automation, start with a small test.
Make one request, check the response, and confirm that everything behaves the way you expect.
Then scale the workflow.
Rotate or replace your API key
There are situations where you may want to replace an existing API key.
Maybe a developer who had access has left your team. Maybe the key was accidentally shared somewhere it shouldn’t have been. Or perhaps rotating credentials is simply part of your company’s security process.
Create or rotate the key from your LeadsFriday API settings where supported, then update the credential wherever your integration uses it.
Make sure the new key works before removing the old one when your setup allows for that transition.
What to do if your key is exposed
If you believe an API key has been exposed, don’t leave it active.
Revoke or rotate it as soon as possible and update your integration with the replacement.
If you notice API activity you don’t recognize, contact LeadsFriday support and include the relevant details.
Keep the key private, test your integration with a small request, and rotate the credential whenever there’s a reason to believe it may no longer be secure.