Created
August 5, 2013 14:27
-
-
Save thepeopleseason/6156326 to your computer and use it in GitHub Desktop.
Brightcove API documentation is wrong
This file contains hidden or 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
===> Please place your reply above this line <=== | |
Hi James, | |
The documentation may actually be incorrect here. I will have our Doc Writers review. No changes have been made to the API in years so I think the documentation has been incorrect all along. | |
I won't be needing the tcpdump or Wireshark logs and Shaun provided the API Call along with the JSON results so I think I have everything I need. We're still investigating why a video in PENDING status was in the API Call results. | |
I'll be in touch when I have some additional information. | |
Many Thanks, | |
Kevin | |
--------------------------------------------------------------- | |
2013-08-02 11:40:17 AM EDT | |
--------------------------------------------------------------- | |
From: Hsiao, James (CMG-Atlanta) <[email protected]> | |
Kevin: | |
According to your API Documentation: | |
The from_date property is the change date of the oldest video you want returned. It is expressed as the number of minutes since the UNIX epoch (January 1st, 1970 00:00:00 GMT). Here's a utility that converts human-readable dates to UNIX dates in seconds. (There are many others on the web, including epochconverter.com.) You'll need to divide the result by 60 to get the number of minutes. | |
So that value isn't actual unix epoch time, but epoch time / 60. | |
Has your API backend changed to require epoch time instead of minutes? | |
-- | |
JAMES HSIAO | Team Lead Developer | CMGdigital | |
[email protected] | p: 678.645.4046 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment