Unipile (@UnipileAPI) header
Unipile (@UnipileAPI) profile picture

Unipile

@UnipileAPI

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

 France
unipile.com
Joined January 2021
  • Tweets157
  • Following11
  • Followers173
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. developer.unipile.com
Code card: GET /users/relations returns HTTP 429 Too Many Requests with Retry-After 3600. Comments: LinkedIn's limit relayed as-is, cadence stays a customer-side decision.

ALT Code card: GET /users/relations returns HTTP 429 Too Many Requests with Retry-After 3600. Comments: LinkedIn's limit relayed as-is, cadence stays a customer-side decision.

1
1
109
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 unipile.com/mcp/linkedin
4
188
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. developer.unipile.com
Code card: GET /chats/{id}/messages with a cursor parameter returning items plus a cursor, paginating message history until the cursor is null.

ALT Code card: GET /chats/{id}/messages with a cursor parameter returning items plus a cursor, paginating message history until the cursor is null.

1
50
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. developer.unipile.com
Code card: retry sequence attempt 1 gets 429 wait 1s, attempt 2 wait 2s, attempt 3 wait 4s, attempt 4 gets 200 OK. Exponential backoff, not a retry loop.

ALT Code card: retry sequence attempt 1 gets 429 wait 1s, attempt 2 wait 2s, attempt 3 wait 4s, attempt 4 gets 200 OK. Exponential backoff, not a retry loop.

47
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. developer.unipile.com #API
Code card: hmac of secret and rawBody compared with timingSafeEqual, returning 401 if invalid. Check the signature before you trust the payload.

ALT Code card: hmac of secret and rawBody compared with timingSafeEqual, returning 401 if invalid. Check the signature before you trust the payload.

56
message.read landed in our webhook before message.received, same message. Under load, delivery order isn't guaranteed. Sort by event timestamp, never by arrival order. developer.unipile.com
Schema: message.read arrived at 14:02:01 and message.received at 14:02:03 for the same message, converging into a block that says sort by event timestamp.

ALT Schema: message.read arrived at 14:02:01 and message.received at 14:02:03 for the same message, converging into a block that says sort by event timestamp.

38
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. developer.unipile.com
Schema: account.disconnected (Outlook revoked the token) and hosted reauth (one link, no redeploy) converging into account.reconnected.

ALT Schema: account.disconnected (Outlook revoked the token) and hosted reauth (one link, no redeploy) converging into account.reconnected.

37
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. developer.unipile.com
Code card: GET /calendars/{id}/free-busy returns a busy list, then POST /events. Check free-busy first, then book.

ALT Code card: GET /calendars/{id}/free-busy returns a busy list, then POST /events. Check free-busy first, then book.

35
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. developer.unipile.com #API #DevTools
Schema: three providers with different payload shapes (Telegram chat.message, Instagram message_create, Outlook Graph delta) converging into a single POST /webhook.

ALT Schema: three providers with different payload shapes (Telegram chat.message, Instagram message_create, Outlook Graph delta) converging into a single POST /webhook.

37
Telegram sends chat_id. Gmail sends threadId. WhatsApp sends message.id. Your webhook handler sees one shape: message.received, same schema, every provider. developer.unipile.com #API #DevTools
Image from Unipile (@UnipileAPI)
1
65
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. developer.unipile.com
Image from Unipile (@UnipileAPI)
75
Load more