Search or ask...
Getting Started
Sections
Getting Started
Introduction
Overview
Features
Cloud-driven Device Management
Getting Started FAQ
Yonomi Platform Developer Portal
Schlage XE360
YP No Tour overview
BLE Proxy overview
Yonomi Platform Concepts
General Terms: Roles
General Terms: Concepts
YP Developer Portal Account
Dev Resource Group
Installation
Organization
Integration
Application Clients
User Scope Clients vs. M2M Clients
Client Use Cases
Webhook
Relationship between Integrations, Organizations and Installations
Identity Federation
Device Claiming
Common Device Workflows
Prerequisites
Determining if a Device is Claimable
Architecture
The Yonomi Platform Solution
Technology Stack overview
Core Components
Platform Interface
Traits
Queries
Training Project
Training Project Solution Goal
What We Will Build
What's Not Covered
Training: YP Developer Portal
Login to YP Developer Portal
Training: Create a Dev Resource Group
Dev Resource Groups Elements
YP Dev Portal: Organization ID
YP Dev Portal: Integrations
YP Dev Portal: Application Clients
YP Dev Portal: Webhooks
YP Dev Portal : Federation Configurations
Training: Create an Integration
Training : Create an M2M Client
Training Create a Webhook Configuration
Training: Create an Identity Federation Configuration
Training: Create a User Scope Application Client
Summary: YP Developer Portal
API Training Section 1: Working with th eYP GraphQL API
Training: Using Postman for API Requests Part 1
Training: Generating Access Tokens using the Client Credential Client
Training: Generating Access Tokens using the M2M Client
Training: Using Postman for API Requests Part 2
Training: Create the Acme Living Organization (Request #2)
Sidequest: Observe the Scripts and Automatically Set Variables
Create the 125 Ocean Ave Installation (Request #5)
Query the Romanworks Integration ID (Request #8)
Authorize the Romanworks Integration to manage the Acme Org (Request #9)
List Authorized Integrations for Acme Living Org (Request #10)
Training: Confirming the Webhooks Subscription
The first webook event: A subscription confirmation request from YP
Training: Preparation for Claiming a Device
Training App
Set the Claim Token in Postman
Sidequest: How to FDR the XE360 WiFi Lock
Sidequest: Device Time
API Training Section 2: Claiming a Device
Training: Set the Claim Token in Postman
Training: Claim a Device (Request #11)
Training: Triggered Events
Training: Raw Event Data
Training: The Message Field
API Training Section 3: Working with Devices
Trait Actions and the Action Lifecycle
API Calls
Single API Call with Synchrounous Resolution
Single API Call with Asynchrounous Resolution
Two-step Bulk Upload Process with Asynchrounous Resolution
Events in Yonomi Platform
Action-Lifecycle Events
Device History Events
Training: Working with Devices
Device Queries
Device Actions: Examples of Single API Calls with Asynchrounous Resolution
Trait Action Resolution: Webhooks vs. Event Queries
Device Actions: Examples of 2-Step API Calls with Asynchronous Resolution
Changelog
Theme switcher
Relationship between Integrations, Organizations and Installations
Integrations
are owned by
PACS Partners
.
Organizations
and
Installations
are owned by
Owners
.
Integrations
represent a
relationship
through which PACS Partners are permitted to manage the installations in owner’s organization.
Owners grant PACS Partners permission to manage
their hardware installations by granting that authority to a PACS Partner’s Integration object.
Was this section helpful?
Yes
No
What made this section unhelpful for you?
Confusing or unclear information
Incorrect or outdated information
Incomplete information or samples
Other
Cancel
Submit
On this page
Relationship between Integrations, Organizations and Installations
