🔐Authentication Options

Some API requests require authentication using a Bearer token in the request header.

Ellipsis Drive supports multiple authentication mechanisms, depending on your integration type and required access scope.

Note: Public and Link-shared layers do not require authentication.

A User Token grants access to all resources that the authenticated user has permission to access.

It is typically used for user-driven applications or personal integrations.

An Access Token provides scoped access to specific folders or layers defined during token creation.

It is commonly used for secure, limited-scope integrations such as client-specific data access or embedded applications.

OAuth is the recommended authentication method for production applications.

It allows users to grant your application delegated access to their Ellipsis Drive account without sharing credentials.

OAuth tokens inherit the user’s permissions while enabling secure application-level control.

Tokens can be generated via:

Depending on your implementation preferences and system architecture.

For simpler integrations, you can redirect users to:

After login, the user is redirected back to your application with a token included in the URL.

This approach is easier to implement, but less secure and less controllable than OAuth.

Last updated 2 months ago