Socket API
PUT /v0/report/upload endpoint removal
Deprecated, no dateSubscribe to Socket APIShare
Socket API has deprecated the PUT /v0/report/upload endpoint without a shutdown date. Calls made to this route are slated for removal and will fail. Developers relying on this endpoint will need to transition their integrations to avoid disruptions.
Calls it hits
PUT /v0/report/upload
What to use instead of these calls
Create a full scan with POST /v0/orgs/{org_slug}/full-scans instead.
In Socket API's words
This endpoint is deprecated. Use the successor version instead. Deprecated: Use /orgs/{org_slug}/full-scans instead.
Facts
- API
- Socket API
api.socket.dev - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Socket API's own pages
Questions
When does this change take effect?
Socket API deprecated PUT /v0/report/upload without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Socket 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 Socket API 5
-
GET /v0/report/view/{id}Endpoint removal Stops workingin 14 days -
No date
DELETE /v0/report/delete/{id}Endpoint removal Deprecated, no date -
No date
GET /v0/repo/listEndpoint removal Deprecated, no date -
No date
GET /v0/report/listEndpoint removal Deprecated, no date -
No date
POST /v0/purlEndpoint 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.