Snitcher API
✓ Official Vendor SpecCRMContact Managementbearer23 EndpointsREST
For Agents
Programmatically get contacts for an organisation, reveal an email for an organisation contact. Covers 23 operations with bearer authentication.
Use for: I need to contacts for an organisation, I want to reveal an email for an organisation contact, Search for organisations using advanced filters, Find all organisations
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Discovering leads or discovering our API. This page is all you need to do both!. The API exposes 23 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Snitcher API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Snitcher 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%2Fsnitcher.com%2Fsnitcher" | 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%2Fsnitcher.com%2Fsnitcher" | 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 Snitcher API.
Get contacts for an organisation
Reveal an email for an organisation contact
List organisations using advanced filters
Add a tag to an organisation
Remove a tag from an organisation
Use Cases
Patterns agents use Snitcher API for, with concrete tasks.
★ CRM Operations
Use the Snitcher API to perform crm operations programmatically. The API provides 23 endpoints covering core functionality including get contacts for an organisation, reveal an email for an organisation contact, list organisations using advanced filters.
Call GET /v1/workspaces/{workspaceUuid}/contacts to get contacts for an organisation
Automated Workspaces Management
Automate workspaces operations by combining multiple Snitcher API endpoints. Agents can reveal an email for an organisation contact and then list organisations using advanced filters in a single workflow.
Call PUT /v1/workspaces/{workspaceUuid}/contacts/{contactUuid}/reveal-email to reveal an email for an organisation contact, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Snitcher 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 'get contacts for an organisation', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
23 endpoints — discovering leads or discovering our api.
METHOD
PATH
DESCRIPTION
GET
/v1/workspaces/{workspaceUuid}/contacts
Get contacts for an organisation
PUT
/v1/workspaces/{workspaceUuid}/contacts/{contactUuid}/reveal-email
Reveal an email for an organisation contact
POST
/v1/workspaces/{workspaceUuid}/organisations
List organisations using advanced filters
GET
/v1/workspaces/{workspaceUuid}/organisations
List organisations
GET
/v1/workspaces/{workspaceUuid}/organisations/{organisationUuid}
Get an organisation
POST
/v1/workspaces/{workspaceUuid}/organisations/{organisationUuid}/tags
Add a tag to an organisation
DELETE
/v1/workspaces/{workspaceUuid}/organisations/{organisationUuid}/tags
Remove a tag from an organisation
GET
/v1/workspaces/{workspaceUuid}/segments
List all segments in a workspace
GET
/v1/workspaces/{workspaceUuid}/contacts
Get contacts for an organisation
PUT
/v1/workspaces/{workspaceUuid}/contacts/{contactUuid}/reveal-email
Reveal an email for an organisation contact
POST
/v1/workspaces/{workspaceUuid}/organisations
List organisations using advanced filters
GET
/v1/workspaces/{workspaceUuid}/organisations
List organisations
GET
/v1/workspaces/{workspaceUuid}/organisations/{organisationUuid}
Get an organisation
POST
/v1/workspaces/{workspaceUuid}/organisations/{organisationUuid}/tags
Add a tag to an organisation
DELETE
/v1/workspaces/{workspaceUuid}/organisations/{organisationUuid}/tags
Remove a tag from an organisation
GET
/v1/workspaces/{workspaceUuid}/segments
List all segments in a workspace
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Snitcher API by hand means sending your bearer token on every request, pointing at the api.snitcher.com host, and threading the workspace id through each contacts and organisations call yourself. Through Jentic you install once, import the Snitcher API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Snitcher puts the workspace id in the URL path (/v1/workspaces/{workspaceUuid}/...), so a rule can pin your agent to one workspace: it can read contacts and organisations there and nothing else. You choose the operations it may call, so destructive ones like removing organisation tags are not included unless you add them.
Credential isolation
Your Snitcher API token 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 'get contacts for an organisation' or 'list segments', and Jentic returns the matching Snitcher 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 Snitcher API through Jentic.
What authentication does the Snitcher API use?
The Snitcher 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 get contacts for an organisation with the Snitcher API?
Yes. Use the GET /v1/workspaces/{workspaceUuid}/contacts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Snitcher 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 get contacts for an organisation through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get contacts for an organisation'. Jentic returns the matching Snitcher API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Snitcher API have?
The Snitcher API exposes 23 endpoints covering workspaces, organisations, contacts operations.
GET STARTED