How to Search Sansan Business Cards with AI Chat | Check Past Contact Before a Sales Meeting via the API

Before a sales meeting, you sometimes want to check whether anyone at your company has already met someone from that company. Even when the cards are in Sansan, searching by company name, opening cards one at a time, and copying down the owner and exchange date takes effort. This article is for salespeople who use Sansan and the administrators who set it up. It explains how to search Sansan business cards and contact records from AI chat.

It also covers how to use Sansan's official API (Sansan Open API) and what to decide when connecting it to AI.

The short answer

  • Sansan has an official API (Sansan Open API). An API key is issued per user, and cards are read with the permissions of the person who issued that key. To issue one, you first need permission to use the API from your company's Sansan administrator
  • Samurai App's Sansan integration only reads cards, people, tags, and contact records. It does not register, edit, or delete cards or contacts. It does not handle card images either
  • After an admin or manager turns on Sansan, each user registers their own API key. The cards they can read are the same as their own permissions in Sansan
  • For research before a sales meeting, combine three things: search the company's cards by company name, look at the latest card for the same person, and list meeting and email records for a set period

Three ways to search Sansan business cards

Search in the Sansan screens Use the Open API in your own tools Read through the API from AI chat
What you need A Sansan account An API key and a mechanism that calls the API An API key and an AI that supports API integrations
Best for Checking one person's card Regularly copying cards into a CRM or similar Searching while changing conditions in conversation
Effort to compile A person copies it down Depends on what you built The AI turns it into a table or summary

Searching in the Sansan screens is the most reliable. You can check everything, including the card image. In exchange, rearranging search results by company or cross-checking them against other records is a person's job.

Sansan Open API is the API Sansan publishes. According to the official reference, you call it with the API key in the request header and can fetch cards, people, tags, contacts, and more. API keys are issued per user, and calls are limited to 10 per second per key. Use of the API is subject to Sansan's API terms of use.

Reading through the API from AI chat hands the Open API reads to an AI. You can search while changing how you ask, such as "this company's cards across the whole company" or "last month's meeting records." Samurai App's Sansan integration works this way.

What Samurai App can and cannot do

What you can do from chat

  • Check which Sansan user you operate as
  • Search cards by company name, person's name, email, phone number, or tag. Company name and phone number are partial matches, person's name is a prefix match, and email is an exact match. Results are sorted by newest registration, up to 100 per request (25 by default)
  • By default, the search covers cards you own. Ask "across the whole company," and it searches every card you can see
  • View one card. It returns company name, department, title, name and its reading, email, phone, mobile, fax, URL, address, exchange date, owner, notes, and tags
  • View the latest card among those grouped as the same person
  • View the list of tags
  • List contact records (meetings, calls, emails, card exchanges, and so on) for a set period. The period is specified by when the record was updated, sorted by most recently updated

What it cannot do

  • Register, edit, or delete cards or contacts. Sansan's API has registration endpoints too, but Samurai App does not use them
  • View card images
  • View cards you cannot see in Sansan. The scope is set by the permissions of the person who owns the registered API key
  • Operate with someone else's API key. It can be used only from the conversations of the person who registered it

Later pages of search results have to be fetched again once 6 hours have passed since the first page was fetched.

Using it to check past contact before a sales meeting

For research before a meeting, asking for these three things in order means less back-and-forth:

  • Search the other company's cards across the whole company. Ask "Search [company] Trading Co., Ltd. cards across the whole company and make a table of the owner, exchange date, and the other person's department and title." You can see who has met people from this company and decide whom to talk to before the meeting
  • View the latest card for the person you are meeting. Ask "From [name]'s card, show me the latest card for the same person," and you get the latest one among the cards Sansan has grouped as the same person. You can check whether their department or title has changed since you last exchanged cards
  • List recent contact. Ask "From contact records updated in the last 3 months, list meetings and emails with [company] Trading." Contact records cannot be filtered by company name, so the AI picks out the ones for that company from the list for the period. A longer period means more records, so start with a few months

