Skip to main content
replaced http://stackapps.com/ with https://stackapps.com/
Source Link

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

For intense "Big data" analysis beyond even SEDE's capabilities, use the quarterly data dumps. (Thanks, Tim Stone, for the reminder.)


If you really must use the API, follow these guidelines:

  1. Register your appRegister your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

For intense "Big data" analysis beyond even SEDE's capabilities, use the quarterly data dumps. (Thanks, Tim Stone, for the reminder.)


If you really must use the API, follow these guidelines:

  1. Register your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

For intense "Big data" analysis beyond even SEDE's capabilities, use the quarterly data dumps. (Thanks, Tim Stone, for the reminder.)


If you really must use the API, follow these guidelines:

  1. Register your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.
added 201 characters in body
Source Link
Brock Adams
  • 13k
  • 5
  • 39
  • 64

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

For intense "Big data" analysis beyond even SEDE's capabilities, use the quarterly data dumps. (Thanks, Tim Stone, for the reminder.)


If you really must use the API, follow these guidelines:

  1. Register your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

If you really must use the API, follow these guidelines:

  1. Register your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

For intense "Big data" analysis beyond even SEDE's capabilities, use the quarterly data dumps. (Thanks, Tim Stone, for the reminder.)


If you really must use the API, follow these guidelines:

  1. Register your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.
Source Link
Brock Adams
  • 13k
  • 5
  • 39
  • 64

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes.

If you really must use the API, follow these guidelines:

  1. Register your app.
  2. Make sure you do not bust your quotas.
  3. Monitor and respect the backoff flag.
  4. For anything more, contact the API team and negotiate for special access.