/v2/enterprise/* → endpoint removal
Devin API
Deprecated, no date
Endpoints matching /v2/enterprise/* are deprecated without a shutdown date. Calls made to these endpoints will eventually fail. The provider notes that this API version is deprecated.
Calls it hits
/v2/enterprise/*
What to use instead of these calls
Call the v3 Enterprise API under /v3/enterprise/ instead, as mapped in the migration guide. Moving requires more than updating the endpoint, as API v3 authenticates with a service user and requires a new service-user key.
API v3 authenticates with a service user, so moving needs a new service-user key.
In Devin API's words
This API version is deprecated. Use API v3 with service user authentication.
Facts
- API
- Devin API
api.devin.ai - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Devin API's own pages
Questions
When does this change take effect?
Devin API deprecated /v2/enterprise/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Devin API has not given a shutdown date yet.
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 Devin API 2
-
No date
/v1/*Endpoint removal Deprecated, no date -
No date
POST /v1/sessionsEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.