Skip to main content
All OutX API errors return a JSON object with an error field containing a human-readable message.

Error Codes

400, Bad Request

Missing or invalid parameters. Check the error message for specifics. Watchlist endpoints: Engagement endpoints: LinkedIn Data endpoints:

401, Unauthorized

API key is missing or invalid. Fix: Include your API key in the x-api-key header. Get your key at mentions.outx.ai/api-doc.

402, Plan Limit Reached

Your team has hit a plan-based limit. The error message includes your current limit. Fix: Upgrade your plan at outx.ai/pricing or wait for daily/weekly limits to reset.
Plan limits by tier:
  • Free: 2 watchlists, 1 auto-engagement rule per watchlist, 5 team members
  • Pro: 5 watchlists, 2 auto-engagement rules per watchlist, 10 team members
  • Expert: 20 watchlists, 5 auto-engagement rules per watchlist, 25 team members
  • Ultimate: 100 watchlists, 10 auto-engagement rules per watchlist, unlimited team members

403, Forbidden

Access denied. Most commonly caused by the Chrome extension not being active. Fix for plugin error: Install the OutX Chrome extension, sign into LinkedIn in the same browser, and keep the browser open. The extension must have been active within the last 48 hours. See Chrome Extension Guide.
The 403 plugin error is the most common API issue. If you’re getting this error, check that:
  1. The Chrome extension is installed on at least one team member’s browser
  2. That browser has been open within the last 48 hours
  3. The team member is signed into LinkedIn in the same browser

404, Not Found

The requested resource does not exist or belongs to a different team.

409, Conflict (Disabled Watchlist)

You sent a PUT /api-keyword-watchlist or PUT /api-reddit-watchlist (patch mode or prompt mode) against a paused watchlist. A disabled watchlist rejects updates so a paused list cannot be silently mutated or backfilled. Fix: Re-enable first, then retry the update:
Check whether a watchlist is disabled via the disabled field on the type’s GET endpoint (GET /api-keyword-watchlist?id=... or GET /api-reddit-watchlist?id=...).

405, Method Not Allowed

You used the wrong HTTP method. Check the endpoint documentation for the correct method (GET, POST, PUT, DELETE).

429, Rate Limit Exceeded

You have exceeded your plan’s API request quota. See Rate Limits for details and retry strategies.

500, Internal Server Error

An unexpected error occurred on our side. Retry with exponential backoff. If the error persists, contact support@outx.ai.

Error Response Format

Every error, on every endpoint, is a JSON object with a single error field:
There are no other error fields (no details, no code). Parse the HTTP status for the category and the error string for specifics.

Frequently Asked Questions

The most common cause is the Chrome extension requirement. At least one team member must have the OutX Chrome extension installed and actively used within the last 48 hours. Install the OutX Chrome Extension, sign into LinkedIn in the same browser, and keep the browser open.
OutX retrieves LinkedIn data through real browser sessions via the Chrome extension. This error means no team member has had the extension active recently. The extension runs in the background, just keep Chrome open with the extension installed and it will stay active.
402 errors mean you’ve reached a limit on your current plan. You can either upgrade your plan at outx.ai/pricing, wait for daily/weekly limits to reset, or delete existing resources (like watchlists) to make room for new ones.
Yes. Daily limits (likes, comments) reset at UTC midnight (00:00 UTC). Weekly limits (posts per watchlist) reset on Monday at 00:00 UTC.