extern/egroupware_official
1
0
Fork 0
mirror of https://github.com/EGroupware/egroupware.git synced 2024-12-24 23:59:39 +01:00
Code Issues Packages Projects Releases Wiki Activity
790db0f619
egroupware_official/doc/REST-CalDAV-CardDAV
History
ralf 18f45b3379 adding HttpException with readonly properties method, request_uri, request_body, response_headers and response for http errors 
incl. exception handler dumpting the HTTP request and response
2024-07-11 13:57:25 +02:00
..
Addressbook.md add missing @type: Card(Group) in Addressbook REST API 2024-05-15 19:52:37 +02:00
api-client.php adding HttpException with readonly properties method, request_uri, request_body, response_headers and response for http errors 2024-07-11 13:57:25 +02:00
Calendar.md replaced draft with now existing rfc URLs and unified the markup of all REST API documents 2024-05-15 08:35:25 +02:00
Infolog.md Add and document filters for InfoLog REST API 2024-05-15 19:21:22 +02:00
Links-and-attachments.md replaced draft with now existing rfc URLs and unified the markup of all REST API documents 2024-05-15 08:35:25 +02:00
Mail.md replaced draft with now existing rfc URLs and unified the markup of all REST API documents 2024-05-15 08:35:25 +02:00
README.md replaced draft with now existing rfc URLs and unified the markup of all REST API documents 2024-05-15 08:35:25 +02:00
Timesheet.md replaced draft with now existing rfc URLs and unified the markup of all REST API documents 2024-05-15 08:35:25 +02:00

README.md

EGroupware CalDAV/CardDAV server and REST API

CalDAV/CardDAV is build on HTTP and WebDAV, implementing the following additional RFCs containing documentation of the protocol:

Path / URL layout for CalDAV/CardDAV and REST is identical

One can use the following URLs relative (!) to https://example.org/egroupware/groupdav.php

  • / base of Cal|Card|GroupDAV tree, only certain clients (KDE, Apple) can autodetect folders from here
  • /principals/ principal-collection-set for WebDAV ACL
  • /principals/users/<username>/
  • /principals/groups/<groupname>/
  • /<username>/ users home-set with
  • /<username>/addressbook/ addressbook of user or group given the user has rights to view it
  • /<current-username>/addressbook-<other-username>/ shared addressbooks from other user or group
  • /<current-username>/addressbook-accounts/ all accounts current user has rights to see
  • /<username>/calendar/ calendar of user given the user has rights to view it
  • /<username>/calendar/?download download whole calendar as .ics file (GET request!)
  • /<current-username>/calendar-<other-username>/ shared calendar from other user or group (only current !)
  • /<username>/inbox/ scheduling inbox of user
  • /<username>/outbox/ scheduling outbox of user
  • /<username>/infolog/ InfoLog's of user given the user has rights to view it
  • /addressbook/ all addressbooks current user has rights to, announced as directory-gateway now
  • /addressbook-accounts/ all accounts current user has rights to see
  • /calendar/ calendar of current user
  • /infolog/ infologs of current user
  • /(resources|locations)/<resource-name>/calendar calendar of a resource/location, if user has rights to view
  • /<current-username>/(resource|location)-<resource-name> shared calendar from a resource/location
  • /mail/ REST API only
  • /timesheet/ REST API only
  • /smallpart/ REST API only

Shared addressbooks or calendars are only shown in the users home-set, if he subscribed to it via his CalDAV preferences!

Calling one of the above collections with a GET request / regular browser generates an automatic index from the data of an allprop PROPFIND, allow browsing CalDAV/CardDAV tree with a regular browser.

REST API: using EGroupware CalDAV/CardDAV server with JSON

  • Addressbook
  • Calendar
    • currently recurring events are readonly, they are returned but can not be created or modified
  • InfoLog
  • Mail
    • currently only sending mails,
    • opening interactive compose windows,
    • view and reply to eml files and
    • vacation handling
  • Timesheet
  • ViDoTeach
  • Links and attachments
    • linking application entries to other application entries
    • attaching files to application entries
    • listing, creating and deleting links and attachments

For the REST API you always have to send an "Accept: application/json" header and for POST & PUT requests additionally a "Content-Type: application/json" header, otherwise you talk to the CalDAV/CardDAV server and don't get the response you expect!

Following RFCs / drafts used/planned for JSON encoding of resources

ToDos