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
  • ParqEx API Uses OAuth
  • OAuth Flow Overview

Was this helpful?

  1. OAUTH

Overview

PreviousTesting AccountsNextHow to Authorize Access

Last updated 4 years ago

Was this helpful?

ParqEx API Uses OAuth

All requests to the ParqEx service are governed by OAuth 2.0 () and follow the standard authorization-access token flow.

The ParqEx implementation closely follows .

OAuth Flow Overview

When a user attempts to authorize their ParqEx account from your application, the following happens:

  1. Your app generates the Authorization URL and displays the ParqEx login form to the user (see Step 1)

  2. ParqEx attempts to authenticate the supplied credentials, and if successful, the user is asked to authorize access to their ParqEx account.

  3. When the user authorizes access, an authorization_code is sent back to your app via a GET request (see Step 2)

  4. Next, your app uses the authorization_code to request an access_token and refresh_token (see Step 3)

  5. Once you have an access_token, you can call the ParqEx API on the user's behalf (see Step 4)

quick primer
RFC 6749