Cannot access Deploy Keys of a repository through Github API

[bzsca80]

Select Topic Area

Question

Body

We need API access to deploy keys on some of our repositories. We created a custom role on the organization that inherits the predefined Write role and adds the Manage Deploy Keys permission. Once I assigned my user to this role on the given repository I can access the deploy keys of the repository on the Web Interface but not through the API. For the API call I authenticate using a Personal Access Token (classic) as Bearer token according to the documentation. The same API call/token works on other repository of my organization where I'm in the pre-defined Admin role.
The request is

curl \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer {PERSONAL_ACCESS_TOKEN}" \
  https://api.github.com/repos/{OWNER}/{REPO}/keys

The response is 404 Not found which as I understand replaces 403 Forbidden at some places for security reasons:

{
  "message": "Not Found",
  "documentation_url": "https://docs.github.com/rest/reference/repos#list-deploy-keys"
}

CLI returns a very similar error:

HTTP 404: Not Found (https://api.github.com/repos/{OWNER}/{REPO}/keys?per_page=100)

Is it possible to access the deploy keys of a repository through github API without being admin on the repository? If yes, what else is
needed apart from the Manage Deploy Key permission?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