Skip to main content
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.
Two levels of reading: Each action’s documentation includes the specific errors it can return. This page provides the overall error landscape across all actions, helping you build robust error handling in your integrations.

Quick Reference Table


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:
Each error response includes:
  • error_label: A machine-readable identifier for the error type
  • error_scope: Indicates which part of the request caused the error (e.g., “input”, “auth”, “server”)
  • error_ref: A unique reference code for tracking and debugging
  • message: A human-readable description of the error
  • status_code: The HTTP status code
  • params: Additional error parameters (if any)
Common HTTP status codes:
  • 200: The request was successful (some API calls may return 201 instead)
  • 400: Bad Request - Invalid input or parameters
  • 401: Unauthorized - Invalid or missing API key
  • 403: Forbidden - Insufficient permissions
  • 404: Not Found - Resource doesn’t exist
  • 424: Failed Dependency - Used to wrap LinkedIn-specific error codes with an additional error_label
  • 500: 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.).
Always check the error_label and error_scope fields to programmatically handle different types of errors in your application.
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 an error_scope field that indicates what caused the error:
The retry_after field from tier provides guidance on how long to wait before making your first retry attempt. For subsequent retries, use an exponential backoff strategy by increasing the wait time between each attempt.

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. Example Implementation:
General Recommendations:
  • 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
To know more about rate limits, see our dedicated Rate Limits section and best practices.

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.).
Example Implementation: