☁️ Libre Graph Cloud Collaboration API
  • Mustache 97.7%
  • HTML 2.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jannik Stehle 24ecd67331
Merge pull request #84 from opencloud-eu/feat/guest-link-logout
feat(guestLinks): add logout endpoint
2026-11-10 13:36:52 +01:00
.github Update settings.yml 2025-02-17 09:43:06 +01:00
.woodpecker ci: fix wp-git-action image tag 2026-07-11 11:58:11 +02:00
api/openapi-spec feat(guestLinks): add logout endpoint 2026-11-10 10:30:48 +01:00
docs/dist chore(deps): update swagger UI 2025-02-17 21:23:11 +01:00
templates CMake 4 dropped support for CMake < 3.5 2025-05-21 14:03:07 +02:00
.editorconfig fix: unify yaml indent style and add editorconfig 2024-04-16 14:54:39 +02:00
.gitignore feature: add listMyDrivesBeta and listAllDrivesBeta endpoints 2023-12-01 12:10:25 +01:00
.nojekyll Create .nojekyll 2022-12-13 19:13:45 +01:00
composer.json Add libre-graph-api-php 2023-08-30 12:44:46 +05:45
index.html feat: push to docs 2025-02-28 16:53:02 +01:00
index_staging.html feat: push to docs 2025-02-28 16:53:02 +01:00
LICENSE refactor!(debranding): Debrand libregraph API 2025-02-17 10:44:02 +01:00
README.md changing the docs link 2025-05-15 14:55:18 +02:00

Libre Graph Api

An API for open Cloud Collaboration. See the Libre Graph Home for more details.

This API is inspired by Microsoft Graph API.

Goal

The project goal is to provide an open source standard for open Cloud Collaboration.

Libre Graph is open source and open to any open source project that implements endpoints of the API.

Influence and differences from Microsoft Graph API

Libre Graph API draws significant inspiration from the Microsoft Graph API, particularly in its approach to providing a unified endpoint for accessing various services and data. We believe that the model provided by Microsoft Graph API is a robust and efficient way to facilitate integration and collaboration across different services.

However, Libre Graph API is not identical to Microsoft Graph API. We have made specific extensions and modifications to better suit our needs and goals:

  1. Extended Functionality: We have added specific endpoints and features unique to our implementation, designed to enhance collaboration and integration within the open source ecosystem.
  2. Custom Extensions: Certain functionalities have been extended to provide additional features that are not present in the Microsoft Graph API.
  3. Beta Features: Some endpoints are currently in beta, allowing us to continuously innovate and adapt to user needs before finalizing them.

Specification

The API specification uses the OpenAPI Specification (OAS) standard.

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.

An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.

Documentation

You can find a rendered version of the API documentation in our dev docs.

Clients

Client code can be generated from the API spec.

For example, to run the generator for the C++ bindings locally, run the following docker-based command:

docker run --rm -v "${PWD}:/local" openapitools/openapi-generator-cli generate --enable-post-process-file  -t local/templates/cpp-qt-client  -i local/api/openapi-spec/v1.0.yaml -g cpp-qt-client -o /local/out/cpp

That generates the output in out/cpp.

Available client libraries