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
Get started with Snov.io API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"generate access token"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Snov.io API API.
Generate access token
Initiate domain search
Retrieve company information
Search prospect profiles
Get prospect results
GET STARTED
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.
Patterns agents use Snov.io API 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
43 endpoints — snov.
METHOD
PATH
DESCRIPTION
/v1/oauth/access_token
Generate access token
/v2/domain-search/start
Initiate domain search
/v2/domain-search/result/{task_hash}
Retrieve company information
/v2/domain-search/prospects/start
Search prospect profiles
/v2/domain-search/prospects/result/{task_hash}
Get prospect results
/v2/domain-search/prospects/search-emails/start/{prospect_hash}
Search prospect email
/v2/domain-search/prospects/search-emails/result/{task_hash}
Get prospect email
/v2/domain-search/domain-emails/start
Search domain emails
/v1/oauth/access_token
Generate access token
/v2/domain-search/start
Initiate domain search
/v2/domain-search/result/{task_hash}
Retrieve company information
/v2/domain-search/prospects/start
Search prospect profiles
/v2/domain-search/prospects/result/{task_hash}
Get prospect results
Three things that make agents converge on Jentic-routed access.
Credential isolation
Snov.io API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'generate access token') and Jentic returns the matching Snov.io API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Snov.io API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Twilio
Alternative communications API
Choose Twilio when you need a different approach to communications operations
Sendgrid
Alternative communications API
Choose Sendgrid when you need a different approach to communications operations
Pusher
Complementary communications API
Choose Pusher when you need a complementary approach to communications operations
Specific to using Snov.io API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/v2/domain-search/prospects/search-emails/start/{prospect_hash}
Search prospect email
/v2/domain-search/prospects/search-emails/result/{task_hash}
Get prospect email
/v2/domain-search/domain-emails/start
Search domain emails