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
  • Device
  • Door

Was this helpful?

  1. THE BASICS

Entities

Device

A Device represents a single ParqEx Access Controller. Each device can have one or more Door (depending on the model. see below what a single-door entity looks like). The attributes of a Device are as follows:

Attribute Name

Data Type

Description

id

UUID

Unique identifier of the Device

number_of_entities_controlled

Integer

1-100

doors

Object

An object array of Doors (see below)

last_contact

Timestamp (eg. YYYY-MM-DD HH:MM:SS)

Timestamp of the last time the Device reached out to the ParqEx service

active

Boolean

true if Device is enabled/authorized by ParqEx, false otherwise

registered

Boolean

true if Device is registered with ParqEx, false otherwise

Door

A Door represents a single access control point (pedestrian door, garage door, elevator button etc.) opener connected to a ParqEx Controller. A Door must belong to a device. The attributes of a device are as follows:

Attribute Name

Data Type

Description

id

UUID

Unique identifier of the Door

image

String

Deprecated

light

Boolean

Deprecated

sensor

Boolean

Deprecated

last_toggled

Timestamp (eg. YYYY-MM-DD HH:MM:SS)

Timestamp of the last time the Device reported a Door state change

name

String

A name assigned by the user. Every user can set their own unique names.

active

Boolean

true if the Door has been registered to a Device, false otherwise

state

Enum

Either “OPEN” or “CLOSED”. Represents current state of door.

user_relationship

String

PreviousAndroid Implementation GuideNextBest Practices

Last updated 4 years ago

Was this helpful?

“Owner” if the current user is the admin of the Device, “Has Access” otherwise (see )

Permissions