LogoLogo
  • Introduction
  • OVERVIEW
    • About ParqEx
      • -- Marketplace
      • -- Access+
      • -- GuestParq & GuestAccess
      • -- Enforcer
    • API Requirements
    • Roles and Permissions
  • GETTING STARTED
    • Requesting an Account
    • Using RESTful Tools
    • Webhooks
  • Embedding ParqEx in Native Mobile Apps
    • Overview
    • FAQ
    • Technical Documentation
      • iOS Implementation Guide
      • Android Implementation Guide
  • THE BASICS
    • Entities
    • Best Practices
    • Testing Accounts
  • OAUTH
    • Overview
    • How to Authorize Access
      • Step 1: Generate Authorization URL
      • Step 2: Handle Authorization Response
      • Step 3: Request an Access Token
      • Step 4: Call API Endpoints
      • Step 5: Refresh the Tokens
  • API ENDPOINTS
    • Overview
    • Get User Info
    • Get User Settings
    • Get User Devices
    • Toggle Access Point
    • Invite User (internal)
    • Get Access History
Powered by GitBook
On this page

Was this helpful?

  1. OAUTH
  2. How to Authorize Access

Step 2: Handle Authorization Response

Assuming the user approves the request, an authorization code is generated and sent back to your application via the query string of the ENCODED_REDIRECT_URL. If the authorization request included state, the exact same value will be returned in the authorization response.

Which follows this format (line breaks added for clarity):

GET https://example.org/?
    code=<CODE>&
    state=<STATE>

For example (line breaks added for clarity):

GET https://example.org/?
    code=1fe21db7d29e61a9dd90da9eef675ea8&
    state=dzRBV1RxdWg5S0JWUTBhMGpEUy9NT3lGS2xjbkRsMHBDeEJDTXdPS1JpRzhlS3FFRmorOHo2SUoxZmlYb0o4dE8wRGM3Nnhwd0xNbWRIUWUvSmptM2c9PS0tSk4yM1Y2ckR1WmZCUGxjc3JBWDBhdz09--e6f508aa05569a93aaa02414c20ab808e8fbda49

Warning! If the state does not exactly match the state that you are expecting, do not continue.

PreviousStep 1: Generate Authorization URLNextStep 3: Request an Access Token

Last updated 4 years ago

Was this helpful?