What you learn here is the contact that remains on record inside your company. How to research outside information, such as the other company's business and recent news, is covered in How to Research a Company Before a Sales Meeting, and What to Prepare First. Put the two together, then decide what to talk about.

What you need

  • A Samurai App admin or manager (the person who turns on Sansan)
  • A Sansan account and permission to use the API from your company's Sansan administrator (for each user)
  • A rule for how widely search results may be shared inside the company. Cards contain personal contact details

Steps

1. The administrator turns on Sansan

Open the Connectors screen (/settings/connections) and press "Add API integration" on the "API integrations" tab. Choose Sansan from the list of services and press "Turn on Sansan."

At this point, nobody can read cards yet. Samurai App does not hold a company key; each user registers their own API key.

2. Each user registers their own API key

Each person who will search cards registers in this order:

  1. Get permission to use the API from your company's Sansan administrator
  2. Open [Settings] > [API Key] from the menu at the top right of Sansan and issue an API key
  3. On Samurai App's "API integrations" tab, open the Sansan row, paste it into the "API key" field, and press "Register Sansan API key"

When registration is done, "In Sansan, you operate as (name)" is shown. Cards are read with the permissions of the person shown here.

Do not share your API key with anyone. Whoever holds the key can read the same cards as the person who issued it. Do not paste it into the chat input either.

3. Ask in chat

In chat, be specific about whom you are meeting and what you want to know.

I have a sales meeting tomorrow at 2 p.m. with [name] from [company] Trading Co., Ltd.
Search business cards across the whole company in Sansan, and make a table of employees who have met people from this company, the dates they exchanged cards, and the other person's department and title

After seeing the results, keep asking.

Check [name]'s latest card to see whether their department and title have changed from the earlier card.
Also, from contact records updated in the last 3 months, list meetings with [company] Trading

You can paste the returned table into your meeting prep notes. When you ask the employee who owns the card how the last meeting went, the exchange date and notes also give you something to go on.

Things to watch

The cards you can read are the same as your own permissions in Sansan. Even if you ask "across the whole company," cards you cannot see in Sansan are not returned. This is why results differ from person to person.

If the API key is disabled in Sansan, the registration stops working too. If it reports that it cannot be used, issue a new key and register again. When an administrator turns off Sansan, everyone's registered API keys are deleted. The cards and contacts in Sansan stay as they are.

Card information may be out of date. A card holds the information as of when it was exchanged. Even the latest card for the same person does not show transfers after that. Before an important meeting, check the other company's website or a message from the person themselves.

Do not spread personal contact details widely. Do not paste the email addresses or mobile numbers from cards into unrelated channels or documents. Share only what the meeting needs.

Frequently asked questions

Which contracts allow use of the Sansan API?

As of November 9, 2026, the official Sansan Open API reference did not say which contracts or plans can use it. To issue an API key, you need permission to use the API from your company's Sansan administrator. Check the contract terms with your Sansan administrator or Sansan representative.

Can I register cards or add notes from chat?

No. Samurai App's Sansan integration is read-only. Register cards and edit notes and tags in the Sansan screens.

Can I see cards that other employees exchanged?

You can read any card you can see in Sansan. Ask "across the whole company," and it searches every card you can see, not only the ones you own. What you can see is set by Sansan's permission settings.

Can I see card images?

No. This integration reads only the text information on cards. To check the image, open the card in the Sansan screens.

Can I record a meeting in Sansan after it ends?

Not from Samurai App. Contact records can only be listed and read. Record meetings in the Sansan screens.

Sources

Based on the official Sansan Open API reference as of November 9, 2026.

Related featureConnect business tools to AI over MCPSamurai App connects your business tools to AI over MCP. Operate accounting and HR SaaS from chat within each person's own permissions, call the agent from Slack or Teams, and use it from outside AI clients over MCP.

More automation examples

    Back to How-to articles

    Everyday work comes together, connects, and becomes the company's strength.

    Contact usOpen Samurai App

    See the demoContact us