# How to answer API questions from LinkedIn prospects
> Handle API questions from LinkedIn prospects, prove your product fits their stack, and move the thread to a call without losing momentum. A short guide.
- HTML: https://getkinlead.com/respond-to-prospect-asking-about-api
- Markdown: https://getkinlead.com/respond-to-prospect-asking-about-api.md

**Short answer:** When a prospect asks about your API on LinkedIn, they are checking whether your product fits their stack before they commit to a call. Confirm the capability, give one concrete example, and ask what they are trying to connect. Send documentation after you know their goal, then suggest a short call to verify the implementation.

## Recognize the technical vet

When a prospect asks for API details on LinkedIn, they are testing whether your product fits their current stack. The URL matters less than the answer to one question: can this thing connect to what we already run? If you are vague, it looks like you have a feature gap. If you dump everything at once, they stop messaging and read alone.

Different buyers ask for different reasons. A founder usually wants to know if the integration is possible before they spend time on a call. A lead developer often looks for a reason to disqualify you so they don't have to sit through a demo. A product manager may be collecting options to compare next week. Your reply should give each one enough proof to keep talking.

The worst reply is a bare link. The second worst is a long feature list with no question. A good reply answers the technical question and gives the prospect a reason to tell you what they are building.

**The documentation dump**

- Here is the link to our full API docs: [link]. Let me know if you have questions!
- Yes, we have an API. You can find everything you need in our developer portal.

**The guided response**

- Yes, we have a REST API. Most teams use it to sync data into custom dashboards. Are you automating a specific workflow?
- We support OAuth and have a full REST API. To make sure I send the right section of the docs, are you focusing on data export or event triggers?

## The three part response framework

You need technical credibility and sales momentum in the same message. The shape that works is confirm, prove, pivot. Confirm the capability in plain terms. Prove it with one real example. Pivot to the integration goal so the conversation stays about their problem.

This keeps the thread from turning into a support ticket. You stay in the role of a consultant helping them solve a problem. The prospect gets a useful answer, and you learn whether a call is worth booking.

Keep the first reply short. You can go deeper once they tell you what they are connecting. A long answer before you know their goal often answers the wrong question.

1. **Confirm the capability.** Start with a direct yes or no. Use the terms your buyer used: REST API, OAuth, webhooks, rate limits. If the answer is no, say so and name the closest workaround.
2. **Give one specific example.** Mention how a customer uses the API. Keep it short. 'A 40-person agency uses our export endpoint to push invoice data into their reporting tool every night.' That is enough proof.
3. **Ask the integration goal question.** Ask which tool or internal workflow they want to connect. This moves the focus from the endpoint to the outcome.
4. **Offer the next step.** Suggest a short call to verify mapping, auth or data volume. Keep it to 10 or 15 minutes and name two times.

## Handling the request for documentation

Asking for docs is often a polite way to avoid a call. If you send the link and nothing else, you lose the chance to qualify the need. The prospect reads alone, gets stuck, and may never reply.

Send the link after you know their goal. Then point them to the section that matches their use case. That turns a passive reading exercise into an active conversation, and it gives you a reason to follow up.

If they insist on the full docs, send them. Add one line: 'The export and auth sections are the two that matter for most teams.' That small bit of guidance keeps you useful without turning the thread into a support queue.

- **them:** Can you just send over the API docs?
- **you:** Yes. Our docs cover auth, export and webhooks, so I can point you to the section that matches your goal. Are you automating data export or triggering actions from events?
- **them:** Mostly automating data export into our CRM.
- **you:** Here is the export section and a sample payload. If that looks right, let's spend 10 minutes on Tuesday to check the data mapping against your CRM setup.

## Moving from technicals to a meeting

The transition from technical detail to a booking is where many threads go quiet. A message that ends with 'Let me know if this helps' gives the prospect permission to disappear. End with a specific question or a suggested time instead.

Link the technical capability to an implementation detail that needs a call. Data mapping, auth setup, rate limits and migration steps are good reasons to talk. The value shifts from how the API works to how it solves their problem.

Name two times. Keep the call short. A 10-minute screen share to check a payload is easier to accept than a 30-minute demo with no agenda.

| | Conversation stage | Weak approach | Strong approach |
| --- | --- | --- | --- |
| After sending docs | Let me know if the docs work for you. | The API handles the export, but the mapping depends on your CRM version. Let's jump on a call to verify. |
| Confirming a feature | Yes, we support that endpoint. | We support that endpoint. I can show you the exact payload for your use case on a 10-minute call. |

> End with a specific question or a suggested time for a short call. 'Let me know' gives the prospect an easy exit.

## Qualifying the buyer behind the API question

Not every API question deserves the same response. Your answer should change based on who is asking and what happens after the call. A founder who wants to check feasibility may need a short yes and a clear next step. A developer who is evaluating tools may need a sample payload and a specific doc section. A procurement lead may need a security or data residency answer before anything else.

Ask one qualifying question before you go deep. 'What are you connecting?' is usually enough. If they name a system you do not support, say so early. That saves both sides time and keeps your credibility intact.

Write down the answers you give most often. If the same three questions come up every week, turn them into a short reply template you can adapt. That is faster than rewriting the same explanation from scratch.

- Founder checking feasibility: wants a yes, a simple example, and a short call.
- Developer comparing tools: wants auth details, a sample payload, and a doc section.
- Product manager collecting options: wants a clear use case and a reason to shortlist you.
- Procurement or security lead: wants data handling, permissions and contract details.

## Keeping the conversation moving when the answer is no

Sometimes the honest answer is no. You do not support that endpoint, that auth method or that data volume. Say that in the first line. Then offer the closest option or a workaround.

A clear no with a path forward often builds more trust than a vague yes. It also protects you from a bad demo where the technical fit falls apart. If the gap is on your roadmap, say what is available today and what is planned, without promising a date you cannot keep.

Use the same structure when the prospect goes quiet. Send one short follow-up with a specific question. If they do not reply, leave it. A technical buyer who needs the feature will come back when the timing changes.

```
Thanks for the detail. We do not support [specific method] today. The closest option is [workaround], which works for [use case]. If that fits, I can show you the setup on a 10-minute call. If not, I will point you to the part of our docs that covers [alternative].
```

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept. The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented.

1. **Find technical leads.** Use the Steal Customers agent to turn commenters on competitor technical posts into leads.
2. **Personalize the opening.** Use AI-written notes under 200 characters to mention the specific post they commented on.
3. **Control the hand-off.** Set the campaign reply mode to hand-off so you personally handle technical API questions and can move them to a call.
4. **Scale with API.** Use the REST Agent API or MCP server to check replies and draft answers based on your technical playbook.

## Related

- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Booking LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)

## Common questions

**What if I don't have a public API yet?**

Be honest and focus on the roadmap. Tell them you have a private API for select partners and ask what functionality they need to see if you can grant early access.

**How do I handle a prospect who refuses to call without seeing the code?**

Provide a small, specific sample payload or a snippet of the documentation. Explain that the code is one part of the implementation and a call saves them hours of trial and error.

**Should I involve a sales engineer in the LinkedIn thread?**

Only after you qualify the business need. A technical expert can answer depth questions, but the thread should still have a clear next step.

**How long should I wait before sending the docs?**

Send the link in the same reply if they asked for it, but add one sentence about which section matters. If they have not shared a goal, ask one question first.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
