Filemanager v3 api #390
Merged
Filemanager v3 api #390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description and Context
There was an update to the filemanager api where APIKEY access was revoked from uploads with the v2 endpoints. It was advised to update the upload enpoint to v3 (which does allow APIKEY) and to keep using v2 for requests that involve fetching files because the v3 API currently does not offer the same endpoints for managing files by path
This was reported in the Developer Slack https://hubspotdev.slack.com/archives/CLJJXGTC0/p1605198690210500