Fireworks AI
POST /v1/accounts/{id}/reinforcementFineTuningJobs endpoint removal
Stopped workingSubscribe to Fireworks AIShare
On October 1, 2026, Fireworks AI shut down the POST /v1/accounts/{id}/reinforcementFineTuningJobs endpoint. Following this change, calls to this endpoint fail. Fireworks AI stated that Managed Training "no longer accepts new RFT jobs" through the API.
Calls it hits
POST /v1/accounts/{id}/reinforcementFineTuningJobs
What to use instead of these calls
Run RL on the Training API instead.
In Fireworks AI's words
Managed Training no longer accepts new RFT jobs from the Fireworks UI, firectl, or the REST API.
Facts
- API
- Fireworks AI
api.fireworks.ai - Kind
- Endpoint removal
- Announced
- October 1, 2026
- Takes effect
- October 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Fireworks AI's own pages
Questions
When does this change take effect?
Calls to POST /v1/accounts/{id}/reinforcementFineTuningJobs on Fireworks AI stopped working on October 1, 2026.
What happens to calls after October 1, 2026?
They have failed since October 1, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Fireworks AI 4
-
No date
accounts/fireworks/models/gpt-oss-120bModel retirement Deprecated, no date -
No date
accounts/fireworks/models/inklingModel retirement Deprecated, no date -
No date
accounts/fireworks/models/nemotron-3-ultra-nvfp4Model retirement Deprecated, no date -
No date
accounts/fireworks/models/nemotron-lightning-3p5-30b-a3bModel retirement Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.