[Schema Inaccuracy] `POST` `/app/installations/{installation_id}/access_tokens` sometimes returns `{}`

Open
#5,565 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Find the OpenAPI response schema for POST /app/installations/{installation_id}/access_tokens and compare it with the reported empty-object response. Reproduce the request if possible, then verify the schema representation of token and expires_at and run the repository's schema validation checks to confirm the documented response accepts valid results.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

Calling the above API sometimes returns an empty object, this is not correct according to the schema as this field is not nullable but it could be valid if token and expires_at are marked as nullable.

Reproduction Steps

Requires an app, then call the above API on it.

Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
3h 33m
Merged PRs (30d)
51

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.