generated: '2026-09-11'
method: searched
source: https://docs.publora.com/guides/rate-limits
note: >-
  Per-request API rate limiting (requests/minute) is planned but NOT currently
  enforced. Enforced limits are plan-based entitlements (monthly posts,
  scheduled-post queue, connection count, schedule horizon) plus one hard
  ingestion window on media URLs.
limit_count: 4
limits:
  - name: media-url-ingestion
    scope: per-account
    window: fixed 1 hour
    limit: 60
    unit: ingested URLs
    exhaustion_status: 429
    exhaustion_code: MEDIA_URL_RATE_LIMITED
    response_headers: [Retry-After]
  - name: monthly-posts
    scope: per-account (Starter) / per-connection (paid)
    limit: "15 (Starter) / unlimited fair-use ~5000 (Pro) / 100-500 (legacy)"
    exhaustion_status: 403
    exhaustion_code: POST_LIMIT_REACHED
    reset_field: periodEnd
  - name: scheduled-post-queue
    scope: workspace-wide
    limit: "3 (Starter) / unlimited (Pro) / 100-500 (legacy)"
    exhaustion_status: 403
    exhaustion_code: SCHEDULED_POST_LIMIT_REACHED
  - name: schedule-horizon
    scope: per-account
    limit: "7 days (Starter) / unlimited (paid)"
    exhaustion_status: 403
    exhaustion_code: SCHEDULE_HORIZON_REACHED
platform_side:
  note: >-
    Destination-platform posting limits are advisory and account-dependent;
    Publora does not treat them as an API contract. Platform-side rate-limit
    failures are reported on the post and are not auto-retried.
  linkedin_analytics: LINKEDIN_RATE_LIMITED (429) with retryAfter seconds
mcp:
  note: MCP session limits documented by the MCP endpoint.