Get your current rate limit status

GET /rate_limit

Response

Status: 200 OK
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4999
X-RateLimit-Reset: 1372700873

{
  "resources": {
    "core": {
      "limit": 5000,
      "remaining": 4999,
      "reset": 1372700873
    },
    "search": {
      "limit": 30,
      "remaining": 18,
      "reset": 1372697452
    },
    "graphql": {
      "limit": 5000,
      "remaining": 4993,
      "reset": 1372700389
    },
    "integration_manifest": {
      "limit": 5000,
      "remaining": 4999,
      "reset": 1551806725
    }
  },
  "rate": {
    "limit": 5000,
    "remaining": 4999,
    "reset": 1372700873
  }
}

Understanding your rate limit status

The Search API has a custom rate limit, separate from the rate limit governing the rest of the REST API. The GraphQL API also has a custom rate limit that is separate from and calculated differently than rate limits in the REST API.

For these reasons, the Rate Limit API response categorizes your rate limit. Under resources, you'll see four objects:

• The core object provides your rate limit status for all non-search-related resources in the REST API.
• The search object provides your rate limit status for the Search API.
• The graphql object provides your rate limit status for the GraphQL API.
• The integration_manifest object provides your rate limit status for the GitHub App Manifest code conversion endpoint.

For more information on the headers and values in the rate limit response, see "Rate limiting."

Deprecation notice

The rate object (shown at the bottom of the response above) is deprecated.

If you're writing new API client code or updating existing code, you should use the core object instead of the rate object. The core object contains the same information that is present in the rate object.