postboost 1.26.0 → 1.26.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (634) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +1 -1
  3. data/docs/AccountsApi.md +1 -1
  4. data/docs/BlogToSocialInput.md +1 -1
  5. data/lib/postboost/api/account_groups_api.rb +2 -2
  6. data/lib/postboost/api/accounts_api.rb +4 -4
  7. data/lib/postboost/api/activity_api.rb +2 -2
  8. data/lib/postboost/api/agents_api.rb +2 -2
  9. data/lib/postboost/api/ai_api.rb +2 -2
  10. data/lib/postboost/api/analytics_api.rb +2 -2
  11. data/lib/postboost/api/competitors_api.rb +2 -2
  12. data/lib/postboost/api/free_tools_api.rb +2 -2
  13. data/lib/postboost/api/hashtag_groups_api.rb +2 -2
  14. data/lib/postboost/api/inbox_api.rb +2 -2
  15. data/lib/postboost/api/media_api.rb +2 -2
  16. data/lib/postboost/api/mentions_api.rb +2 -2
  17. data/lib/postboost/api/posting_schedule_api.rb +2 -2
  18. data/lib/postboost/api/posts_api.rb +2 -2
  19. data/lib/postboost/api/receipts_api.rb +2 -2
  20. data/lib/postboost/api/subscriptions_api.rb +2 -2
  21. data/lib/postboost/api/tags_api.rb +2 -2
  22. data/lib/postboost/api/templates_api.rb +2 -2
  23. data/lib/postboost/api/users_api.rb +2 -2
  24. data/lib/postboost/api/webhooks_api.rb +2 -2
  25. data/lib/postboost/api/workspaces_api.rb +2 -2
  26. data/lib/postboost/api_client.rb +2 -2
  27. data/lib/postboost/api_error.rb +2 -2
  28. data/lib/postboost/configuration.rb +2 -2
  29. data/lib/postboost/models/account.rb +2 -2
  30. data/lib/postboost/models/account_analytics.rb +2 -2
  31. data/lib/postboost/models/account_analytics_initial_sync.rb +2 -2
  32. data/lib/postboost/models/account_connection_health.rb +2 -2
  33. data/lib/postboost/models/account_errors_inner.rb +2 -2
  34. data/lib/postboost/models/account_errors_inner_one_of.rb +2 -2
  35. data/lib/postboost/models/account_group.rb +2 -2
  36. data/lib/postboost/models/account_group_input.rb +2 -2
  37. data/lib/postboost/models/account_health.rb +2 -2
  38. data/lib/postboost/models/account_health_daily_cap.rb +2 -2
  39. data/lib/postboost/models/account_schedule.rb +2 -2
  40. data/lib/postboost/models/add_competitor202_response.rb +2 -2
  41. data/lib/postboost/models/add_competitor409_response.rb +2 -2
  42. data/lib/postboost/models/add_generic_subscription_request.rb +2 -2
  43. data/lib/postboost/models/add_post_to_queue_request.rb +2 -2
  44. data/lib/postboost/models/agent_page_meta.rb +2 -2
  45. data/lib/postboost/models/agent_proposal.rb +2 -2
  46. data/lib/postboost/models/agent_proposal_decision.rb +2 -2
  47. data/lib/postboost/models/agent_run.rb +2 -2
  48. data/lib/postboost/models/ai_credits.rb +2 -2
  49. data/lib/postboost/models/ai_usage.rb +2 -2
  50. data/lib/postboost/models/ai_usage_text.rb +2 -2
  51. data/lib/postboost/models/analytics_period.rb +2 -2
  52. data/lib/postboost/models/analytics_summary.rb +2 -2
  53. data/lib/postboost/models/analytics_summary_data.rb +2 -2
  54. data/lib/postboost/models/api_activity.rb +2 -2
  55. data/lib/postboost/models/api_activity_outcome.rb +2 -2
  56. data/lib/postboost/models/api_key.rb +2 -2
  57. data/lib/postboost/models/api_key_ability.rb +2 -2
  58. data/lib/postboost/models/api_key_input.rb +2 -2
  59. data/lib/postboost/models/approve_agent_proposal200_response.rb +2 -2
  60. data/lib/postboost/models/approve_agent_proposal409_response.rb +2 -2
  61. data/lib/postboost/models/approve_inbox_reply_draft403_response.rb +2 -2
  62. data/lib/postboost/models/approve_post_request.rb +2 -2
  63. data/lib/postboost/models/best_posting_times.rb +2 -2
  64. data/lib/postboost/models/best_posting_times_times_inner.rb +2 -2
  65. data/lib/postboost/models/blog_to_social200_response.rb +2 -2
  66. data/lib/postboost/models/blog_to_social429_response.rb +2 -2
  67. data/lib/postboost/models/blog_to_social_caption.rb +2 -2
  68. data/lib/postboost/models/blog_to_social_input.rb +2 -2
  69. data/lib/postboost/models/blog_to_social_media.rb +2 -2
  70. data/lib/postboost/models/blog_to_social_response.rb +2 -2
  71. data/lib/postboost/models/brand_voice.rb +2 -2
  72. data/lib/postboost/models/brand_voice_input.rb +2 -2
  73. data/lib/postboost/models/brand_voice_meta.rb +2 -2
  74. data/lib/postboost/models/cancel_subscription422_response.rb +2 -2
  75. data/lib/postboost/models/cancel_subscription422_response_errors.rb +2 -2
  76. data/lib/postboost/models/cancel_subscription_request.rb +2 -2
  77. data/lib/postboost/models/change_subscription_plan_request.rb +2 -2
  78. data/lib/postboost/models/channel_account.rb +2 -2
  79. data/lib/postboost/models/checkout_subscription200_response.rb +2 -2
  80. data/lib/postboost/models/checkout_subscription_request.rb +2 -2
  81. data/lib/postboost/models/coded_error.rb +2 -2
  82. data/lib/postboost/models/competitor.rb +2 -2
  83. data/lib/postboost/models/competitor_detail.rb +2 -2
  84. data/lib/postboost/models/competitor_input.rb +2 -2
  85. data/lib/postboost/models/competitor_media.rb +2 -2
  86. data/lib/postboost/models/competitor_snapshot.rb +2 -2
  87. data/lib/postboost/models/complete_chunked_upload_request.rb +2 -2
  88. data/lib/postboost/models/connect_channel_input.rb +2 -2
  89. data/lib/postboost/models/connect_link.rb +2 -2
  90. data/lib/postboost/models/create_account_group201_response.rb +2 -2
  91. data/lib/postboost/models/create_agent201_response.rb +2 -2
  92. data/lib/postboost/models/create_api_key201_response.rb +2 -2
  93. data/lib/postboost/models/create_api_key201_response_data.rb +2 -2
  94. data/lib/postboost/models/create_connect_link_request.rb +2 -2
  95. data/lib/postboost/models/create_hashtag_group201_response.rb +2 -2
  96. data/lib/postboost/models/create_inbox_reply_draft201_response.rb +2 -2
  97. data/lib/postboost/models/create_media_folder_request.rb +2 -2
  98. data/lib/postboost/models/create_mention201_response.rb +2 -2
  99. data/lib/postboost/models/create_post201_response.rb +2 -2
  100. data/lib/postboost/models/create_recycling_rule201_response.rb +2 -2
  101. data/lib/postboost/models/create_report_export201_response.rb +2 -2
  102. data/lib/postboost/models/create_reseller_client201_response.rb +2 -2
  103. data/lib/postboost/models/create_rss_feed201_response.rb +2 -2
  104. data/lib/postboost/models/create_template201_response.rb +2 -2
  105. data/lib/postboost/models/create_webhook_subscription201_response.rb +2 -2
  106. data/lib/postboost/models/create_webhook_subscription201_response_data.rb +2 -2
  107. data/lib/postboost/models/delete_agent200_response.rb +2 -2
  108. data/lib/postboost/models/delete_media_bulk_request.rb +2 -2
  109. data/lib/postboost/models/delete_media_bulk_request_items_inner.rb +2 -2
  110. data/lib/postboost/models/delete_media_folder_request.rb +2 -2
  111. data/lib/postboost/models/delete_mode.rb +2 -2
  112. data/lib/postboost/models/delete_post_request.rb +2 -2
  113. data/lib/postboost/models/delete_posts_bulk_request.rb +2 -2
  114. data/lib/postboost/models/delete_receipts_bulk_request.rb +2 -2
  115. data/lib/postboost/models/delete_result.rb +2 -2
  116. data/lib/postboost/models/delete_user400_response.rb +2 -2
  117. data/lib/postboost/models/delete_users_bulk_request.rb +2 -2
  118. data/lib/postboost/models/delete_workspaces_bulk_request.rb +2 -2
  119. data/lib/postboost/models/free_tool_build_utm_url_request.rb +2 -2
  120. data/lib/postboost/models/free_tool_build_utm_url_response.rb +2 -2
  121. data/lib/postboost/models/free_tool_calculate_engagement_rate_request.rb +2 -2
  122. data/lib/postboost/models/free_tool_calculate_engagement_rate_response.rb +2 -2
  123. data/lib/postboost/models/free_tool_clean_text_request.rb +2 -2
  124. data/lib/postboost/models/free_tool_clean_text_response.rb +2 -2
  125. data/lib/postboost/models/free_tool_clean_text_response_changes_inner.rb +2 -2
  126. data/lib/postboost/models/free_tool_clean_text_response_flags_inner.rb +2 -2
  127. data/lib/postboost/models/free_tool_count_characters_request.rb +2 -2
  128. data/lib/postboost/models/free_tool_count_characters_response.rb +2 -2
  129. data/lib/postboost/models/free_tool_count_characters_response_networks_inner.rb +2 -2
  130. data/lib/postboost/models/free_tool_error.rb +2 -2
  131. data/lib/postboost/models/free_tool_format_linked_in_post_request.rb +2 -2
  132. data/lib/postboost/models/free_tool_format_linked_in_post_response.rb +2 -2
  133. data/lib/postboost/models/free_tool_generate_fancy_text_request.rb +2 -2
  134. data/lib/postboost/models/free_tool_generate_fancy_text_response.rb +2 -2
  135. data/lib/postboost/models/free_tool_generate_fancy_text_response_styles_inner.rb +2 -2
  136. data/lib/postboost/models/free_tool_list.rb +2 -2
  137. data/lib/postboost/models/free_tool_list_item.rb +2 -2
  138. data/lib/postboost/models/free_tool_split_thread_request.rb +2 -2
  139. data/lib/postboost/models/free_tool_split_thread_response.rb +2 -2
  140. data/lib/postboost/models/free_tool_split_thread_response_posts_inner.rb +2 -2
  141. data/lib/postboost/models/get_account_health200_response.rb +2 -2
  142. data/lib/postboost/models/get_brand_voice200_response.rb +2 -2
  143. data/lib/postboost/models/get_competitor200_response.rb +2 -2
  144. data/lib/postboost/models/get_inbox_conversation200_response.rb +2 -2
  145. data/lib/postboost/models/get_posting_schedule200_response.rb +2 -2
  146. data/lib/postboost/models/get_remote_upload_status200_response.rb +2 -2
  147. data/lib/postboost/models/get_report_branding200_response.rb +2 -2
  148. data/lib/postboost/models/get_repurpose_run200_response.rb +2 -2
  149. data/lib/postboost/models/guardrail_error.rb +2 -2
  150. data/lib/postboost/models/hashtag_group.rb +2 -2
  151. data/lib/postboost/models/hashtag_group_input.rb +2 -2
  152. data/lib/postboost/models/image_alt_text200_response.rb +2 -2
  153. data/lib/postboost/models/image_alt_text_input.rb +2 -2
  154. data/lib/postboost/models/image_alt_text_response.rb +2 -2
  155. data/lib/postboost/models/image_credit_balance.rb +2 -2
  156. data/lib/postboost/models/image_edit_input.rb +2 -2
  157. data/lib/postboost/models/image_generate200_response.rb +2 -2
  158. data/lib/postboost/models/image_generate429_response.rb +2 -2
  159. data/lib/postboost/models/image_generate_input.rb +2 -2
  160. data/lib/postboost/models/image_generation_response.rb +2 -2
  161. data/lib/postboost/models/image_prompt200_response.rb +2 -2
  162. data/lib/postboost/models/image_prompt429_response.rb +2 -2
  163. data/lib/postboost/models/image_prompt_input.rb +2 -2
  164. data/lib/postboost/models/image_prompt_response.rb +2 -2
  165. data/lib/postboost/models/image_variations200_response.rb +2 -2
  166. data/lib/postboost/models/image_variations_input.rb +2 -2
  167. data/lib/postboost/models/image_variations_response.rb +2 -2
  168. data/lib/postboost/models/inbox_author.rb +2 -2
  169. data/lib/postboost/models/inbox_conversation.rb +2 -2
  170. data/lib/postboost/models/inbox_conversation_account.rb +2 -2
  171. data/lib/postboost/models/inbox_conversation_update.rb +2 -2
  172. data/lib/postboost/models/inbox_message.rb +2 -2
  173. data/lib/postboost/models/inbox_message_author.rb +2 -2
  174. data/lib/postboost/models/inbox_reply_draft.rb +2 -2
  175. data/lib/postboost/models/inbox_reply_draft_approve.rb +2 -2
  176. data/lib/postboost/models/inbox_reply_draft_edit.rb +2 -2
  177. data/lib/postboost/models/inbox_reply_draft_input.rb +2 -2
  178. data/lib/postboost/models/initiate_chunked_upload201_response.rb +2 -2
  179. data/lib/postboost/models/initiate_chunked_upload_request.rb +2 -2
  180. data/lib/postboost/models/initiate_remote_upload201_response.rb +2 -2
  181. data/lib/postboost/models/initiate_remote_upload201_response_one_of.rb +2 -2
  182. data/lib/postboost/models/initiate_remote_upload_request.rb +2 -2
  183. data/lib/postboost/models/learn_brand_voice_input.rb +2 -2
  184. data/lib/postboost/models/learn_brand_voice_response.rb +2 -2
  185. data/lib/postboost/models/learn_brand_voice_response_meta.rb +2 -2
  186. data/lib/postboost/models/list_account_groups200_response.rb +2 -2
  187. data/lib/postboost/models/list_accounts200_response.rb +2 -2
  188. data/lib/postboost/models/list_agent_proposals200_response.rb +2 -2
  189. data/lib/postboost/models/list_agent_runs200_response.rb +2 -2
  190. data/lib/postboost/models/list_agents200_response.rb +2 -2
  191. data/lib/postboost/models/list_api_activity200_response.rb +2 -2
  192. data/lib/postboost/models/list_api_keys200_response.rb +2 -2
  193. data/lib/postboost/models/list_competitors200_response.rb +2 -2
  194. data/lib/postboost/models/list_hashtag_groups200_response.rb +2 -2
  195. data/lib/postboost/models/list_inbox_conversations200_response.rb +2 -2
  196. data/lib/postboost/models/list_inbox_reply_drafts200_response.rb +2 -2
  197. data/lib/postboost/models/list_media200_response.rb +2 -2
  198. data/lib/postboost/models/list_media_folders200_response.rb +2 -2
  199. data/lib/postboost/models/list_mentions200_response.rb +2 -2
  200. data/lib/postboost/models/list_my_workspaces200_response.rb +2 -2
  201. data/lib/postboost/models/list_posts200_response.rb +2 -2
  202. data/lib/postboost/models/list_receipts200_response.rb +2 -2
  203. data/lib/postboost/models/list_recycling_rules200_response.rb +2 -2
  204. data/lib/postboost/models/list_recycling_runs200_response.rb +2 -2
  205. data/lib/postboost/models/list_report_exports200_response.rb +2 -2
  206. data/lib/postboost/models/list_reseller_clients200_response.rb +2 -2
  207. data/lib/postboost/models/list_rss_feeds200_response.rb +2 -2
  208. data/lib/postboost/models/list_tags200_response.rb +2 -2
  209. data/lib/postboost/models/list_templates200_response.rb +2 -2
  210. data/lib/postboost/models/list_users200_response.rb +2 -2
  211. data/lib/postboost/models/list_webhook_subscriptions200_response.rb +2 -2
  212. data/lib/postboost/models/list_workspaces200_response.rb +2 -2
  213. data/lib/postboost/models/media.rb +2 -2
  214. data/lib/postboost/models/media_base64_input.rb +2 -2
  215. data/lib/postboost/models/media_folder.rb +2 -2
  216. data/lib/postboost/models/media_folder_input.rb +2 -2
  217. data/lib/postboost/models/media_folder_ref.rb +2 -2
  218. data/lib/postboost/models/mention.rb +2 -2
  219. data/lib/postboost/models/mention_identity.rb +2 -2
  220. data/lib/postboost/models/mention_identity_input.rb +2 -2
  221. data/lib/postboost/models/mention_input.rb +2 -2
  222. data/lib/postboost/models/message_only.rb +2 -2
  223. data/lib/postboost/models/pagination_meta.rb +2 -2
  224. data/lib/postboost/models/pagination_meta_links.rb +2 -2
  225. data/lib/postboost/models/pagination_meta_meta.rb +2 -2
  226. data/lib/postboost/models/poll_rss_feed200_response.rb +2 -2
  227. data/lib/postboost/models/post.rb +2 -2
  228. data/lib/postboost/models/post_analytics.rb +2 -2
  229. data/lib/postboost/models/post_content.rb +2 -2
  230. data/lib/postboost/models/post_input.rb +2 -2
  231. data/lib/postboost/models/post_options_instagram.rb +2 -2
  232. data/lib/postboost/models/post_options_tik_tok.rb +2 -2
  233. data/lib/postboost/models/post_options_youtube.rb +2 -2
  234. data/lib/postboost/models/post_status.rb +2 -2
  235. data/lib/postboost/models/post_version.rb +2 -2
  236. data/lib/postboost/models/post_version_options.rb +2 -2
  237. data/lib/postboost/models/post_warning.rb +2 -2
  238. data/lib/postboost/models/post_warnings.rb +2 -2
  239. data/lib/postboost/models/posting_schedule.rb +2 -2
  240. data/lib/postboost/models/posting_schedule_day.rb +2 -2
  241. data/lib/postboost/models/posting_schedule_day_times_inner.rb +2 -2
  242. data/lib/postboost/models/posting_schedule_input.rb +2 -2
  243. data/lib/postboost/models/posting_time_slot.rb +2 -2
  244. data/lib/postboost/models/posting_times.rb +2 -2
  245. data/lib/postboost/models/posting_times_best_inner.rb +2 -2
  246. data/lib/postboost/models/posting_times_day_intervals_inner_inner.rb +2 -2
  247. data/lib/postboost/models/posting_times_days_inner.rb +2 -2
  248. data/lib/postboost/models/preflight_result.rb +2 -2
  249. data/lib/postboost/models/public_workspace.rb +2 -2
  250. data/lib/postboost/models/public_workspace_pivot.rb +2 -2
  251. data/lib/postboost/models/publish_progress.rb +2 -2
  252. data/lib/postboost/models/queue_slots.rb +2 -2
  253. data/lib/postboost/models/receipt.rb +2 -2
  254. data/lib/postboost/models/receipt_input.rb +2 -2
  255. data/lib/postboost/models/receipt_update_input.rb +2 -2
  256. data/lib/postboost/models/recommended_posting_times.rb +2 -2
  257. data/lib/postboost/models/reconnect_link.rb +2 -2
  258. data/lib/postboost/models/recycling_rule.rb +2 -2
  259. data/lib/postboost/models/recycling_rule_input.rb +2 -2
  260. data/lib/postboost/models/recycling_rule_settings.rb +2 -2
  261. data/lib/postboost/models/recycling_rule_update.rb +2 -2
  262. data/lib/postboost/models/recycling_run.rb +2 -2
  263. data/lib/postboost/models/remove_generic_subscription422_response.rb +2 -2
  264. data/lib/postboost/models/remove_user_from_workspace_request.rb +2 -2
  265. data/lib/postboost/models/report_branding.rb +2 -2
  266. data/lib/postboost/models/report_branding_input.rb +2 -2
  267. data/lib/postboost/models/report_export.rb +2 -2
  268. data/lib/postboost/models/report_export_input.rb +2 -2
  269. data/lib/postboost/models/repurpose_content200_response.rb +2 -2
  270. data/lib/postboost/models/repurpose_content202_response.rb +2 -2
  271. data/lib/postboost/models/repurpose_content500_response.rb +2 -2
  272. data/lib/postboost/models/repurpose_input.rb +2 -2
  273. data/lib/postboost/models/repurpose_input_theme.rb +2 -2
  274. data/lib/postboost/models/repurpose_result.rb +2 -2
  275. data/lib/postboost/models/repurpose_result_media.rb +2 -2
  276. data/lib/postboost/models/repurpose_result_source.rb +2 -2
  277. data/lib/postboost/models/repurpose_run.rb +2 -2
  278. data/lib/postboost/models/repurpose_run_accepted.rb +2 -2
  279. data/lib/postboost/models/repurpose_slide.rb +2 -2
  280. data/lib/postboost/models/reseller_client.rb +2 -2
  281. data/lib/postboost/models/reseller_client_input.rb +2 -2
  282. data/lib/postboost/models/reseller_client_usage.rb +2 -2
  283. data/lib/postboost/models/retry_post_account_result.rb +2 -2
  284. data/lib/postboost/models/rss_feed.rb +2 -2
  285. data/lib/postboost/models/rss_feed_input.rb +2 -2
  286. data/lib/postboost/models/rss_feed_update.rb +2 -2
  287. data/lib/postboost/models/run_agent202_response.rb +2 -2
  288. data/lib/postboost/models/schedule_post_request.rb +2 -2
  289. data/lib/postboost/models/schedule_result.rb +2 -2
  290. data/lib/postboost/models/subscription.rb +2 -2
  291. data/lib/postboost/models/subscription_input.rb +2 -2
  292. data/lib/postboost/models/subscription_status.rb +2 -2
  293. data/lib/postboost/models/subscription_update_input.rb +2 -2
  294. data/lib/postboost/models/tag.rb +2 -2
  295. data/lib/postboost/models/tag_input.rb +2 -2
  296. data/lib/postboost/models/template.rb +2 -2
  297. data/lib/postboost/models/template_content_item.rb +2 -2
  298. data/lib/postboost/models/template_input.rb +2 -2
  299. data/lib/postboost/models/template_input_content_inner.rb +2 -2
  300. data/lib/postboost/models/update_media_request.rb +2 -2
  301. data/lib/postboost/models/update_post200_response.rb +2 -2
  302. data/lib/postboost/models/upload_chunk201_response.rb +2 -2
  303. data/lib/postboost/models/user.rb +2 -2
  304. data/lib/postboost/models/user_input.rb +2 -2
  305. data/lib/postboost/models/user_update_input.rb +2 -2
  306. data/lib/postboost/models/webhook_event_name.rb +2 -2
  307. data/lib/postboost/models/webhook_event_payload.rb +2 -2
  308. data/lib/postboost/models/webhook_subscription.rb +2 -2
  309. data/lib/postboost/models/webhook_subscription_input.rb +2 -2
  310. data/lib/postboost/models/workspace.rb +2 -2
  311. data/lib/postboost/models/workspace_agent.rb +2 -2
  312. data/lib/postboost/models/workspace_agent_input.rb +2 -2
  313. data/lib/postboost/models/workspace_agent_settings.rb +2 -2
  314. data/lib/postboost/models/workspace_agent_update.rb +2 -2
  315. data/lib/postboost/models/workspace_input.rb +2 -2
  316. data/lib/postboost/models/workspace_user_input.rb +2 -2
  317. data/lib/postboost/models/x_usage.rb +2 -2
  318. data/lib/postboost/models/x_usage_counter.rb +2 -2
  319. data/lib/postboost/version.rb +3 -3
  320. data/lib/postboost.rb +2 -2
  321. data/postboost.gemspec +3 -3
  322. data/spec/api/account_groups_api_spec.rb +2 -2
  323. data/spec/api/accounts_api_spec.rb +3 -3
  324. data/spec/api/activity_api_spec.rb +2 -2
  325. data/spec/api/agents_api_spec.rb +2 -2
  326. data/spec/api/ai_api_spec.rb +2 -2
  327. data/spec/api/analytics_api_spec.rb +2 -2
  328. data/spec/api/competitors_api_spec.rb +2 -2
  329. data/spec/api/free_tools_api_spec.rb +2 -2
  330. data/spec/api/hashtag_groups_api_spec.rb +2 -2
  331. data/spec/api/inbox_api_spec.rb +2 -2
  332. data/spec/api/media_api_spec.rb +2 -2
  333. data/spec/api/mentions_api_spec.rb +2 -2
  334. data/spec/api/posting_schedule_api_spec.rb +2 -2
  335. data/spec/api/posts_api_spec.rb +2 -2
  336. data/spec/api/receipts_api_spec.rb +2 -2
  337. data/spec/api/subscriptions_api_spec.rb +2 -2
  338. data/spec/api/tags_api_spec.rb +2 -2
  339. data/spec/api/templates_api_spec.rb +2 -2
  340. data/spec/api/users_api_spec.rb +2 -2
  341. data/spec/api/webhooks_api_spec.rb +2 -2
  342. data/spec/api/workspaces_api_spec.rb +2 -2
  343. data/spec/models/account_analytics_initial_sync_spec.rb +2 -2
  344. data/spec/models/account_analytics_spec.rb +2 -2
  345. data/spec/models/account_connection_health_spec.rb +2 -2
  346. data/spec/models/account_errors_inner_one_of_spec.rb +2 -2
  347. data/spec/models/account_errors_inner_spec.rb +2 -2
  348. data/spec/models/account_group_input_spec.rb +2 -2
  349. data/spec/models/account_group_spec.rb +2 -2
  350. data/spec/models/account_health_daily_cap_spec.rb +2 -2
  351. data/spec/models/account_health_spec.rb +2 -2
  352. data/spec/models/account_schedule_spec.rb +2 -2
  353. data/spec/models/account_spec.rb +2 -2
  354. data/spec/models/add_competitor202_response_spec.rb +2 -2
  355. data/spec/models/add_competitor409_response_spec.rb +2 -2
  356. data/spec/models/add_generic_subscription_request_spec.rb +2 -2
  357. data/spec/models/add_post_to_queue_request_spec.rb +2 -2
  358. data/spec/models/agent_page_meta_spec.rb +2 -2
  359. data/spec/models/agent_proposal_decision_spec.rb +2 -2
  360. data/spec/models/agent_proposal_spec.rb +2 -2
  361. data/spec/models/agent_run_spec.rb +2 -2
  362. data/spec/models/ai_credits_spec.rb +2 -2
  363. data/spec/models/ai_usage_spec.rb +2 -2
  364. data/spec/models/ai_usage_text_spec.rb +2 -2
  365. data/spec/models/analytics_period_spec.rb +2 -2
  366. data/spec/models/analytics_summary_data_spec.rb +2 -2
  367. data/spec/models/analytics_summary_spec.rb +2 -2
  368. data/spec/models/api_activity_outcome_spec.rb +2 -2
  369. data/spec/models/api_activity_spec.rb +2 -2
  370. data/spec/models/api_key_ability_spec.rb +2 -2
  371. data/spec/models/api_key_input_spec.rb +2 -2
  372. data/spec/models/api_key_spec.rb +2 -2
  373. data/spec/models/approve_agent_proposal200_response_spec.rb +2 -2
  374. data/spec/models/approve_agent_proposal409_response_spec.rb +2 -2
  375. data/spec/models/approve_inbox_reply_draft403_response_spec.rb +2 -2
  376. data/spec/models/approve_post_request_spec.rb +2 -2
  377. data/spec/models/best_posting_times_spec.rb +2 -2
  378. data/spec/models/best_posting_times_times_inner_spec.rb +2 -2
  379. data/spec/models/blog_to_social200_response_spec.rb +2 -2
  380. data/spec/models/blog_to_social429_response_spec.rb +2 -2
  381. data/spec/models/blog_to_social_caption_spec.rb +2 -2
  382. data/spec/models/blog_to_social_input_spec.rb +2 -2
  383. data/spec/models/blog_to_social_media_spec.rb +2 -2
  384. data/spec/models/blog_to_social_response_spec.rb +2 -2
  385. data/spec/models/brand_voice_input_spec.rb +2 -2
  386. data/spec/models/brand_voice_meta_spec.rb +2 -2
  387. data/spec/models/brand_voice_spec.rb +2 -2
  388. data/spec/models/cancel_subscription422_response_errors_spec.rb +2 -2
  389. data/spec/models/cancel_subscription422_response_spec.rb +2 -2
  390. data/spec/models/cancel_subscription_request_spec.rb +2 -2
  391. data/spec/models/change_subscription_plan_request_spec.rb +2 -2
  392. data/spec/models/channel_account_spec.rb +2 -2
  393. data/spec/models/checkout_subscription200_response_spec.rb +2 -2
  394. data/spec/models/checkout_subscription_request_spec.rb +2 -2
  395. data/spec/models/coded_error_spec.rb +2 -2
  396. data/spec/models/competitor_detail_spec.rb +2 -2
  397. data/spec/models/competitor_input_spec.rb +2 -2
  398. data/spec/models/competitor_media_spec.rb +2 -2
  399. data/spec/models/competitor_snapshot_spec.rb +2 -2
  400. data/spec/models/competitor_spec.rb +2 -2
  401. data/spec/models/complete_chunked_upload_request_spec.rb +2 -2
  402. data/spec/models/connect_channel_input_spec.rb +2 -2
  403. data/spec/models/connect_link_spec.rb +2 -2
  404. data/spec/models/create_account_group201_response_spec.rb +2 -2
  405. data/spec/models/create_agent201_response_spec.rb +2 -2
  406. data/spec/models/create_api_key201_response_data_spec.rb +2 -2
  407. data/spec/models/create_api_key201_response_spec.rb +2 -2
  408. data/spec/models/create_connect_link_request_spec.rb +2 -2
  409. data/spec/models/create_hashtag_group201_response_spec.rb +2 -2
  410. data/spec/models/create_inbox_reply_draft201_response_spec.rb +2 -2
  411. data/spec/models/create_media_folder_request_spec.rb +2 -2
  412. data/spec/models/create_mention201_response_spec.rb +2 -2
  413. data/spec/models/create_post201_response_spec.rb +2 -2
  414. data/spec/models/create_recycling_rule201_response_spec.rb +2 -2
  415. data/spec/models/create_report_export201_response_spec.rb +2 -2
  416. data/spec/models/create_reseller_client201_response_spec.rb +2 -2
  417. data/spec/models/create_rss_feed201_response_spec.rb +2 -2
  418. data/spec/models/create_template201_response_spec.rb +2 -2
  419. data/spec/models/create_webhook_subscription201_response_data_spec.rb +2 -2
  420. data/spec/models/create_webhook_subscription201_response_spec.rb +2 -2
  421. data/spec/models/delete_agent200_response_spec.rb +2 -2
  422. data/spec/models/delete_media_bulk_request_items_inner_spec.rb +2 -2
  423. data/spec/models/delete_media_bulk_request_spec.rb +2 -2
  424. data/spec/models/delete_media_folder_request_spec.rb +2 -2
  425. data/spec/models/delete_mode_spec.rb +2 -2
  426. data/spec/models/delete_post_request_spec.rb +2 -2
  427. data/spec/models/delete_posts_bulk_request_spec.rb +2 -2
  428. data/spec/models/delete_receipts_bulk_request_spec.rb +2 -2
  429. data/spec/models/delete_result_spec.rb +2 -2
  430. data/spec/models/delete_user400_response_spec.rb +2 -2
  431. data/spec/models/delete_users_bulk_request_spec.rb +2 -2
  432. data/spec/models/delete_workspaces_bulk_request_spec.rb +2 -2
  433. data/spec/models/free_tool_build_utm_url_request_spec.rb +2 -2
  434. data/spec/models/free_tool_build_utm_url_response_spec.rb +2 -2
  435. data/spec/models/free_tool_calculate_engagement_rate_request_spec.rb +2 -2
  436. data/spec/models/free_tool_calculate_engagement_rate_response_spec.rb +2 -2
  437. data/spec/models/free_tool_clean_text_request_spec.rb +2 -2
  438. data/spec/models/free_tool_clean_text_response_changes_inner_spec.rb +2 -2
  439. data/spec/models/free_tool_clean_text_response_flags_inner_spec.rb +2 -2
  440. data/spec/models/free_tool_clean_text_response_spec.rb +2 -2
  441. data/spec/models/free_tool_count_characters_request_spec.rb +2 -2
  442. data/spec/models/free_tool_count_characters_response_networks_inner_spec.rb +2 -2
  443. data/spec/models/free_tool_count_characters_response_spec.rb +2 -2
  444. data/spec/models/free_tool_error_spec.rb +2 -2
  445. data/spec/models/free_tool_format_linked_in_post_request_spec.rb +2 -2
  446. data/spec/models/free_tool_format_linked_in_post_response_spec.rb +2 -2
  447. data/spec/models/free_tool_generate_fancy_text_request_spec.rb +2 -2
  448. data/spec/models/free_tool_generate_fancy_text_response_spec.rb +2 -2
  449. data/spec/models/free_tool_generate_fancy_text_response_styles_inner_spec.rb +2 -2
  450. data/spec/models/free_tool_list_item_spec.rb +2 -2
  451. data/spec/models/free_tool_list_spec.rb +2 -2
  452. data/spec/models/free_tool_split_thread_request_spec.rb +2 -2
  453. data/spec/models/free_tool_split_thread_response_posts_inner_spec.rb +2 -2
  454. data/spec/models/free_tool_split_thread_response_spec.rb +2 -2
  455. data/spec/models/get_account_health200_response_spec.rb +2 -2
  456. data/spec/models/get_brand_voice200_response_spec.rb +2 -2
  457. data/spec/models/get_competitor200_response_spec.rb +2 -2
  458. data/spec/models/get_inbox_conversation200_response_spec.rb +2 -2
  459. data/spec/models/get_posting_schedule200_response_spec.rb +2 -2
  460. data/spec/models/get_remote_upload_status200_response_spec.rb +2 -2
  461. data/spec/models/get_report_branding200_response_spec.rb +2 -2
  462. data/spec/models/get_repurpose_run200_response_spec.rb +2 -2
  463. data/spec/models/guardrail_error_spec.rb +2 -2
  464. data/spec/models/hashtag_group_input_spec.rb +2 -2
  465. data/spec/models/hashtag_group_spec.rb +2 -2
  466. data/spec/models/image_alt_text200_response_spec.rb +2 -2
  467. data/spec/models/image_alt_text_input_spec.rb +2 -2
  468. data/spec/models/image_alt_text_response_spec.rb +2 -2
  469. data/spec/models/image_credit_balance_spec.rb +2 -2
  470. data/spec/models/image_edit_input_spec.rb +2 -2
  471. data/spec/models/image_generate200_response_spec.rb +2 -2
  472. data/spec/models/image_generate429_response_spec.rb +2 -2
  473. data/spec/models/image_generate_input_spec.rb +2 -2
  474. data/spec/models/image_generation_response_spec.rb +2 -2
  475. data/spec/models/image_prompt200_response_spec.rb +2 -2
  476. data/spec/models/image_prompt429_response_spec.rb +2 -2
  477. data/spec/models/image_prompt_input_spec.rb +2 -2
  478. data/spec/models/image_prompt_response_spec.rb +2 -2
  479. data/spec/models/image_variations200_response_spec.rb +2 -2
  480. data/spec/models/image_variations_input_spec.rb +2 -2
  481. data/spec/models/image_variations_response_spec.rb +2 -2
  482. data/spec/models/inbox_author_spec.rb +2 -2
  483. data/spec/models/inbox_conversation_account_spec.rb +2 -2
  484. data/spec/models/inbox_conversation_spec.rb +2 -2
  485. data/spec/models/inbox_conversation_update_spec.rb +2 -2
  486. data/spec/models/inbox_message_author_spec.rb +2 -2
  487. data/spec/models/inbox_message_spec.rb +2 -2
  488. data/spec/models/inbox_reply_draft_approve_spec.rb +2 -2
  489. data/spec/models/inbox_reply_draft_edit_spec.rb +2 -2
  490. data/spec/models/inbox_reply_draft_input_spec.rb +2 -2
  491. data/spec/models/inbox_reply_draft_spec.rb +2 -2
  492. data/spec/models/initiate_chunked_upload201_response_spec.rb +2 -2
  493. data/spec/models/initiate_chunked_upload_request_spec.rb +2 -2
  494. data/spec/models/initiate_remote_upload201_response_one_of_spec.rb +2 -2
  495. data/spec/models/initiate_remote_upload201_response_spec.rb +2 -2
  496. data/spec/models/initiate_remote_upload_request_spec.rb +2 -2
  497. data/spec/models/learn_brand_voice_input_spec.rb +2 -2
  498. data/spec/models/learn_brand_voice_response_meta_spec.rb +2 -2
  499. data/spec/models/learn_brand_voice_response_spec.rb +2 -2
  500. data/spec/models/list_account_groups200_response_spec.rb +2 -2
  501. data/spec/models/list_accounts200_response_spec.rb +2 -2
  502. data/spec/models/list_agent_proposals200_response_spec.rb +2 -2
  503. data/spec/models/list_agent_runs200_response_spec.rb +2 -2
  504. data/spec/models/list_agents200_response_spec.rb +2 -2
  505. data/spec/models/list_api_activity200_response_spec.rb +2 -2
  506. data/spec/models/list_api_keys200_response_spec.rb +2 -2
  507. data/spec/models/list_competitors200_response_spec.rb +2 -2
  508. data/spec/models/list_hashtag_groups200_response_spec.rb +2 -2
  509. data/spec/models/list_inbox_conversations200_response_spec.rb +2 -2
  510. data/spec/models/list_inbox_reply_drafts200_response_spec.rb +2 -2
  511. data/spec/models/list_media200_response_spec.rb +2 -2
  512. data/spec/models/list_media_folders200_response_spec.rb +2 -2
  513. data/spec/models/list_mentions200_response_spec.rb +2 -2
  514. data/spec/models/list_my_workspaces200_response_spec.rb +2 -2
  515. data/spec/models/list_posts200_response_spec.rb +2 -2
  516. data/spec/models/list_receipts200_response_spec.rb +2 -2
  517. data/spec/models/list_recycling_rules200_response_spec.rb +2 -2
  518. data/spec/models/list_recycling_runs200_response_spec.rb +2 -2
  519. data/spec/models/list_report_exports200_response_spec.rb +2 -2
  520. data/spec/models/list_reseller_clients200_response_spec.rb +2 -2
  521. data/spec/models/list_rss_feeds200_response_spec.rb +2 -2
  522. data/spec/models/list_tags200_response_spec.rb +2 -2
  523. data/spec/models/list_templates200_response_spec.rb +2 -2
  524. data/spec/models/list_users200_response_spec.rb +2 -2
  525. data/spec/models/list_webhook_subscriptions200_response_spec.rb +2 -2
  526. data/spec/models/list_workspaces200_response_spec.rb +2 -2
  527. data/spec/models/media_base64_input_spec.rb +2 -2
  528. data/spec/models/media_folder_input_spec.rb +2 -2
  529. data/spec/models/media_folder_ref_spec.rb +2 -2
  530. data/spec/models/media_folder_spec.rb +2 -2
  531. data/spec/models/media_spec.rb +2 -2
  532. data/spec/models/mention_identity_input_spec.rb +2 -2
  533. data/spec/models/mention_identity_spec.rb +2 -2
  534. data/spec/models/mention_input_spec.rb +2 -2
  535. data/spec/models/mention_spec.rb +2 -2
  536. data/spec/models/message_only_spec.rb +2 -2
  537. data/spec/models/pagination_meta_links_spec.rb +2 -2
  538. data/spec/models/pagination_meta_meta_spec.rb +2 -2
  539. data/spec/models/pagination_meta_spec.rb +2 -2
  540. data/spec/models/poll_rss_feed200_response_spec.rb +2 -2
  541. data/spec/models/post_analytics_spec.rb +2 -2
  542. data/spec/models/post_content_spec.rb +2 -2
  543. data/spec/models/post_input_spec.rb +2 -2
  544. data/spec/models/post_options_instagram_spec.rb +2 -2
  545. data/spec/models/post_options_tik_tok_spec.rb +2 -2
  546. data/spec/models/post_options_youtube_spec.rb +2 -2
  547. data/spec/models/post_spec.rb +2 -2
  548. data/spec/models/post_status_spec.rb +2 -2
  549. data/spec/models/post_version_options_spec.rb +2 -2
  550. data/spec/models/post_version_spec.rb +2 -2
  551. data/spec/models/post_warning_spec.rb +2 -2
  552. data/spec/models/post_warnings_spec.rb +2 -2
  553. data/spec/models/posting_schedule_day_spec.rb +2 -2
  554. data/spec/models/posting_schedule_day_times_inner_spec.rb +2 -2
  555. data/spec/models/posting_schedule_input_spec.rb +2 -2
  556. data/spec/models/posting_schedule_spec.rb +2 -2
  557. data/spec/models/posting_time_slot_spec.rb +2 -2
  558. data/spec/models/posting_times_best_inner_spec.rb +2 -2
  559. data/spec/models/posting_times_day_intervals_inner_inner_spec.rb +2 -2
  560. data/spec/models/posting_times_days_inner_spec.rb +2 -2
  561. data/spec/models/posting_times_spec.rb +2 -2
  562. data/spec/models/preflight_result_spec.rb +2 -2
  563. data/spec/models/public_workspace_pivot_spec.rb +2 -2
  564. data/spec/models/public_workspace_spec.rb +2 -2
  565. data/spec/models/publish_progress_spec.rb +2 -2
  566. data/spec/models/queue_slots_spec.rb +2 -2
  567. data/spec/models/receipt_input_spec.rb +2 -2
  568. data/spec/models/receipt_spec.rb +2 -2
  569. data/spec/models/receipt_update_input_spec.rb +2 -2
  570. data/spec/models/recommended_posting_times_spec.rb +2 -2
  571. data/spec/models/reconnect_link_spec.rb +2 -2
  572. data/spec/models/recycling_rule_input_spec.rb +2 -2
  573. data/spec/models/recycling_rule_settings_spec.rb +2 -2
  574. data/spec/models/recycling_rule_spec.rb +2 -2
  575. data/spec/models/recycling_rule_update_spec.rb +2 -2
  576. data/spec/models/recycling_run_spec.rb +2 -2
  577. data/spec/models/remove_generic_subscription422_response_spec.rb +2 -2
  578. data/spec/models/remove_user_from_workspace_request_spec.rb +2 -2
  579. data/spec/models/report_branding_input_spec.rb +2 -2
  580. data/spec/models/report_branding_spec.rb +2 -2
  581. data/spec/models/report_export_input_spec.rb +2 -2
  582. data/spec/models/report_export_spec.rb +2 -2
  583. data/spec/models/repurpose_content200_response_spec.rb +2 -2
  584. data/spec/models/repurpose_content202_response_spec.rb +2 -2
  585. data/spec/models/repurpose_content500_response_spec.rb +2 -2
  586. data/spec/models/repurpose_input_spec.rb +2 -2
  587. data/spec/models/repurpose_input_theme_spec.rb +2 -2
  588. data/spec/models/repurpose_result_media_spec.rb +2 -2
  589. data/spec/models/repurpose_result_source_spec.rb +2 -2
  590. data/spec/models/repurpose_result_spec.rb +2 -2
  591. data/spec/models/repurpose_run_accepted_spec.rb +2 -2
  592. data/spec/models/repurpose_run_spec.rb +2 -2
  593. data/spec/models/repurpose_slide_spec.rb +2 -2
  594. data/spec/models/reseller_client_input_spec.rb +2 -2
  595. data/spec/models/reseller_client_spec.rb +2 -2
  596. data/spec/models/reseller_client_usage_spec.rb +2 -2
  597. data/spec/models/retry_post_account_result_spec.rb +2 -2
  598. data/spec/models/rss_feed_input_spec.rb +2 -2
  599. data/spec/models/rss_feed_spec.rb +2 -2
  600. data/spec/models/rss_feed_update_spec.rb +2 -2
  601. data/spec/models/run_agent202_response_spec.rb +2 -2
  602. data/spec/models/schedule_post_request_spec.rb +2 -2
  603. data/spec/models/schedule_result_spec.rb +2 -2
  604. data/spec/models/subscription_input_spec.rb +2 -2
  605. data/spec/models/subscription_spec.rb +2 -2
  606. data/spec/models/subscription_status_spec.rb +2 -2
  607. data/spec/models/subscription_update_input_spec.rb +2 -2
  608. data/spec/models/tag_input_spec.rb +2 -2
  609. data/spec/models/tag_spec.rb +2 -2
  610. data/spec/models/template_content_item_spec.rb +2 -2
  611. data/spec/models/template_input_content_inner_spec.rb +2 -2
  612. data/spec/models/template_input_spec.rb +2 -2
  613. data/spec/models/template_spec.rb +2 -2
  614. data/spec/models/update_media_request_spec.rb +2 -2
  615. data/spec/models/update_post200_response_spec.rb +2 -2
  616. data/spec/models/upload_chunk201_response_spec.rb +2 -2
  617. data/spec/models/user_input_spec.rb +2 -2
  618. data/spec/models/user_spec.rb +2 -2
  619. data/spec/models/user_update_input_spec.rb +2 -2
  620. data/spec/models/webhook_event_name_spec.rb +2 -2
  621. data/spec/models/webhook_event_payload_spec.rb +2 -2
  622. data/spec/models/webhook_subscription_input_spec.rb +2 -2
  623. data/spec/models/webhook_subscription_spec.rb +2 -2
  624. data/spec/models/workspace_agent_input_spec.rb +2 -2
  625. data/spec/models/workspace_agent_settings_spec.rb +2 -2
  626. data/spec/models/workspace_agent_spec.rb +2 -2
  627. data/spec/models/workspace_agent_update_spec.rb +2 -2
  628. data/spec/models/workspace_input_spec.rb +2 -2
  629. data/spec/models/workspace_spec.rb +2 -2
  630. data/spec/models/workspace_user_input_spec.rb +2 -2
  631. data/spec/models/x_usage_counter_spec.rb +2 -2
  632. data/spec/models/x_usage_spec.rb +2 -2
  633. data/spec/spec_helper.rb +2 -2
  634. metadata +8 -8
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
data/spec/spec_helper.rb CHANGED
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #PostBoost API
3
3
 
