DoorFlow Integration Approval Checklist

Why We Have an Approval Process

Access control systems manage physical security for buildings and spaces. Our approval process ensures:

1. Security - Your integration handles access credentials safely and follows security best practices
2. Reliability - Your integration works properly with our systems for a seamless customer experience

---

Benefits for You as a Developer

• Reduced Support Burden: Approved integrations have fewer support tickets and customer issues
• Technical Guidance: We'll help you avoid common pitfalls and use our APIs efficiently
• Visibility: Opportunity to be featured in our App Directory for more exposure in the future

---

Integration Checklist

Check off each item during development. We'll review the same list during our demo call.

Authentication & Core Setup

• [ ] OAuth Implementation - Properly handle authorization flow with refresh tokens
  • [ ] Use state parameter to support multiple DoorFlow accounts
  • [ ] Secure token storage following best practices
  • [ ] "Connect to DoorFlow" button with correct branding
  • [ ] "Disconnect from DoorFlow" button that revokes tokens

People Management

• [ ] Person Records
  • [ ] Create DoorFlow person records for all members (even before they need credentials)
  • [ ] Properly set organisationsystemid for all created people (this allows us to map a DoorFlow person record with an identifier from the canonical main membership directory
  • [ ] Avoid creating duplicate person records (one person = one record)
  • [ ] Cache person data locally to minimize API calls

Credentials & Access

• [ ] Credential Handling
  • [ ] Present credential options dynamically from DoorFlow API
  • [ ] Support all credential types (cards, pins, mobile passes) for an account https://developer.doorflow.com/docs/categories/api/articles/47861#list-all-credential-types
  • [ ] Implement proper validation for credentials
  • [ ] Support mobile access passes if applicable

Group Management

• [ ] Group Mapping
  • [ ] Cache and display DoorFlow Groups in your UI
  • [ ] Provide admin UI for mapping your groups/membership levels to DoorFlow Groups
  • [ ] Use Groups for access permissions

API Usage & Performance

• [ ] Efficient API Usage
  • [ ] Call /sync after batches of changes (not per individual change)
  • [ ] Handle all appropriate HTTP responses
  • [ ] Maintain local caches to reduce API calls

Optional Features

• [ ] Webhooks (if implemented)
  • [ ] Consume events via webhooks
  • [ ] Process data changes from DoorFlow by requesting resources from the DoorFlow API
  • [ ] Send ack_token with DoorFlow API triggered by the webhook https://developer.doorflow.com/docs/categories/api/articles/47877#acknowledge-token

---

What to Expect During Approval

1. Demo request: Contact us at developer@doorflow.com to request a demonstration outlining the scopes that your integration will be using.
2. Demo Call: Schedule once your implementation meets all checklist items
3. Production Approval: Typically 1-3 business days after successful demo

Need Help?

Contact our developer support at developer@doorflow.com with any questions.