This page provides a comprehensive reference for understanding and handling errors across the Edges API. Use the Quick Reference Table for fast lookups, or dive into the detailed sections for specific error handling guidance.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.
Quick Reference Table
| Error Label | HTTP Code | Category | Retry? |
|---|---|---|---|
BAD_INPUT | 400 | Input | No — fix input |
BAD_PARAMETERS | 400 | Input | No — fix parameters |
MISSING_PARAMETER | 424 | Input | No — add parameter |
NO_ACCESS | 402 | Access | No — check subscription |
STATUS_403 | 424 | Access | No — check permissions |
STATUS_404 | 424 | Not Found | No — resource doesn’t exist |
NO_RESULT | 424 | Not Found | No — empty result |
LIMIT_REACHED | 429/409 | Rate Limit | Yes - Use postponed_until then with backoff |
STATUS_429 | 429 | Rate Limit | Yes — Use postponed_until then with backoff |
LK_ERROR | 424 | No | |
LK_524 | 424 | Yes — wait & retry | |
LK_MISSING_DATA | 424 | No | |
LK_INMAIL_CANNOT_RESEND | 424 | No — wait for reply | |
LK_INMAIL_NOT_ENOUGH_CREDIT | 424 | No — add credits | |
LK_EVENT | 424 | No — check event | |
NOT_CONNECTED | 424 | No — connect first | |
SN_CONFLICT | 424 | Sales Navigator | No — already connected |
SN_OUT_OF_NETWORK | 424 | Sales Navigator | No — upgrade account |
NO_VALID_ACCOUNT_CONFIGURED | 424 | Config | No — configure identity |
INTEGRATION_ERROR | 424 | Config | No - contact support |
PROXY_ERROR | 424 | Config | Yes — Use postponed_until if present or wait 1 minute |
GENERIC_ERROR | 424 | Processing | No - contact support |
NO_DATA_LOADED | 424 | Processing | No |
MANDATORY_DATA_MISSING | 424 | Processing | No — check input |
UNDEFINED_FIELD | 424 | Processing | No — check input |
UNKNOWN_ERROR | 424 | System | Contact support |
ACTION_ABORTED | 422 | System | No - Check appendix |
API_MAX_RETRY | 424 | System | Conditional — yes if managed/auto |
API_TIMEOUT_ERROR | 424 | System | Yes |
GMAPS_NO_INTERCEPT | 424 | Input | No |
HPE_HEADER_OVERFLOW | 424 | System | No |
HTTP_RESPONSE_EMPTY | 424 | System | Depends — see insights |
LK_403 | 424 | No | |
LK_409 | 424 | No | |
LK_413 | 424 | No | |
LK_BAD_COOKIE | 424 | Yes if managed/auto — update integration | |
LK_LOGIN_ERROR | 424 | Yes if managed/auto | |
LR_ACCOUNT_UPGRADE | 424 | Yes if managed/auto | |
MISSING_COOKIE | 424 | Config | Yes if managed/auto |
RLS_BAD_COOKIE | 424 | Yes if managed/auto | |
SN_ACCOUNT_UPGRADE | 424 | Sales Navigator | Yes if managed/auto |
SN_LOGIN_ERROR | 424 | Sales Navigator | Yes if managed/auto |
RLS_LOGIN_ERROR | 424 | Yes if managed/auto | |
STATUS_400 | 400 | Input | No — API only |
STATUS_409 | 409 | System | No — API only |
STATUS_422 | 422 | System | No — API only |
HTTP_ERROR | 424 | System | Yes |
LK_GET_FEATURES_ERROR | 424 | Yes if managed/auto | |
LK_ACCOUNT_UPGRADE | 424 | Yes if managed/auto | |
RUN_MAX_RETRY | 424 | System | No — run async only; resume resets retry_count |
OUTPUT_VALIDATION_FAILED | 424 | Processing | No — contact support |
Error Response Structure
The API uses a consistent error response format across all endpoints. When an error occurs, you’ll receive a response with the following structure:error_label: A machine-readable identifier for the error typeerror_scope: Indicates which part of the request caused the error (e.g., “input”, “auth”, “server”)error_ref: A unique reference code for tracking and debuggingmessage: A human-readable description of the errorstatus_code: The HTTP status codeparams: Additional error parameters (if any)
200: The request was successful (some API calls may return 201 instead)400: Bad Request - Invalid input or parameters401: Unauthorized - Invalid or missing API key403: Forbidden - Insufficient permissions404: Not Found - Resource doesn’t exist424: Failed Dependency - Used to wrap LinkedIn-specific error codes with an additionalerror_label500: Internal Server Error - Server-side issue
Why we use 424 for LinkedIn errors: We use the
424 Failed Dependency status code to wrap all LinkedIn-specific error codes. This is because a 404 (or any other error code) from LinkedIn doesn’t imply the same error code on our own APIs. For example, if LinkedIn returns a 404 for a profile that doesn’t exist, that doesn’t mean our API endpoint is returning a 404 — it means the dependency (LinkedIn) failed. The specific LinkedIn error is indicated in the error_label field (e.g., STATUS_404, NO_RESULT, etc.).If you encounter an unusual error, such as a 500 or 503, feel free to reach
out! These are internal errors on our end, and we’re happy to help resolve
them.
Understanding Error Scopes
Every error response includes anerror_scope field that indicates what caused the error:
| Scope | Description | Typical Action |
|---|---|---|
input | The input data provided is invalid | Fix the input format or value |
param | A parameter in the request is invalid | Check parameter requirements |
config | Configuration issue (identity, integration) | Verify your setup in the dashboard |
integ | Third-party integration error (LinkedIn) | Check resource availability or retry later |
Handling Rate Limit Errors (429)
429 errors indicate that you’ve exceeded a rate limit imposed by either Edges or LinkedIn. It’s crucial to identify the source of the limit to apply the appropriate handling strategy.
A 429 Too Many Requests error means you’ve exceeded a usage limit — but it’s important to identify which system triggered it.
| Source | Identifier | Retry Strategy |
|---|---|---|
| Edges API | X-RateLimit-Type header | Use Retry-After header + exponential backoff |
| LinkedIn (guarded) | error_label = LIMIT_REACHED | Check params.appendix and params.timespan to distinguish limit type (e.g. API_FUSE_LIMIT/Daily, MINUTE_LIMIT/Minute). Wait for the relevant window to reset. |
| LinkedIn (raw) | error_label = STATUS_429 | Apply exponential backoff. Do not retry aggressively. |
- Monitor identity usage via
/identities/{identity_uid}/actions/{action_slug}/limits - Avoid parallel tools or conflicting automation platforms
- Match identity timezones with VPNs and login locations
Handling LinkedIn Errors (424)
424 errors indicate a failed dependency — we use this status code to wrap all LinkedIn-specific error codes. It’s important to identify the specific error_label to determine the appropriate handling strategy.
A 424 Failed Dependency error means the external service (LinkedIn) returned an error — the error_label will tell you which LinkedIn error occurred.
Why we use 424 for LinkedIn errors: We use the
424 Failed Dependency status code to wrap all LinkedIn-specific error codes. This is because a 404 (or any other error code) from LinkedIn doesn’t imply the same error code on our own APIs. For example, if LinkedIn returns a 404 for a profile that doesn’t exist, that doesn’t mean our API endpoint is returning a 404 — it means the dependency (LinkedIn) failed. The specific LinkedIn error is indicated in the error_label field (e.g., STATUS_404, NO_RESULT, etc.).
