Unipile

Unipile's API integrates messaging, email, and calendar functionalities into your app, offering a seamless communication experience.

[Unipile @UnipileAPI]

LinkedIn returns 429 with a Retry-After header. We relay it as-is, we never invent a stricter limit on top.

Every request runs on behalf of the authenticated user. Cadence stays a customer-side decision, not ours.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

Point your coding agent at it (Codex, Cursor, Claude Code or Gemini CLI) and describe the feature:
→ sync each recruiter's LinkedIn inbox into your ATS
→ reply to candidates from your own UI
→ people search, Sales Navigator, Recruiter

https://t.co/9TxvWHAPQJ

[Unipile @UnipileAPI]

Pulling 6 months of Gmail thread history in one GET request times out or truncates.

Cursor-based pagination: page through message history until the cursor comes back null.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

@toddsaunders we created it : https://t.co/RVB5WBo5oK

[Unipile @UnipileAPI]

Instagram rate limits you on message 40 of a sync job.

Exponential backoff, not a retry loop: 1s, then 2s, then 4s. Hammering a 429 just earns a longer cooldown.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

Your webhook endpoint is a public URL. Anyone with it can POST a fake message.received and watch your automation fire.

Verify the signature header before you trust the payload. Every single time.

https://t.co/pYbbGUQ2oI
#API

[Unipile @UnipileAPI]

https://t.co/G6f0IciZJP landed in our webhook before message.received, same message.

Under load, delivery order isn't guaranteed. Sort by event timestamp, never by arrival order.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

Outlook revoked the refresh token mid-sync. Nobody needs to page an engineer for that.

account.disconnected fires, the user clicks one hosted reauth link, account.reconnected fires back. No redeploy.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

Proposing a slot without checking free-busy first is how you double-book a prospect's calendar.

GET free-busy, find the actual gap, then POST the event.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

Telegram sends one payload shape. Instagram sends another. Outlook sends a third.

One webhook URL for all of it. We normalize the shape before it reaches your endpoint.

https://t.co/pYbbGUQ2oI
#API #DevTools

[Unipile @UnipileAPI]

Cheap leads are easy. Current leads aren't.

Those providers are selling you LinkedIn data from 6 months ago.
Give the agent the user's own LinkedIn session instead.

API. On behalf of the authenticated user. No scraping.

[Jason Zhou @jasonzhou1993]

Introducing Claude for people-search

No more $600 subscriptions, juts $0.0089/lead

Claude is now the best people finder in the world

#1 on People Search Bench
Fully open source, 0% markup

Try it at https://t.co/s60Ye4EO3h

Git Repo below 👇

[Unipile @UnipileAPI]

Hope you can find great staff here :https://t.co/qC5mpawtPx

[Andrey @Andrey__HQ]

We've just replaced LinkedIn capabilities by enabling our agents to take actions on our behalf

AgentWeb has indexed LinkedIn entirely (without violating TOS) to do anything a user can do

Made possible with AgentWeb (only)

[Unipile @UnipileAPI]

Yes it's true, hard to find a good LinkedIn API..:)
I think you're in the right place

[Vinayak Kamath @vin_kamath]

Did you know you can access LinkedIn over MCP?

Most apps today, including CRMs like Recruit CRM, which have linkedin connectivity rely on @UnipileAPI. Unipile themselves rely on https://t.co/OefSQoIbnh, which is a open source MCP server for LinkedIn that you can run locally.

[Unipile @UnipileAPI]

Telegram sends chat_id. Gmail sends threadId. WhatsApp sends https://t.co/w51MOmFVkN.

Your webhook handler sees one shape: message.received, same schema, every provider.

https://t.co/V0u4wXR8LO
#API #DevTools

[Unipile @UnipileAPI]

Gmail wants OAuth 2.0 + PKCE. Outlook wants MSAL and the Graph API. IMAP wants an app password.

Three auth flows to send one email.

Or one API key and POST /emails.

https://t.co/pYbbGUQ2oI

[Unipile @UnipileAPI]

Your webhook just fired twice for the same message.

That's not a bug, that's at-least-once delivery. Dedup on message_id before you process it, or you'll double-send replies.

https://t.co/V0u4wXR8LO
#API

[Unipile @UnipileAPI]

Your booking request times out. You retry. Now the prospect has 2 calendar invites for the same slot.

Idempotency-Key header fixes it. Same key, same booking, no duplicate.

https://t.co/V0u4wXR8LO

[Unipile @UnipileAPI]

Your AI agent doesn't hold a credential. Your user does.

One hosted auth flow per user. Every API call after that passes account_id, scoped to their session, on their behalf.

No shared service account touching hundreds of inboxes.

https://t.co/V0u4wXR8LO

[Unipile @UnipileAPI]

WhatsApp's 200 OK just means your message left the queue.

Delivered? Read? That's a separate webhook: message.status.

Sent on behalf of the authenticated user, tracked async.

https://t.co/V0u4wXR8LO