Get
Support
Need help with ShineiAPI? Find answers below or reach out to the community.
Frequently Asked Questions
Do I need an API key?
No. ShineiAPI is completely free and requires zero authentication. Just make a request and get JSON back. No sign-ups, no API keys, no OAuth.
What are the rate limits?
60 requests per minute per IP address. Rate limit info is included in every response via X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After headers.
I'm getting a 429 error — what do I do?
You've hit the rate limit. Wait for the window to reset (check the Retry-After header) or implement request throttling in your app. If you need higher limits, open an issue.
How often is the data updated?
Data comes from the Toraka API. ShineiAPI caches responses for 5–15 minutes depending on the endpoint. Series data refreshes every 5 minutes, search results every 10 minutes, and rankings every 15 minutes.
Can I use ShineiAPI in my commercial project?
Yes. The API is free to use. The source code is MIT licensed. However, you may not resell the API itself or charge users for direct access to ShineiAPI.
Why is a series missing or returning wrong data?
ShineiAPI pulls data from Toraka. If a series is missing or incorrect, it's likely an upstream issue. You can report it on GitHub and we'll investigate. Include the series slug in your report.
Does ShineiAPI support CORS?
Yes. All origins are allowed. You can call the API directly from any browser, mobile app, desktop app, or browser extension without a proxy.
How do I get the cover image for a series?
The cover field in series responses contains the full URL to the cover image. Use it directly in an <img> tag or fetch it server-side.
Troubleshooting
CORS Errors in Browser
ShineiAPI sets Access-Control-Allow-Origin: * on all responses. If you're still getting CORS errors, check that you're hitting https://shineiapi.vercel.app (not http).
404 — Series Not Found
The slug must match exactly. Try /api/v1/search?q=title first to find the correct slug, then use it in /api/v1/series/{slug}.
Slow Responses
First request to an uncached endpoint may be slower (upstream fetch). Subsequent requests within the TTL window are served from cache in milliseconds. If responses are consistently slow, check /api/v1/health for upstream status.
Empty or Malformed Responses
Always check the success field in the response envelope. If success: false, the error field contains details.
API Status
Check the health of the API and its upstream dependency:
Community & Contact
ShineiAPI is open source and community-driven. The best way to get help is through GitHub: