Estimate reading time​
Estimate the number of seconds it would take to read a range. We estimate it based on the average reading speed we have collected on quran.com.
Query Parameters
Possible values: Value must match regular expression ^(\d+:\d+-\d+:\d+(?:,\d+:\d+-\d+:\d+)*)$
a comma separated string of Ayah ranges e.g. 1:1-1:2
- 200
- 400
- 401
- 403
- 404
- 422
- 429
- 500
- 502
- 503
- 504
Request has been handled successfully.
Schema
data object
The number of seconds it would take on average to read the range of Ayahs.
{
  "success": true,
  "data": {
    "seconds": 66.8
  }
}
The request is missing required parameters or is invalid.
Schema
{
  "message": "The request is missing required headers or is invalid",
  "type": "invalid_request",
  "success": false
}
The request is unauthorized.
Schema
{
  "message": "The request requires user authentication",
  "type": "unauthorized",
  "success": false
}
Forbidden error. Can either be due to access token not being passed, having been expired or the caller trying to access a resource without enough permissions.
Schema
{
  "message": "The server understood the request, but refuses to authorize it",
  "type": "forbidden",
  "success": false
}
Not Found. The resource being accessed does not exist.
Schema
{
  "message": "The requested resource could not be found",
  "type": "not_found",
  "success": false
}
Validation Error. The request includes one or more invalid params. Please check the request params and try again.
Schema
{
  "message": "The request was well-formed but was unable to be followed due to semantic errors",
  "type": "unprocessable_entity",
  "success": false
}
Too many requests, please try again later.
Schema
{
  "message": "Too many requests, please try again later",
  "type": "rate_limit_exceeded",
  "success": false
}
Server Error. Something went wrong, try again later.
Schema
{
  "message": "The server encountered an internal error and was unable to complete your request",
  "type": "internal_server_error",
  "success": false
}
Invalid response from the upstream server
Schema
{
  "message": "The server was acting as a gateway or proxy and received an invalid response from the upstream server",
  "type": "bad_gateway",
  "success": false
}
The server is currently unable to handle the request due to a temporary overload or scheduled maintenance
Schema
{
  "message": "The server is currently unable to handle the request due to a temporary overload or scheduled maintenance",
  "type": "service_unavailable",
  "success": false
}
The server did not receive a timely response from the upstream server.
Schema
{
  "message": "The server was acting as a gateway or proxy and did not receive a timely response from the upstream server",
  "type": "gateway_timeout",
  "success": false
}