# Manage Doors via API

Third-party platforms can programmatically control Verkada-managed doors with the **Enable Door Management via API** setting enabled using Verkada’s access control API.

### Applicable Door Management APIs

The following Access Control API categories include APIs that require all doors controlled with the API to have **Enable Door Management via API** enabled.

* [Access Door Unlock APIs](https://apidocs.verkada.com/reference/postaccessadminapiunlockviewv1)
* [Door Exception Calendar APIs](https://apidocs.verkada.com/reference/getaccessdoorexceptioncalendarsviewv1)
* [Access Level APIs](https://apidocs.verkada.com/reference/getaccesslevelview)

{% hint style="warning" %}
See [Verkada API Docs](https://apidocs.verkada.com/) for details on specific API endpoints that require this setting.
{% endhint %}

***

## Command Configuration

Before a door can be controlled via API, permissions to control the door via API need to be enabled at the following levels:

* [Organization level](https://help.verkada.com/access-control/integrations-and-alerts/manage-doors-via-api)
* [Site level](https://help.verkada.com/access-control/integrations-and-alerts/manage-doors-via-api)
* [Door level](https://help.verkada.com/access-control/integrations-and-alerts/manage-doors-via-api)

### Organization level configuration

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**On the left navigation, click Access Settings .**
{% endstep %}

{% step %}
**Toggle on Enable Door Management via API.**
{% endstep %}
{% endstepper %}

### Site level configuration

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**From the All Sites dropdown, select a site.**
{% endstep %}

{% step %}
**At the top, click Access Settings .**
{% endstep %}

{% step %}
**Toggle on Enable Door Management via API.**
{% endstep %}
{% endstepper %}

### Door level configuration

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**From the All Sites dropdown, select a site.**
{% endstep %}

{% step %}
**Select a door and click Settings .**
{% endstep %}

{% step %}
**Under Installer Settings, toggle on Enable Door Management via API.**
{% endstep %}
{% endstepper %}

***

## Reviewing API Unlock Events

When a door unlock API call is used, an event is logged in Command indicating that a request to unlock a door via API was made. The event will indicate whether access was granted, what API was used, and (if applicable) an access user associated with the request.

Events associated with a door unlock API request can be viewed on the access control [Reports](https://help.verkada.com/access-control/integrations-and-alerts/access-control-reports) page or on the [door page](https://help.verkada.com/access-control/configuration/configure-a-door-in-command/view-access-control-doors) for a relevant door.

Events associated with door unlock API requests include the following information:

* **Event Name:** Access Granted or Access Denied
* **Method:** User Unlock API or Admin Unlock API
* **User** (if method is User Unlock API): Access user associated with the unlock request.
* **Credential:** Name of the [Verkada API Key](https://apidocs.verkada.com/reference/quick-start-guide) used to make the API unlock request.

![](https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-cf0634a515298f6859d83b4003fdfe66e7be1d0f%2F7a19b9a1125e6501a1d598feac3e3287d32a2029.png?alt=media)

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=nvJkh2jyOjU).
{% endhint %}
