← Live dashboard

LinkedIn AccessToken and Authorization API Returning 429 Error

ResolvedminorOfficial source confirmedFirst recorded update Jan 13, 2025, 04:22 PM · Resolved Jan 13, 2025, 08:01 PM

We’re pleased to report that the issue affecting the platform, where some API requests to /v2/accessToken and /v2/authorization were returning a 429 error code, has now been resolved. Our team has implemented a fix, and all systems are back to normal operation. We sincerely appreciate your patience while we worked to resolve this matter. If you continue to encounter any issues, please contact our support team for assistance.

LinkedIn live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with LinkedIn now? Check the current status

Updates (4)

  1. Jan 13, 2025, 08:01 PM
    LinkedIn AccessToken and Authorization API Returning 429 Error

    We’re pleased to report that the issue affecting the platform, where some API requests to /v2/accessToken and /v2/authorization were returning a 429 error code, has now been resolved. Our team has implemented a fix, and all systems are back to normal operation. We sincerely appreciate your patience while we worked to resolve this matter. If you continue to encounter any issues, please contact our support team for assistance.

    LinkedIn ↗
  2. Jan 13, 2025, 06:42 PM
    LinkedIn AccessToken and Authorization API Returning 429 Error

    We are continuing to work on a fix for this issue.

    LinkedIn ↗
  3. Jan 13, 2025, 06:37 PM
    LinkedIn AccessToken and Authorization API Returning 429 Error

    The issue has been identified and a fix is being implemented.

    LinkedIn ↗
  4. Jan 13, 2025, 04:22 PM
    LinkedIn AccessToken and Authorization API Returning 429 Error

    We are currently experiencing an issue across the platform that may cause some API requests to /v2/accessToken and /v2/authorization are returning a 429 error code. We are investigating the issue and working on a resolution.

    LinkedIn ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow LinkedIn's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.