search

Bedework / bedework

An Enterprise Calendar and Scheduling System
Apache License 2.0
40 stars 9 forks source link

Where is the REST API documentation for Bedework calendar server ? #120

Open signalarun opened 6 years ago

smythp commented 5 years ago

I'm also looking for this documentation.

douglm commented 5 years ago

There isn't a REST api for bedework. There's CalDAV and bedework supports pretty much all of the standard. There's also CalWS-SOAP The intent is to support some upcoming json based protocols but that's probably going to be a year or so - see https://tools.ietf.org/html/draft-ietf-jmap-calendars-00

smythp commented 5 years ago

I'm trying to procedurally extract info for events that I am admin on. Is this something that calDAV can support? Can you give a little direction as to the best way to approach this? I'm essentially looking for programmatic access to what admins get under the "View Registration" button. Everything else I can get by pulling in a feed.

This presentation that comes up for a lot of queries about Bedework says that a REST API is one of the features of Bedework 3.0, which might be causing some confusion.

http://dev.bedework.org/downloads/presentations/Bedework-Apereo2015.pdf

douglm commented 5 years ago

On 10/22/19 19:32, Patrick Smyth wrote:

I'm trying to procedurally extract info for events that I am admin on. Is this something that calDAV can support? Can you give a little direction as to the best way to approach this? I'm essentially looking for programmatic access to what admins get under the "View Registration" button. Everything else I can get by pulling in a feed.

You're using the event registration features? I'd have to look to remind myself but I think it's possible to get a full set of registrations as a csv download. We possibly allowed other formats. That wouldn't be via CalDAV. The interactions with the event registration app are all fairly simple so it might be possible to do that as a REST call - the biggest problem is likely to be the authentication - it's forms based.

It's usually not that hard to add a REST style interface and it would make sense to do that for reports.

This presentation that comes up for a lot of queries about Bedework says that a REST API is one of the features of Bedework 3.0, which might be causing some confusion.

http://dev.bedework.org/downloads/presentations/Bedework-Apereo2015.pdf

Yes - I guess that's CalWS-REST. This never got beyond a very basic definition and implementation adn had a weird mix of CalDAV search in it.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Bedework/bedework/issues/120?email_source=notifications&email_token=AAW2MBWQXA5OAXQ533HLBEDQP6ESRA5CNFSM4FHSY2W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7RKQA#issuecomment-545199424, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAW2MBTXSWUQ7PZEULV7OQLQP6ESRANCNFSM4FHSY2WQ.

smythp commented 5 years ago

Thanks for your responses! Do you think you could provide an example of an endpoint that I might use to get the CSV downloads? I can get the event ids, path, etc. from the feed, if that's part of it. Really don't want to have to scrape my own calendar with Selenium :(

smythp commented 4 years ago

Just wanted to check in on this, is a REST API implementation further along?

LSPaninka commented 1 year ago

I have the same question! There will be a REST API Implementation?

douglm commented 1 year ago

On 3/7/23 12:25, Lucas Paninka wrote:

I have the same question! There will be a REST API Implementation?

Not necessarily. The main focus is on supporting existing and developing protocols. So CalDAV - https://www.rfc-editor.org/rfc/rfc4791 - is fully supported and next in line is supporting jmap for calendars and contacts

— Reply to this email directly, view it on GitHub https://github.com/Bedework/bedework/issues/120#issuecomment-1458554202, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAW2MBURDW4XWKF5USEMZUTW25VR5ANCNFSM4FHSY2WQ. You are receiving this because you commented.Message ID: @.***>

smythp commented 1 year ago

I'm not using Bedework anymore, but I do think a simple REST API would be of great use. I had to reverse-engineer all the tokens and URI to scrape my own events, which was less than ideal.