4
- #The PostBoost REST API lets you publish, schedule, and analyze social media posts across 12+ platforms from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
4
+ #The PostBoost REST API lets you publish, schedule, and analyze social media posts on every supported network from a single integration. No OAuth apps to maintain — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when the workspace's plan does not include API access (capability `api`). ## Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in the request's `timezone` when one is given, otherwise in the workspace timezone. ## Idempotent requests Send an `Idempotency-Key` header (any unique string, for example a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing a key with a different body returns `422`; a request still in progress with the same key returns `409`. `5xx` and `429` responses are not stored, so they can be retried with the same key. ## Guardrails for automated clients Create and update requests are checked before anything is written: a post whose content matches one created for the same account in the last 24 hours returns `409` (`code: duplicate_post`, override with `allow_duplicate: true`), scheduling past an account's daily cap returns `429` (`code: account_daily_cap_reached`), and scheduling to an account that must be reconnected returns `422` (`code: account_unauthorized` or `account_token_missing`). Use `POST /{workspaceUuid}/posts/validate` for a dry run and `GET /{workspaceUuid}/activity` to review what API clients did. ## Authentication All requests require a Bearer token in the `Authorization` header. Generate tokens in your PostBoost dashboard under **Settings → Access Tokens**. ``` Authorization: Bearer YOUR_API_TOKEN ```
5
5
 
