title: Linkedin API oAuth 2.0 REST Query parameters
body: <p>I'm running into a problem with adding a query to the callback URL. I'm getting an invalid URI scheme error attempting to authorize the following string:</p>
  
  <p><a href="https://www.linkedin.com/uas/oauth2/authorization?response_type=code&amp;client_id=75df1ocpxohk88&amp;scope=rw_groups%20w_messages%20r_basicprofile%20r_contactinfo%20r_network&amp;state=7a6c697d357e4921aeb1ba3793d7af5a&amp;redirect_uri=http://marktest.clubexpress.com/basic_modules/club_admin/website/auth_callback.aspx?type=linkedin" rel="nofollow">https://www.linkedin.com/uas/oauth2/authorization?response_type=code&amp;client_id=75df1ocpxohk88&amp;scope=rw_groups%20w_messages%20r_basicprofile%20r_contactinfo%20r_network&amp;state=7a6c697d357e4921aeb1ba3793d7af5a&amp;redirect_uri=http://marktest.clubexpress.com/basic_modules/club_admin/website/auth_callback.aspx?type=linkedin</a></p>
  
  <p>I've read some conflicting information in forum posts here. Some say that it's possible to add query strings to callbacks, and others say that it results in error.</p>
  
  <p>If I remove ?type=linkedin, I can authorize just fine and receive the token. It would make my life so much easier if I could use a query string on the callback url, as I need to do some additional processing in the callback.</p>
  
  <p><strong>In short, can I append a query string to the end of the callback url?</strong> </p>
  
  <p>For fun, I tried encoding the callback url in the request (obviously this is a no-no according to their documentation):
  <a href="https://www.linkedin.com/uas/oauth2/authorization?response_type=code&amp;client_id=75df1ocpxohk88&amp;scope=rw_groups%20w_messages%20r_basicprofile%20r_contactinfo%20r_network&amp;state=5cabef71d89149d48df523558bd12121&amp;redirect_uri=http%3a%2f%2fmarktest.clubexpress.com%2fbasic_modules%2fclub_admin%2fwebsite%2fauth_callback.aspx%3ftype%3dlinkedin" rel="nofollow">https://www.linkedin.com/uas/oauth2/authorization?response_type=code&amp;client_id=75df1ocpxohk88&amp;scope=rw_groups%20w_messages%20r_basicprofile%20r_contactinfo%20r_network&amp;state=5cabef71d89149d48df523558bd12121&amp;redirect_uri=http%3a%2f%2fmarktest.clubexpress.com%2fbasic_modules%2fclub_admin%2fwebsite%2fauth_callback.aspx%3ftype%3dlinkedin</a></p>
  
  <p>This also resulted in an error but was worth a shot.</p>
  
  <p> The documetation here: <a href="https://developer.linkedin.com/forum/oauth-20-redirect-url-faq-invalid-redirecturi-error" rel="nofollow">https://developer.linkedin.com/forum/oauth-20-redirect-url-faq-invalid-redirecturi-error</a> indicates that you CAN use query parameters. And in the first request, it appears that I'm doing it correctly. Post #25 on this page - <a href="https://developer.linkedin.com/forum/error-while-getting-access-token" rel="nofollow">https://developer.linkedin.com/forum/error-while-getting-access-token</a> indicates that you have to remove the query parameters to make it work</p>
  
  <p><strong>Anyone have experience with successfully passing additional query paramaters in the callback url for the linkedin API using oAuth2.0? If so, what am I doing wrong?</strong></p>