Lavanda Developer Docs
  • Welcome
  • Quickstart
    • Getting Started
    • Versioning
    • API Explorer
  • Concepts
    • Structure & Terms
    • Auth
    • Webhooks
    • API Paradigms
      • Connections
      • Pagination (Cursors)
      • Client Name Header
  • CRM
    • Leads
    • Contacts
    • Companies
    • Institutions
    • Offers
    • Subjects
  • Bookings
    • Bookings
  • Spaces & Inventory
    • Buildings
    • Unit Types
    • Units
  • Availability
    • Availability
  • Pricing
    • Pricing
    • Product
  • Ecommerce
    • Flow
    • Search
    • Checkout
  • Guest Messaging
    • General
  • Finance & Accounting
    • Invoices
    • Payments
  • Tickets
    • Tickets
    • Tasks
    • Charges
  • Users
    • Queries
      • whoami
    • Mutations
  • Legacy
    • README
    • Auth
    • Create Lead
    • Legacy Azure API
Powered by GitBook
On this page
  • Creating a new API Access Key
  • Key Permissions & Scopes
  1. Legacy

Auth

PreviousREADMENextCreate Lead

Last updated 8 months ago

The Azure Dev API uses API Access Keys for a workspace.

Each access key is bound to a given workspace and only has access to resources inside of that workspace. As such, if your API integration needs resources from multiple workspaces, then an API key will need to be created per workspace.

Creating a new API Access Key

An API key can be created via logging into the , and select the workspace to integrate against, then navigate to Settings -> Developer.

On this screen click the "Generate New Key" button.

This will issue you an API Access Key that can be used in the Azure Dev API.

Key Permissions & Scopes

Each API Key has defined scopes for what resources it is permitted to.

PMS application