📖 API Curation Registry
Explore comprehensive technical maps for the Runflix edge ecosystem. Gateway root: https://api.runflix.name.ng
Overview
The Runflix API accepts edge-proxied secure HTTPS requests. All methods return structured, compressed JSON response packages designed for high-concurrency client-side workflows.
All standard responses strictly contain a
status (integer HTTP code), a success (boolean status), a creator ("Daratech"), and a result block hosting requested datasets.Authentication & Keys
Whitelisted endpoints verify clients via authentication keys. Pass your credentials inside the query string or within the secure HTTP header block:
1. Query string parameter verification
https://api.runflix.name.ng/category/endpoint?q=query&apikey=YOUR_KEY
2. Secure HTTP header token verification
curl https://api.runflix.name.ng/ai/overchat?q=hello \ -H "X-API-Key: YOUR_KEY"
Head to the access requisition panel to provision a key. You can dynamically query key details and metrics at `/apikey-status` using the Checker panel below.
Error Resolution Matrix
ERRORS
HTTP Response Codes
Matrix of standardized gateway status codes and resolutions.
Status Codes
200 OK
SUCCESS
Request succeeded. Payload contains requested data.
400 Bad Request
CLIENT ERROR
Missing required query parameters (e.g.
q or url).
401 Unauthorized
AUTH ERROR
API key parameter (
apikey) missing, invalid, or suspended.
403 Forbidden
PERM ERROR
API key does not have permission to access this category or endpoint.
429 Rate Limit
QUOTA EXCEEDED
Daily request count exceeded your plan limit. Resets at midnight UTC.
503 Unavailable
MAINTENANCE
The endpoint is currently offline for development or scheduled maintenance.
Category Registry Groups
Select a category group below to browse and run integration tests for its whitelisted endpoints.