Return to Answer

You are subject to throttling.

You can get more calls by first registering your application. After that you get access to a detail page which includes a value for key. The description for that field is:

Pass this as key when making requests against the Stack Exchange API to receive a higher request quota.

 

This is not considered a secret, and may be safely embed in client side code or distributed binaries.

Once you have your key, the url to use becomes:

/users/+J+/questions?order=desc&sort=activity&site=stackoverflow&key=*somekey*

I have an example here where I use a key query parameter in a similar way.

Keep in mind to still check for the existence of a value in the backoff field in the wrapper response. It indicates the number of seconds to wait before you are allowed to make the next call.

You are subject to throttling.

You can get more calls by first registering your application. After that you get access to a detail page which includes a value for key. The description for that field is:

Pass this as key when making requests against the Stack Exchange API to receive a higher request quota.

This is not considered a secret, and may be safely embed in client side code or distributed binaries.

Once you have your key, the url to use becomes:

/users/+J+/questions?order=desc&sort=activity&site=stackoverflow&key=*somekey*

I have an example here where I use a key query parameter in a similar way.

Keep in mind to still check for the existence of a value in the backoff field in the wrapper response. It indicates the number of seconds to wait before you are allowed to make the next call.

You are subject to throttling.

You can get more calls by first registering your application. After that you get access to a detail page which includes a value for key. The description for that field is:

Pass this as key when making requests against the Stack Exchange API to receive a higher request quota.

This is not considered a secret, and may be safely embed in client side code or distributed binaries.

Once you have your key, the url to use becomes:

/users/+J+/questions?order=desc&sort=activity&site=stackoverflow&key=*somekey*

I have an example here where I use a key query parameter in a similar way.

Keep in mind to still check for the existence of a value in the backoff field in the wrapper response. It indicates the number of seconds to wait before you are allowed to make the next call.

You are subject to throttling.

You can get more calls by first registering your application. After that you get access to a detail page which includes a value for key. The description for that field is:

Pass this as key when making requests against the Stack Exchange API to receive a higher request quota.

This is not considered a secret, and may be safely embed in client side code or distributed binaries.

Once you have your key, the url to use becomes:

/users/+J+/questions?order=desc&sort=activity&site=stackoverflow&key=*somekey*

I have an example here where I use a key query parameter in a similar way.

Keep in mind to still check for the existence of a value in the backoff field in the wrapper response. It indicates the number of seconds to wait before you are allowed to make the next call.

You are subject to throttling.

You can get more calls by first registering your application. After that you get access to a detail page which includes a value for key. The description for that field is:

Pass this as key when making requests against the Stack Exchange API to receive a higher request quota.

This is not considered a secret, and may be safely embed in client side code or distributed binaries.

Once you have your key, the url to use becomes:

/users/+J+/questions?order=desc&sort=activity&site=stackoverflow&key=*somekey*

I have an example here where I use a key query parameter in a similar way.

Keep in mind to still check for the existence of a value in the backoff field in the wrapper response. It indicates the number of seconds to wait before you are allowed to make the next call.

You are subject to throttling.

You can get more calls by first registering your application. After that you get access to a detail page which includes a value for key. The description for that field is:

Pass this as key when making requests against the Stack Exchange API to receive a higher request quota.

This is not considered a secret, and may be safely embed in client side code or distributed binaries.

Once you have your key, the url to use becomes:

/users/+J+/questions?order=desc&sort=activity&site=stackoverflow&key=*somekey*

I have an example here where I use a key query parameter in a similar way.

Keep in mind to still check for the existence of a value in the backoff field in the wrapper response. It indicates the number of seconds to wait before you are allowed to make the next call.