> ## Documentation Index
> Fetch the complete documentation index at: https://docs.drime.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# The Application Folder

> Working inside one folder of each user's Drive

An application created with **A folder of its own** never sees the rest of the Drive. When a user authorizes it, Drime creates a folder for it in their personal Drive:

```
Their Drive
└── Applications
    └── Your application name    (everything your application can see)
```

Several applications get several folders under the same `Applications` folder.

## Find your folder

```bash theme={null}
curl https://app.drime.cloud/api/v1/drive/app-folder \
  -H "Authorization: Bearer $ACCESS_TOKEN"
```

```json theme={null}
{
  "app_folder": {
    "id": 84213,
    "name": "Lumo",
    "type": "folder",
    "hash": "ODQyMTN8cGFkZA"
  },
  "status": "success"
}
```

The real object carries more fields; `id` is the one to keep. An application that works on the whole Drive gets `{"app_folder": null}` from the same route, so one code path serves both kinds. An invalid token gets `401`.

## Inside and outside

Inside the folder, your application uses the API like any other client. Outside it, nothing exists for your application:

| | |
| - | - |
| An id or a hash from elsewhere in the Drive | `404`, on every endpoint |
| A listing with no `folderId` | Lists your folder |
| An upload, or a new folder or document, with no `parentId` | Lands in your folder, not at the top of the Drive |
| `workspaceId` other than `0` | `403`: your folder lives in the personal Drive, team workspaces are out of reach |
| The sync API (`/sync/…`) | `403`: it works on the whole Drive |
| `workspaces.*` and `vault.*` scopes | Cannot be selected for this kind of application |

## What the user can do with the folder

* **Rename it or move it.** Your application keeps working: it is tied to the folder itself, not to its name or its place.
* **Delete it.** A new, empty one is created on a later call. Treat "my files are gone" as a state you can recover from.
* **Disconnect your application.** If they authorize it again later, Drime reuses the folder if it is still called exactly like your application, directly inside `Applications`. Otherwise it creates a new, empty one.

After the user moves or deletes the folder, allow up to a minute before your application sees the change.

Revoking your own tokens with [`/oauth/revoke`](/oauth/authorization-flow) does not lose the folder: when the user authorizes again, you find the same one, with its contents.

## Storage

The folder uses the account's storage quota. It limits what your application can reach, not how much it can store.

## Notifications

[Webhooks](/oauth/webhooks) name the account that changed, not the folder: your application can be notified of a change made elsewhere in the user's Drive. List your folder to see whether anything changed in it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.