> ## Documentation Index
> Fetch the complete documentation index at: https://docs.edges.run/llms.txt
> Use this file to discover all available pages before exploring further.
# Engagement Identities
> Learn how to use Engagement Identities to run LinkedIn outreach actions without consuming credits.
## What are Engagement Identities?
**Engagement Identities** are a special type of identity on Edges, allowing you to run a broad set of outreach actions on LinkedIn and Sales Navigator **without consuming credits**.
They are ideal for building SaaS products or AI agents that enable users to engage on LinkedIn or create outreach sequences, while optimizing credit costs at scale.
Engagement Identities must be **enabled first** from the [Developer Settings](https://app.edges.run/settings/developers) page. Billing details must be filled before activation is confirmed.
### Key Benefits
* Access a predefined list of **free outreach actions**
* Keep using all other actions — paid at the normal credit rate
* Create Engagement Identities via UI or API
* Billing by contract: a monthly peak of active identities, or a fixed pool
* Live feedback on current billing status
### Identity Types Comparison
| | Standard Identity | Engagement Identity |
| - | - | - |
| Credit-free outreach | ❌ | ✅ |
| Other actions cost credits | ✅ | ✅ |
| Billed | No *(included in plan)* | Yes *(monthly peak or fixed pool)* |
| API `type` field | `standard` | `engagement` |
## Pricing & Billing
Billing follows the contract. On a **monthly active-identity** contract, the invoice is the **peak** number of active Engagement Identities in the cycle. On a **fixed pool**, usually billed annually, the contracted count stays as agreed for the term.
### When is an Engagement Identity active or inactive?
* **Active** — An Engagement Identity is counted as active when:
* You **add a LinkedIn integration** to it (connect an account), or
* You **call an action** with that identity (e.g. message, connect, extract conversations).
* **Inactive** — An Engagement Identity becomes inactive when:
* It has **not been used in any action** for **30 days**, or
* You **synchronized a LinkedIn account** but have **not called any action** with that identity for **5 days**.
What inactivity does to the invoice depends on the contract:
* **Monthly, active identities.** The identity stops counting toward the billed peak until it is active again — you run an action with it, or connect an integration.
* **Fixed pool, usually annual.** The contracted count stays as agreed. Inactivity is the signal to disconnect that identity from the pool yourself.
Which of these applies depends on the contract: billing frequency and the price per identity. Confirm yours with [support](mailto:support@edges.run).
### How we count: peak of active Engagement Identities
This is the monthly active-identity contract. The charge is the **maximum number of active Engagement Identities** at the same time during the cycle.
**Example:** You start the month with 5 active Engagement Identities. You add 3 more (8 active). Then 2 become inactive (6 active). You add 2 more (8 active). Later, 3 become inactive (5 active). You are billed for **8** — the highest count of active Engagement Identities during the month — even though 10 Engagement Identities were active at some point.
On a monthly active-identity contract, Engagement Identities are billed on the **peak number of active Engagement Identities** in the billing cycle.
* **Starting at \$7.99/identity/month**
* **Pricing is dynamic**: unit cost decreases as volume increases.
* Pricing details available at [edges.run/pricing?mode=outreach](https://edges.run/pricing?mode=outreach).
### Billing Examples
These examples are for a monthly active-identity contract.
| Scenario | Current Cycle Billed | Next Cycle Billed |
| - | - | - |
| Peak of **10** active Engagement Identities, then you delete all 10 | 10 | 0 |
| Peak of **10** active Engagement Identities, delete 10, recreate 10 (all active again) | 10 | 10 |
| Peak of **3** active Engagement Identities, delete 1, don't recreate | 3 | 2 |
| Peak of **3** active Engagement Identities, delete 1, recreate 1 | 3 | 3 |
## Quick Start
1. **Enable Engagement Identities** in [Developer Settings](https://app.edges.run/settings/developers) and fill billing details
2. **Create an Engagement Identity** via API with `"type": "engagement"`
3. **Connect a LinkedIn account** to your Engagement Identity using the [Connect Integration](/v1/api/integrations/connect) endpoint
4. **Execute actions** — use any of the included actions listed below; they'll run without consuming credits
## Included Actions
The following actions are included for free when executed via an Engagement Identity:
| Action | Endpoint |
| - | - |
| **Connection Actions** | |
| Connect LinkedIn Profile | [`linkedin-connect-profile`](/v1/api/actions/linkedin-connect-profile) |
| Connect Sales Navigator Profile | [`salesnavigator-connect-profile`](/v1/api/actions/salesnavigator-connect-profile) |
| Accept LinkedIn Received Invitations | [`linkedin-accept-invitations`](/v1/api/actions/linkedin-accept-invitations) |
| Withdraw LinkedIn Pending Invitations | [`linkedin-withdraw-invitations`](/v1/api/actions/linkedin-withdraw-invitations) |
| Follow LinkedIn Profile | [`linkedin-follow-profile`](/v1/api/actions/linkedin-follow-profile) |
| **Messaging Actions** | |
| Message LinkedIn Profile | [`linkedin-message-profile`](/v1/api/actions/linkedin-message-profile) |
| Send LinkedIn InMail | [`linkedin-inmail-profile`](/v1/api/actions/linkedin-inmail-profile) |
| Send Sales Navigator InMail | [`salesnavigator-inmail-profile`](/v1/api/actions/salesnavigator-inmail-profile) |
| **Engagement Actions** | |
| Like LinkedIn Post | [`linkedin-like-post`](/v1/api/actions/linkedin-like-post) |
| Comment LinkedIn Post | [`linkedin-comment-post`](/v1/api/actions/linkedin-comment-post) |
| Visit LinkedIn Profile | [`linkedin-visit-profile`](/v1/api/actions/linkedin-visit-profile) |
| Visit Sales Navigator Profile | [`salesnavigator-visit-profile`](/v1/api/actions/salesnavigator-visit-profile) |
| Invite People to LinkedIn Event | [`linkedin-invite-event`](/v1/api/actions/linkedin-invite-event) |
| **Extract Actions** | |
| Extract LinkedIn Connections | [`linkedin-extract-connections`](/v1/api/actions/linkedin-extract-connections) |
| Extract LinkedIn Conversations | [`linkedin-extract-conversations`](/v1/api/actions/linkedin-extract-conversations) |
| Extract LinkedIn Messages | [`linkedin-extract-messages`](/v1/api/actions/linkedin-extract-messages) |
| Extract LinkedIn Followers | [`linkedin-extract-followers`](/v1/api/actions/linkedin-extract-followers) |
| Extract LinkedIn Page Followers | [`linkedin-extract-page-followers`](/v1/api/actions/linkedin-extract-page-followers) |
| Extract LinkedIn Profile Viewers | [`linkedin-extract-profile-viewers`](/v1/api/actions/linkedin-extract-profile-viewers) |
| Extract LinkedIn Received Invitations | [`linkedin-extract-received-invitations`](/v1/api/actions/linkedin-extract-received-invitations) |
| Extract LinkedIn Sent Invitations | [`linkedin-extract-sent-invitations`](/v1/api/actions/linkedin-extract-sent-invitations) |
## Usage Guide
### Requirements & Limitations
* **Account levels matter**: Actions requiring Sales Navigator will only work if the underlying LinkedIn account has proper access.
* The API's global **rate limit** applies (default: 120 req/min).
* A **reasonable usage** is expected to avoid overload for Edges and client platforms. Abuse may result in throttling or degradation.
### API Usage
You can manage Engagement Identities via API using the `type` parameter. See the [Create an Identity](/v1/api/identities/create) endpoint for full request body details.
```bash theme={null}
# Create an Engagement Identity
POST /v1/identities
{
"name": "Sales Outreach Identity",
"timezone": "America/New_York",
"type": "engagement"
}
```
The identity `type` cannot be changed after creation. If you need to switch an identity from `standard` to `engagement` (or vice versa), you must delete the existing identity and create a new one with the desired type.
Each identity response includes a `type` field indicating whether it's `"standard"` or `"engagement"`.
### Monitor Your Usage
You can monitor your monthly Engagement Identity usage directly in the [Identities page](https://app.edges.run/identities) in the Edges dashboard. It shows your current peak of active Engagement Identities and billing forecast for the cycle.
Use Engagement Identities for high-volume, repetitive outreach actions (connect, message, follow) and keep standard identities for more occasional or data extraction workflows.
## Need Help?
Reach out to the Edges team via chat or at [support@edges.run](mailto:support@edges.run) for assistance with activation, billing, or best practices.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.