You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a heads up, not all APIs are the same, and I'm not really expecting you to flesh out the ENTIRE Vimeo Api (although it would be cool if you got as far as you can). Feel free to delete any endpoints that don't exist on Vimeo. I'm actually surprised that the Vimeo and Flickr endpoints are so nearly identical, cuz I've never seen that before.
It looks like you're definitely doing everything correctly, just make sure you rename the files too. You can do this by doing git mv [path/to/old/file.php] [path/to/new/file.php] so that git doesn't just think you deleted the old file and created a new one. Not a big deal if it can't tell the difference though.
So the main thing is most of the common endpoints under the videos section are what I need. I need the endpoint for getting a list of your OWN (the currently logged in user if possible, otherwise passing a username as the condition) videos. It would also be good to get the endpoint for seeing if the current user is logged in.
In addition I need to be able to get detailed info about a video.
It looks like I will also need similar stuff for albums, channels, and categories.
Remember, when deciding what 'resource' or 'section' to place this under is up to you entirely. So when I'm querying information about a user, you can create a 'users' section. You can also add more sections or remove sections that aren't used (you can delete anything you don't end up using).
An example of some potentially confusing stuff is when you are querying a user's videos. Even though you're filtering by user, ultimately the resource you are getting is videos, so this request should go under the 'videos' section. This is probably the biggest different between the config array and most API documentation.
People tend to throw the person's videos underneath the 'person' section, but I do not.
OPTIONAL fields (like on this endpoint: vimeo.videos.comments.getList) can be placed into a sub-array with a key of 'optional'.
Dude what you did so far is FUCKING AWESOME.
Just a heads up, not all APIs are the same, and I'm not really expecting you to flesh out the ENTIRE Vimeo Api (although it would be cool if you got as far as you can). Feel free to delete any endpoints that don't exist on Vimeo. I'm actually surprised that the Vimeo and Flickr endpoints are so nearly identical, cuz I've never seen that before.
It looks like you're definitely doing everything correctly, just make sure you rename the files too. You can do this by doing
git mv [path/to/old/file.php] [path/to/new/file.php]
so that git doesn't just think you deleted the old file and created a new one. Not a big deal if it can't tell the difference though.So the main thing is most of the common endpoints under the
videos
section are what I need. I need the endpoint for getting a list of your OWN (the currently logged in user if possible, otherwise passing a username as the condition) videos. It would also be good to get the endpoint for seeing if the current user is logged in.In addition I need to be able to get detailed info about a video.
It looks like I will also need similar stuff for
albums
,channels
, andcategories
.Remember, when deciding what 'resource' or 'section' to place this under is up to you entirely. So when I'm querying information about a user, you can create a 'users' section. You can also add more sections or remove sections that aren't used (you can delete anything you don't end up using).
An example of some potentially confusing stuff is when you are querying a user's videos. Even though you're filtering by user, ultimately the resource you are getting is videos, so this request should go under the 'videos' section. This is probably the biggest different between the config array and most API documentation.
People tend to throw the person's videos underneath the 'person' section, but I do not.
OPTIONAL fields (like on this endpoint: vimeo.videos.comments.getList) can be placed into a sub-array with a key of 'optional'.
So it would look like:
The text was updated successfully, but these errors were encountered: