Snov.io API
Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer43 EndpointsREST
For Agents
Programmatically generate access token, initiate domain search. Covers 43 operations with bearer authentication.
Use for: I need to generate access token, I want to initiate domain search, Search for company information, Find all prospect profiles
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Snov.io provides email finder, verification, and outreach automation APIs. The API exposes 43 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Snov.io API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Snov.io API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsnov.io%2Fsnov" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsnov.io%2Fsnov" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Snov.io API.
Generate access token
Initiate domain search
Retrieve company information
Search prospect profiles
Get prospect results
Use Cases
Patterns agents use Snov.io API for, with concrete tasks.
★ Communications Operations
Use the Snov.io API to perform communications operations programmatically. The API provides 43 endpoints covering core functionality including generate access token, initiate domain search, retrieve company information.
Call POST /v1/oauth/access_token to generate access token
Automated Add Prospect To List Management
Automate add prospect to list operations by combining multiple Snov.io API endpoints. Agents can initiate domain search and then retrieve company information in a single workflow.
Call POST /v2/domain-search/start to initiate domain search, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Snov.io API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
43 endpoints — snov.
METHOD
PATH
DESCRIPTION
POST
/v1/oauth/access_token
Generate access token
POST
/v2/domain-search/start
Initiate domain search
GET
/v2/domain-search/result/{task_hash}
Retrieve company information
POST
/v2/domain-search/prospects/start
Search prospect profiles
GET
/v2/domain-search/prospects/result/{task_hash}
Get prospect results
POST
/v2/domain-search/prospects/search-emails/start/{prospect_hash}
Search prospect email
GET
/v2/domain-search/prospects/search-emails/result/{task_hash}
Get prospect email
POST
/v2/domain-search/domain-emails/start
Search domain emails
POST
/v1/oauth/access_token
Generate access token
POST
/v2/domain-search/start
Initiate domain search
GET
/v2/domain-search/result/{task_hash}
Retrieve company information
POST
/v2/domain-search/prospects/start
Search prospect profiles
GET
/v2/domain-search/prospects/result/{task_hash}
Get prospect results
POST
/v2/domain-search/prospects/search-emails/start/{prospect_hash}
Search prospect email
GET
/v2/domain-search/prospects/search-emails/result/{task_hash}
Get prospect email
POST
/v2/domain-search/domain-emails/start
Search domain emails
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Snov.io API by hand means exchanging credentials at its OAuth access-token endpoint, sending the bearer token on every request, and polling the task hash for domain-search results yourself. Through Jentic you install once, import the Snov.io API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The Snov.io API identifies work by operation and a task hash rather than a durable resource id in the URL path, so limit the agent to the operations it needs, such as starting a domain search and reading its result. You choose that set, so prospect and email-search operations are only included if you add them.
Credential isolation
Your Snov.io API credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find emails for a domain' or 'get domain search results', and Jentic returns the matching Snov.io API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Snov.io API through Jentic.
What authentication does the Snov.io API use?
The Snov.io API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I generate access token with the Snov.io API?
Yes. Use the POST /v1/oauth/access_token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Snov.io API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I generate access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'generate access token'. Jentic returns the matching Snov.io API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Snov.io API have?
The Snov.io API exposes 43 endpoints covering add prospect to list, add to do not email list, campaigns operations.
Can I limit what my agent is allowed to do with the Snov.io API?
Yes. Because you run Jentic One yourself, your own rules decide which Snov.io API operations and credentials the agent may use. The Snov.io API identifies work by operation and task hash rather than a durable resource id in the URL, so you can restrict the agent to just the calls it needs, such as starting a domain search and reading its result. Prospect and email-search operations are only in scope if you choose to add them.
GET STARTED