Best times to post
GET/best-times
When to post, for one or more accounts or for a platform. For an account with 30+ posts with stats in the last 90 days, times come from its own posts (each post compared with the account's typical post), filled out with platform-wide data. With fewer, they come from PostEverywhere users on that platform, in each poster's local time. Where neither has enough data (for example X, Telegram, Discord) the result is general guidance and says so. Several account_ids give one combined pick in combined. next_best is the soonest of the top three slots: use its next.iso as scheduled_for to post at the best time. Errors: missing_parameter, invalid_id, invalid_platform, invalid_timezone, not_found (account outside your organization or key scope).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
Best times
Validation error — see error.code and error.details
Missing/invalid/revoked/expired API key (codes invalid_api_key, api_key_revoked, api_key_expired, api_key_required, auth_failed). Auth-layer 401s omit error.retryable and meta.request_id.
API key missing the required scope (insufficient_scope), storage quota exceeded (storage_quota_exceeded), or account limit reached (account_limit_reached)
Resource not found in your organization/workspace (not_found)
Rate limit exceeded (rate_limit_exceeded, or plan budgets post_limit_reached / daily_limit_reached on schedulePost). All 429s carry Retry-After. The API-key limiter additionally sets the X-RateLimit-* headers and error.details {limit, remaining, reset_at}.
Response Headers
Seconds to wait before retrying
Requests allowed in the window (API-key limiter only)
Requests remaining (API-key limiter only)
Unix seconds when the window resets (API-key limiter only)
Internal error (internal_error and endpoint-specific 5xx codes). Retryable.