Found it. And found the answer to one of my other questions re: the name of the form field for uploading audio files. I hadn't realized all audio had to go through the IMPORT command, and that it would have to be done after creating a cart.
One bit of weirdness to report. Doing a "list cart" call, there are a few fields that don't seem to get returned. Namely: NOTES, BPM, START_DATETIME, and END_DATETIME. (Using the 3.0 beta in case that makes a difference). I can see why some of the internally used values like the PENDING values wouldn't be included. But the fields I named are available to be edited in the "Edit Cart" call. It seems weird to me that these values could be written but not read through the web API. And I know that at least one of these values is non-null because one thing I wanted to do once I had API calls in the program was fix a glitch in my data I'd created early in my programming: I'd set the "Notes" on most of my songs to "TWin32MemoStrings" when I queried classname instead of text. 😊 Was not passing that data along a deliberate decision or a glitch? -----Original Message----- > Is there any documentation for the Web API itself? Which CGI files to call, how to format my POST data, etc.? Or can someone at least point me in the right direction for how it works so I can try sussing it out myself? Full documentation is included with the Rivendell sources. If you?re building from source, you?ll find it in ?docs/apis/web_api.pdf?. On a standard CentOS install, it?s in ?/usr/share/doc/rivendell-<version>/apis/web_api.pdf?. There is also a full set of docs for the ?rivwebcapi? library; see ?docs/rivwebcapi/clibsummary.pdf? to get started. _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
