Fivetran REST API
dbt Transformation Management API removal
Stopped workingSubscribe to Fivetran REST APIShare
On February 1, 2025, Fivetran removed the dbt Transformation resource from its REST API. Calls to the /v1/dbt/* endpoints now fail.
Calls it hits
/v1/dbt/*
What to use instead of these calls
Manage transformations with the Transformation Management API using /v1/transformation-projects and /v1/transformations instead of /v1/dbt/projects, /v1/dbt/models, and /v1/dbt/transformations.
In Fivetran REST API's words
We have removed the dbt Transformation resource in our REST API. Use the Transformation Management resource instead.
Facts
- API
- Fivetran REST API
api.fivetran.com - Kind
- Removal
- Announced
- January 1, 2025
- Takes effect
- February 1, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Fivetran REST API's own pages
Questions
When does this change take effect?
Calls to /v1/dbt/* on Fivetran REST API stopped working on February 1, 2025.
What happens to calls after February 1, 2025?
They have failed since February 1, 2025.
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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.