Meditlink Scraper

Authorization protocols provide a state parameter that allows you to restore the previous state of your application. The state parameter preserves some state object set by the client in the Authorization request and makes it available to the client in the response.ref. https://auth0.com/docs/protocols/oauth2/oauth-state#csrf-attacks**Step #2. Login and Authorize approve**Clicking on this link will take the end user to the MeditLink OpenAPI Log In pageAfter entering their MeditLink ID credentials and logging in, the user will be redirected to the OAuth consent page.When consent has been granted, the user will be redirected back to your callback URL (redirect_uri) with an additional code query parameter that contains the authorization code (e.g., R24zS0EsRklPd0JtpFV7ua0EsRklPdS2).**Step #3. Implement Code that Extracts the Authorization Code**in this example, the user was redirected to http://your-domain-url/callback?code=R24zS0EsRklPd0JtpFV7ua0EsRklPdS2Your code that serves up the /callback URL in your web app should extract this code query parameter value and store it in a temporary variable.**Step #4. Exchange the Authorization Code for an Access Token**`POST https://openapi-auth.meditlink.com/oauth/token`Immediately after extracting the code query parameter value, you should exchange the authorization code for an access token using the `/oauth/token` endpoint.Replace the client_id, client_secret, code, and redirect_uri values in the example below with those specific to your app and from the above steps.Authorization: Basic {your-basic-authentication-value}Content-Type: application/x-www-form-urlencodedcode=R24zS0EsRklPd0JtpFV7ua0EsRklPdS2&state=bn6q6ru91ygkzwo8rfc0s1f7&grant_type=authorization_code&redirect_uri=http%3A%2F%2Flocalhost%3A20000%2Fcallback&scope=USER%20GROUPHost: openapi-auth.meditlink.com`you can use this example to instrument the correct call in your server-side code.