API Overview
Complete guide to the ConnectSafely API including authentication, rate limits, error handling, and endpoint groups for LinkedIn automation and data retrieval.
API Overview
The ConnectSafely API surfaces LinkedIn automation features that power the product UI. Each endpoint documented here comes directly from the main app and supports live testing via the Try it now playground.
Authentication
- Generate an API key from connectsafely.ai/api-key.
- Send it with every authenticated request as a Bearer token.
- Rotate keys regularly and never expose production keys in client-side code.
Authorization: Bearer <YOUR_API_KEY>Environments
| Environment | Base URL | Notes |
|---|---|---|
| Production | https://api.connectsafely.ai | Best data freshness and rate limits. |
| Sandbox | https://sandbox.api.connectsafely.ai | Safe for integration tests. Mirrors features but with throttled LinkedIn actions. |
Configure the docs playground using the Docs environment (proxied through this site). For production traffic, call the API from your backend services directly.
Endpoint Groups
- LinkedIn Account – Manage account status, activity history, and warmup settings.
- LinkedIn Actions – Follow, connect, and manage relationships with members.
- LinkedIn Posts – Read, react, comment, and create posts.
- LinkedIn Profiles – Retrieve enriched profile data and visitors.
- LinkedIn Groups – Search and manage LinkedIn groups.
- LinkedIn Messaging – Send messages and manage conversations.
- LinkedIn Search – Search for people, companies, jobs, and more.
- LinkedIn Analytics – Access creator analytics and engagement data.
Use the sidebar navigation to browse each group or jump directly using the shortcuts below:
- LinkedIn Account
- LinkedIn Actions
- LinkedIn Posts
- LinkedIn Profiles
- LinkedIn Groups
- LinkedIn Messaging
- LinkedIn Search
- LinkedIn Analytics
Rate Limits
Default allowance is 60 requests per minute with short-term bursts up to 100 requests per 10 seconds. Contact support if you need higher throughput.
Error Handling
Errors follow a consistent shape:
{
"success": false,
"code": "validation_error",
"message": "Explanation of what went wrong"
}Always check the HTTP status code and the success field before processing data.
Changelog
Endpoint docs are generated from the canonical specification inside the web application. Regenerate the docs (bun run generate:api) whenever the product team updates the in-app documentation.