# Access to Jira Dev Ops Components via Forge

**URL:** <https://community.developer.atlassian.com/t/access-to-jira-dev-ops-components-via-forge/86437>\
**Category:** Forge\
**Tags:** compass, jira-cloud, forge, atlassian-connect\
**Created:** [November 21, 2024, 3:19am UTC](https://community.developer.atlassian.com/t/access-to-jira-dev-ops-components-via-forge/86437 "2024-11-21T03:19:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ForgedApps](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/forgedapps/32/51439_2.png) [@ForgedApps](https://community.developer.atlassian.com/u/ForgedApps)\
**Post date:** [November 21, 2024, 3:19am UTC](https://community.developer.atlassian.com/t/access-to-jira-dev-ops-components-via-forge/86437/1 "2024-11-21T03:19:48Z")

</div>

The Jira Dev Ops Components are accessible via the REST API as documented [here](https://developer.atlassian.com/cloud/jira/software/rest/api-group-devops-components/#api-group-devops-components), but unfortunately “These APIs are available to Atlassian Connect apps.”

While trying to access the API using Forge with:

```auto
await api.asUser().requestJira(route`/rest/devopscomponents/1.0/{id}`)

```

It results in a `401 Unauthorized` error.

Additionally, the GraphQL Explorer can be used to access these components, but the same query fails when using `requestGraph` using Forge due to a 403 error.

This is problematic because every new Compass component creates a Dev Ops Component, and the Compass component can’t be deleted until the corresponding Dev Ops Component is deleted first.

Is there a programmatic way from Forge to access these components?