Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Org Events REST API Hard Limit of 45

Open
#4,407 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github, openapi
Domain
api, documentation

Research direction

Start with the organization-events endpoint and compare its OpenAPI description with the documented behavior and the linked data-retention changelog. Verify the reported 45-event result independently, then determine whether the repository description is inaccurate. Done means the specification reflects the confirmed API behavior and the issue's expected 30-day coverage is resolved or clearly documented.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

Org Events API, is not giving all the events under 30 days. It only returns the latest 45 events when I invoke the API with a token with all the permissions.

Note: I have successfully implemented pagination logic to get all the pages, but the result is still 45.

I have gone through GitHub Docs, and it says they reduced the events window from 90 days to 30 days, this will take effect after Jan 2025. But I'm not even getting data for 30 days.

Expected

It should return data of 30 days, and not limit the returned response to 45.

Reproduction Steps

  • Be the Owner of an Organization
  • Make a Classic Token with all the permissions on the portal
  • Hit the API:
curl -L \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR-TOKEN>" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/users/USERNAME/events/orgs/ORG
  • Check the count of the results obtained, if it's 45 for you too.
Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
2h 23m
Merged PRs (30d)
57

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.