Skip to main content

​
Publishing Errors

When a post fails to publish, Soku provides an HTTP status code and error message to help you identify the cause. This page covers the most common publishing errors and how to resolve them.

​
Error Code Reference

Status CodeErrorMeaningHow to Fix
400Bad RequestThe request is missing required fields or contains invalid data.Check that all required fields are filled in — caption, content type, at least one platform selected, and media attached (if applicable).
401UnauthorizedYour API key is invalid, expired, or missing.Verify your API key in Settings > API. If the key was revoked, generate a new one. See API Key Management.
403ForbiddenYour subscription is inactive or your trial has expired.Check your subscription status in Settings > Billing. Subscribe or renew to restore publishing access.
500Internal Server ErrorAn unexpected error occurred on Soku’s servers.Wait a moment and retry. If the error persists, contact support.

​
400 — Bad Request

A 400 error means the request was malformed or missing required information. Common causes:
  • No platforms selected. You must select at least one connected account to publish to.
  • Missing caption. Some platforms require a caption (text body) for the post.
  • Missing media. If you selected a video or image content type, you must attach the media file.
  • Invalid media format. The attached file may not be in a supported format for the selected platform.
  • No connected accounts. You selected a platform but do not have an account connected for it.
How to fix:
  1. Review the error message for specific details about what is missing.
  2. Go back to the post editor and ensure all required fields are filled.
  3. Verify that you have at least one connected account for each selected platform in Settings > Integrations.

​
401 — Unauthorized

A 401 error means Soku could not authenticate your request. Common causes:
  • Your API key is incorrect or has been revoked.
  • The Authorization header is missing or malformed.
  • Your platform token has expired and could not be refreshed.
How to fix:
  1. If you are using the API, check that your API key is correct and included as Authorization: Bearer sk_live_... in the request header.
  2. If publishing from the dashboard, check your platform connection status in Settings > Integrations. A red (Danger) status means you need to re-authorize the account.
  3. If your API key was revoked, generate a new one in Settings > API.

​
403 — Forbidden

A 403 error means your account does not have permission to perform the requested action. Common causes:
  • Your free trial has ended and you have not subscribed.
  • Your subscription has been canceled or paused due to a failed payment.
  • You are attempting an action not available on your current plan.
How to fix:
  1. Go to Settings > Billing and check your subscription status.
  2. If your trial has expired, subscribe to a plan to restore access.
  3. If your subscription was canceled due to a failed payment, update your payment method in the Stripe billing portal.

​
500 — Internal Server Error

A 500 error means something went wrong on Soku’s servers. How to fix:
  1. Wait and retry. Transient server errors often resolve themselves within a few minutes.
  2. Check the Soku status page for any ongoing incidents.
  3. Try again later. If the error persists after multiple retries over several minutes, contact support with the details of your request (timestamp, platforms, error message).
500 errors are not caused by anything on your end. If you encounter one, it is safe to retry the same request.

​
Viewing Post Error Details

To see the specific error for a failed post:
  1. Go to /posts in the main sidebar.
  2. Find the post with a Failed status.
  3. Click the post to expand its details.
  4. Each platform’s individual status and error message is shown.
A single post may succeed on some platforms and fail on others. The error details are shown per platform so you can identify exactly where the issue occurred.