How to Connect Sansan MCP to an AI Agent
Auth setup
1. Register at developer.sansan.com. 2. Create OAuth application. 3. Note: API key auth was removed in March 2026 — must use OAuth 2.0 now.
Key facts
| Base URL | https://api.sansan.com/v8/ |
|---|
| API version | v8 |
|---|
| Auth | OAuth 2.0 (since March 2026, replacing API key auth). Register at developer.sansan.com. Client credentials or Authorization Code flow. |
|---|
| Token URL | https://api.sansan.com/oauth/token |
|---|
| Scopes | bizcard:read,user:read |
|---|
| Request body | application/json |
|---|
| Pagination | cursor-based: response includes 'hasMore' and 'nextPageToken'. Pass as pageToken param. |
|---|
| Rate limit | 1,000 requests/hour. HTTP 429 with Retry-After. |
|---|
| Error format | JSON: {"error":{"code":"NOT_FOUND","message":"...","details":[]}} |
|---|
Key endpoints
| Method | Path | Description |
|---|
GET | /bizcards | Search business cards |
GET | /bizcards/{id} | Get business card details |
GET | /users | List company users |
GET | /tags | List tags for organizing contacts |
Quickstart
GET /v8/bizcards?name=田中&limit=10 HTTP/1.1
Host: api.sansan.com
Authorization: Bearer {access_token}
Response: {"data":[{"id":"bc_123","personName":{"lastName":"田中","firstName":"太郎"},"companyName":"株式会社テスト","email":"tanaka@test.co.jp"}]}
Agent pitfalls & tips
- BREAKING CHANGE (March 2026): Authentication switched from API key to OAuth 2.0. Old API keys no longer work.
- Business card OCR accuracy is 98% — but always verify critical fields like email/phone for programmatic use.
- Name search supports both kanji (田中) and reading (たなか). Use 'name' param for both.
- Personal information (個人情報) handling: Sansan data contains real contact info. Comply with Japan's APPI (個人情報保護法).
- Read-only API — you cannot create or modify business card records via API.
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-04. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is Sansan MCP's AEO score?
▼
Sansan MCP has an AEO score of 0.90 and is rated AA (Strong agent support with minor gaps). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Sansan MCP AI-agent-ready?
▼
Sansan MCP is currently ✓ verified for AI agent use. It offers an official MCP (Model Context Protocol) server, which means AI agents can connect directly. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Sansan MCP compare to other CRM & Sales services?
▼
In the CRM & Sales category, Sansan MCP is rated AA. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Sansan MCP compares.
How can I integrate Sansan MCP with an AI agent?
▼
The fastest way to integrate Sansan MCP with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Sansan MCP?
▼
OAuth 2.0 (since March 2026, replacing API key auth). Register at developer.sansan.com. Client credentials or Authorization Code flow. Setup: 1. Register at developer.sansan.com. 2. Create OAuth application. 3. Note: API key auth was removed in March 2026 — must use OAuth 2.0 now.
What are Sansan MCP's API rate limits?
▼
1,000 requests/hour. HTTP 429 with Retry-After.