Overview

Unipile uses a Restful / CRUD approach on methods and you can explore all endpoints in the API Reference, under Methods category.

They are organized into distinct sub-groups based on the features offered by providers. Each API group focuses on manipulating specific types of resources:

• Messaging API, for messaging providers with Chats, Messages, and Groups
• Emails API, for emailing providers, with Emails, Drafts and Folders
• Calendar API, for calendar providers, with Calendars and Calendar Events
• Users API, for social providers with User Profiles and Relations
• Posts API, for social providers with Posts and Comments
• Specific API, for providers that have anything that does not fit in any other API. For ex: Linkedin have an API to get Companies and Hiring projects which are resources specific to LinkedIn

Before making your first API calls, you need to authenticate your requests using API keys.

Because Unipile relies on underlying providers, all operations are subject to provider-specific constraints such as rate limits, quotas, and feature availability.
To handle these constraints safely and consistently, Unipile enforces rate limiting rules and provides a built-in caching layer.

Next Steps

The following guides walk you through authentication, caching, and rate limits before you dive into the full API Reference.