Skip to main content
GET
/
identities
/
{identity_uid}
/
actions
/
{action_slug}
/
limits
Get the integrations limit for an identity on a specific action
curl --request GET \
  --url https://api.edges.run/v1/identities/{identity_uid}/actions/{action_slug}/limits \
  --header 'X-API-Key: <api-key>'
{
  "identity_uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "action_slug": "<string>",
  "level": "<string>",
  "standard_level": "<string>",
  "limits": [
    {
      "id": 123,
      "name": "<string>",
      "slug": "<string>",
      "max_limit": 123,
      "consumed": 123,
      "has_reached_limit": true,
      "started_at": "2023-11-07T05:31:56Z",
      "ended_at": "2023-11-07T05:31:56Z",
      "remaining": 123,
      "last_consumption_at": "2023-11-07T05:31:56Z",
      "first_consumption_at": "2023-11-07T05:31:56Z",
      "available_at": "2023-11-07T05:31:56Z"
    }
  ]
}

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.

This endpoint retrieves the current usage limits and consumption data for a specific action on a given identity. It helps you monitor how close an identity is to reaching its limits for a particular action. Edges applies Smart Limits to prevent LinkedIn accounts from getting restricted. These limits operate on a 24-hour sliding window and help stay within LinkedIn’s daily action caps.
This endpoint is specific to Edges Smart Limits and tracks only actions performed within the platform. It does not guarantee that LinkedIn won’t impose its own restrictions.
Evaluating limits in real-time is a consuming operation. Use this endpoint sparingly to avoid performance issues. It is rate limited along with other identity management operations.
For more details about Smart Limits, best practices, and how to handle rate limits, see our LinkedIn Rate Limits documentation.

​
Understanding the Response

Some actions consume multiple limits internally. For example, linkedin-message-profile may consume LK_MESSAGES_SENT, LK_PROFILE_ENRICHMENTS, and LK_GET_CONTACT_INFO depending on the operation. This is why querying limits for a single action may return multiple limit objects in the limits array.
When checking if an action can be performed, ensure all returned limits have has_reached_limit: false. If any limit is reached, the action may be blocked.
For a full list of limit slugs and their meanings, see the LinkedIn Commercial Limits table.

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
identity_uid
string<uuid>
required

Account UID

​
action_slug
string
required

Action slug

Response

Default Response

​
identity_uid
string<uuid>

Unique identifier for the identity

​
action_slug
string

Slug representing the action (e.g. linkedin-extract-people)

​
level
string

Integration level of the account required for the action

​
standard_level
string

Standardized Integration level of the account required for the action

​
limits
object[]

List of usage limits and consumption data