canonical: https://jentic.com/apis/snitcher.com/snitcher

# Snitcher API

Discovering leads or discovering our API. This page is all you need to do both!. The API exposes 23 endpoints secured with bearer authentication.

## For AI agents

Programmatically get contacts for an organisation, reveal an email for an organisation contact. Covers 23 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get contacts for an organisation', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Workspaces** — Endpoints for managing workspaces, users and tags available in the workspace
- **Organisations** — Endpoints for organisations
- **Contacts** — Endpoints for organisation contacts
- **Sessions** — Endpoints for sessions
- **Segments** — Endpoints for segments

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 68 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/snitcher.com/snitcher/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Snitcher API?

Yes. Because you self-host Jentic One, your own rules decide which Snitcher operations and credentials the agent may use. Since Snitcher carries the workspace id in the URL path (`/v1/workspaces/{workspaceUuid}/...`), you can pin the agent to a single workspace and grant only the calls it needs, such as reading contacts and organisations. Destructive operations like removing a tag from an organisation stay off limits unless you explicitly add them.