LinkedIn posting errors and fixes
A LinkedIn failure is almost always reconnect_required (the login is revoked, expired or lost its admin access, so reconnect), platform_rejected (LinkedIn refused the content, including a duplicate post) or platform_unavailable (LinkedIn rate limited or was down, nothing posted).
#Errors you can get posting
yeetpost answers with its own code and message. It does not hand back LinkedIn's own text, so the second column is what yeetpost reads off LinkedIn's answer. Every body is JSON with an error code and a message; platform_rejected, platform_unavailable and internal_server_error also carry a req_id. Inside a post item the same vocabulary shows up as { "code": ..., "message": ... }.
| yeetpost code | HTTP | What yeetpost reads | What it means | Fix |
|---|---|---|---|---|
reconnect_required | 403 | A 401, or an error body whose code is REVOKED_ACCESS_TOKEN or EXPIRED_ACCESS_TOKEN, on the post or on an image step. The message is "LinkedIn no longer accepts this connection's login. Reconnect the account in the yeetpost dashboard." | The login is dead. A LinkedIn login lasts 60 days and renews itself from a refresh token that lasts 365 days; a refused renewal or a grant revoked on LinkedIn's side ends here. The connection shows reconnect_required, and expiring for the last 14 days before. | Reconnect the account at app.yeetpost.com/app/connections. For a customer's connection, send them through POST /profiles/{profileId}/connect with the connectionId. |
reconnect_required | 403 | A 403 with code ACCESS_DENIED when posting as a company page. The message is "You're no longer an admin of {page} on LinkedIn, or the login lost access. Reconnect it." | The person who connected the page is no longer an admin of it on LinkedIn, or the login lost access to it. The token can look fine and still not post as the page. | Make sure the person reconnecting is an admin of the page on LinkedIn, then reconnect the account. |
platform_rejected | 422 | An error body with a DUPLICATE_POST input error. The message is "LinkedIn: duplicate post was detected". | LinkedIn refused the post because it matches one already posted. | Change the text, then post again. |
platform_rejected | 422 | Any other 4xx on the post. The message is "LinkedIn rejected the post". On an image step it is "LinkedIn rejected the image". | LinkedIn refused the content. yeetpost does not read the reason beyond the cases above. | Change the text or the image and post again. Quote the req_id if the refusal looks wrong. |
platform_unavailable | 503 | A 429 or a 5xx on the post or an image step, or no answer at all on an image step. The message is "LinkedIn was busy or down, so nothing went out. Send it again." platform_status carries the status when there was one. | LinkedIn rate limited the account or was down. Nothing was posted. | Nothing was posted. Wait a bit, then send it again with a new Idempotency-Key. |
text_too_long | 400 | Nothing: yeetpost checks before it calls LinkedIn. | The text is over 3,000 characters, or the first comment is over 1,250. The field says which. Nothing is sent or scheduled. | Shorten the part the field names. |
internal_server_error | 500 | An answer yeetpost could not read, or the post request itself failing or timing out after it started. The message is "An unexpected error occurred" or "An unexpected error occurred while sending." with a req_id. | Whether the post went out is unknown. It may be live already. | Check the account on the platform before sending again. GET /posts/{postId} shows how yeetpost recorded it. Quote the req_id if you report it. |
reconnect_required | 403 | Nothing: yeetpost has no stored login for this connection. | The message is "LinkedIn's login is missing. Reconnect it to send again." | Reconnect the account at app.yeetpost.com/app/connections. For a customer's connection, send them through POST /profiles/{profileId}/connect with the connectionId. |
platform_unavailable | 503 | Nothing: yeetpost could not get ready to send. | The message is "LinkedIn was busy or down, so nothing went out. Send it again." Nothing was posted. | Nothing was posted. Wait a bit, then send it again with a new Idempotency-Key. |
internal_server_error | 500 | Nothing readable: something threw after the send to the platform had started. The message is "An unexpected error occurred while sending." with a req_id. | The post may already be live on LinkedIn. | Check the platform before sending again: a blind resend can post twice. GET /posts/{postId} shows how yeetpost recorded it. Quote the req_id if you report it. |
Codes that are not about one platform (invalid_request, invalid_connection, idempotency_key_conflict, the rate limit and the rest) are on Errors.
#Reconnecting
reconnect_required and, inside a post item, unauthorized both mean the stored login is dead. Nothing in the request will fix it. Reconnect the account at https://app.yeetpost.com/app/connections. For a customer's connection under a profile, send them through POST /profiles/{profileId}/connect and pass the connectionId. GET /connections shows each connection's status: active, expiring or reconnect_required. The connection.reconnect_required webhook fires the moment yeetpost learns the login is dead.
#More
Last verified 2026-10-29