6
- The version of the OpenAPI document: 1.26.0
6
+ The version of the OpenAPI document: 1.26.1
7
7
  Contact: hi@postboost.co
8
8
  Generated by: https://openapi-generator.tech
9
9
  Generator version: 7.9.0
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: postboost
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.26.0
4
+ version: 1.26.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - OpenAPI-Generator
@@ -50,13 +50,13 @@ dependencies:
50
50
  - !ruby/object:Gem::Version
51
51
  version: 3.6.0
52
52
  description: 'The PostBoost REST API lets you publish, schedule, and analyze social
53
- media posts across 12+ platforms from a single integration. No OAuth apps to maintain
54
- — PostBoost handles platform authorization for you. ## Base URL All workspace-scoped
55
- endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints are prefixed
56
- with `/panel`. ## Plan access Every workspace-scoped endpoint returns `403` when
57
- the workspace''s plan does not include API access (capability `api`). ## Dates
58
- and times Post dates and times (`date`, `time`, `accounts_schedule`) are read in
59
- the request''s `timezone` when one is given, otherwise in the workspace timezone. ##
53
+ media posts on every supported network from a single integration. No OAuth apps
54
+ to maintain — PostBoost handles platform authorization for you. ## Base URL All
55
+ workspace-scoped endpoints are prefixed with `/{workspaceUuid}`. Panel/admin endpoints
56
+ are prefixed with `/panel`. ## Plan access Every workspace-scoped endpoint returns
57
+ `403` when the workspace''s plan does not include API access (capability `api`). ##
58
+ Dates and times Post dates and times (`date`, `time`, `accounts_schedule`) are read
59
+ in the request''s `timezone` when one is given, otherwise in the workspace timezone. ##
60
60
  Idempotent requests Send an `Idempotency-Key` header (any unique string, for example
61
61
  a UUID) with a `POST`. Repeating the request with the same key within 24 hours returns
62
62
  the stored response with `Idempotent-Replayed: true` and creates nothing new. Reusing