shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs 24 Pull Requests

Same instrument, two spec sheets — measured, not claimed.

APIGitHub Project IssuesUNMONITORED—24 Pull RequestsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GitHub Project Issues vs 24 Pull Requests: common questions

Which is more reliable, GitHub Project Issues or 24 Pull Requests?

Only 24 Pull Requests is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do GitHub Project Issues and 24 Pull Requests need an API key?

Neither needs a paid key — GitHub Project Issues is callable with no signup, and 24 Pull Requests is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GitHub Project Issues and 24 Pull Requests from the browser?

Neither sends browser-friendly CORS headers reliably, so call GitHub Project Issues and 24 Pull Requests from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are GitHub Project Issues and 24 Pull Requests free for commercial use?

GitHub Project Issues has unclear commercial terms, and 24 Pull Requests has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.