# Feature NEX-452 - Make OpenProject API endpoints available for API consumers

Project: Stream Nextcloud app "OpenProject Integration"
Status: closed
URL: https://community.openproject.org/work_packages/NEX-452

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Nextcloud Integration 2.8.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Julien Veyssier |
| Accountable | JankariTech Dev |
| Product manager |  |
| Developers |  |
| Designer |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Labor costs |  |

## Description

**As a** Nextcloud (integrations) developer  
**I want to** use the integration app to interact with OpenProject outside of the web UI  
**so that** I can automate actions, such as creating work packages, via other interfaces or conversational agents.

**Acceptance Criteria**

  - The integration app provides OCS endpoints that allow authentication via any supported method (basic auth, app passwords, etc.).

  - OCS endpoints return responses in the standard OCS format (meta and data).

  - OpenProject-related actions (e.g., creating work packages) can be triggered programmatically via OCS without requiring a web session.

  - The updated frontend supports these changes without altering existing app behavior.

<br>

**Technical notes**

From [PR\#769](https://github.com/nextcloud/integration_openproject/pull/769)

> Here is a change suggestion to make it possible to use this integration app from somewhere else than the web UI.  
> All the endpoints that communicate with OP are grouped in an OCS controller.  
> OCS endpoints can be reached without having a web session but with any supported authentication method (basic auth, app password etc...).
> 
> OCS endpoints always return an `ocs` object which contains a `meta` key and a `data` one. More info at <https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-api-overview.html>
> 
> The frontend has been adjusted but not tested IRL. This does not affect how the app works.
> 
> This would allow us, in [the agency feature](https://docs.nextcloud.com/server/latest/admin_manual/ai/app_context_agent.html), to make OP-related tools. In short, NC users would be able to ask a conversational agent to create a work package in OP for example.