This document summarizes the Kopano GRAPI implementation differences and scope in relation to Microsoft Graph API. Thus the upstream documentation applies to GRAPI. For a list of endpoints implemented by GRAPI see the Resources section below.
- Endpoints such as "/me/messages" or "/me/events" do not expose the entire store, but just the inbox or calendar, respectively.
- Relative paths, such as "mailFolder/id/childFolder/id/childFolder/id/.." are not supported.
Genereally the Graph documentation applies considering the following changes:
- We do not support
$filter
or$format
. - Support for
$expand
and$count
is preliminary.
- We support handling attachments in binary using
$value
. For example:GET /me/messages/id/attachment/id/$value
- We support the query parameter
$search
for/users
.
We support the JSON batching API for combining multiple requests in one HTTP call.
This API supports groupware related endpoints. GRAPI follows a experimental/non-experimental
approach. Experimental endpoints are disabled by default (enable with --enable-experimental-endpoints
commandline switch).
(Extension: use attachment/id/$value
to get attachment in binary.)