Leland Whitlock
07/02/2026, 1:05 PMkapa.ai
07/02/2026, 1:05 PMPOST /v1/jobs endpoint only accepts two jobType values: [API reference]
• sync
• reset
Passing jobType=REFRESH will result in an UnprocessableEntityProblem error with the message "Refreshes are not supported in the public API", even though the refresh documentation previously implied API support was available. [GitHub issue]
Current status • There is an open GitHub issue tracking this exact problem. [GitHub issue]
• A documentation PR (#79699) has been raised to clarify that POST /v1/jobs does not support refresh jobs. [docs PR]
• The internal machinery for refreshes already exists in the platform (it's what the UI uses), but the public API is simply not wired to it yet. [GitHub issue]
Your options right now 1. Use the UI — Refresh syncs (both "Refresh and Remove Records" and "Refresh and Retain Records") can be triggered from the Airbyte UI, which will keep your destination data available during the refresh. [refreshes docs]
2. Avoid reset if possible — As you noted, reset clears destination data before reloading, which introduces downtime risk. Until refresh is supported in the public API, the UI is the safest programmatic-free alternative.
3. Watch the GitHub issue — You can follow issue #75459 for updates on when public API support for REFRESH may be added. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.