Egnyte
Egnyte is a content cloud where businesses store, share, and govern their files in Shared and Private folders, share content with outside parties through links, and manage users, groups, and folder permissions. The Egnyte connector reads files, folders, links, permissions, users, groups, comments, metadata, project folders, and audit and file system events, and can create folders, links, users, groups, comments, bookmarks, and permissions.

Power end-to-end data operations for your Egnyte API with Nexla. Our bi-directional Egnyte connector is purpose-built for Egnyte, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Egnyte or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Egnyte workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Nexla connects to Egnyte through the Egnyte Public API on your own Egnyte domain (https://<your-domain>.egnyte.com), using an Egnyte API key that your organization registers. Egnyte does not offer self-serve API keys, so complete the following steps before creating a credential in Nexla.
-
Confirm that your organization is on an eligible Egnyte plan. Egnyte API keys are not available for Trial, Legacy Office, or Team plan domains.
-
Have an active Egnyte domain administrator request an API key at developers.egnyte.com. Egnyte declines key requests from users who are not domain administrators, and a domain can hold at most five API keys.
-
Choose the application type that matches the authentication method you plan to use:
-
OAuth 2.0 (Authorization Code): Register the key with the redirect URL
https://dataops.nexla.io/nexla-api/oauth/callback. The redirect URL sent during sign-in must match the URL registered on the key exactly. -
OAuth 2.0 (Username and Password, internal apps): Register the key as an internal application. The password grant is intended for trusted internal applications only.
-
-
Wait for Egnyte to approve the key. New keys start as Pending Approval and become Active after Egnyte approves them; Egnyte sends an activation email, and the key works within about 20 minutes of that email.
-
Copy the key (used as the API Key (Client ID) in Nexla) and its shared secret (the Client Secret). Keys issued after January 2015 require the secret.
Until a key is approved for production use, it only works against the single Egnyte domain registered on the key. Using one key across multiple Egnyte domains requires Egnyte's production approval, and production-approved keys must request their scopes explicitly. For complete details, see Egnyte's Getting Started and Authentication guides.
Egnyte enforces limits per access token (not per API key): by default, 2 calls per second and a daily call quota that depends on your plan, from 1,000 calls per day (Business and Essentials) to 2,000 (Enterprise Lite and Elite) or 4,000 (Enterprise and Ultimate). The daily quota resets at 00:00 UTC. Listing a large folder tree or user base can use up the daily quota, so schedule sources that page through large result sets accordingly. Token requests are limited separately: 100 per hour for public applications, and 10 per user per hour for internal applications that use the password grant. See Egnyte's API best practices and FAQ for current limits.
Authenticate
Every Egnyte credential needs your Egnyte Domain: the part of your Egnyte URL before .egnyte.com, entered without https:// or a trailing slash. For example, for https://acme.egnyte.com, enter acme. Nexla uses the domain for the token request and for every endpoint URL.
Credentials required
- OAuth 2.0 (Authorization Code)
- OAuth 2.0 (Username and Password, internal apps)
Sign in to Egnyte in the browser. Needs an Egnyte API key and secret registered by a domain admin at developers.egnyte.com, with the Nexla callback as its redirect URL.
| Field | Required | Secret | Description |
|---|---|---|---|
| Egnyte Domain | Yes | No | Your Egnyte domain name only: the part before .egnyte.com, without https:// or a trailing slash. For https://acme.egnyte.com enter acme. |
| API Key (Client ID) | Yes | Yes | The key of your Egnyte API key, from developers.egnyte.com (My Account > Applications). |
| Client Secret | Yes | Yes | The shared secret shown for the same Egnyte API key. |
| Access Scope | No | No | Space-separated Egnyte scopes to request. The default covers every source and destination in this connector; production-approved keys must request scopes explicitly. |
Password grant for internal Egnyte API keys: exchanges a user's username and password plus the key and secret for a token. Egnyte allows 10 token requests per user per hour.
| Field | Required | Secret | Description |
|---|---|---|---|
| Egnyte Domain | Yes | No | Your Egnyte domain name only: the part before .egnyte.com, without https:// or a trailing slash. For https://acme.egnyte.com enter acme. |
| API Key (Client ID) | Yes | Yes | The key of your internal Egnyte API key, from developers.egnyte.com. |
| Client Secret | Yes | Yes | The shared secret of the same Egnyte API key (required for keys issued after January 2015). |
| Username | Yes | No | Egnyte username of the account Nexla acts as. |
| Password | Yes | Yes | Password of that Egnyte user. Changing the password revokes the token, so update it here afterwards. |
| Scopes | Yes | No | Space-separated Egnyte scopes to request. The default covers every source and destination in this connector. |
Both methods request the scopes Egnyte.filesystem Egnyte.link Egnyte.permission Egnyte.user Egnyte.group Egnyte.audit Egnyte.bookmark Egnyte.projectfolders by default, which cover every source and destination template on this page. Egnyte scopes are granted per API rather than per operation, so there is no read-only scope. If you narrow the scopes, templates that need an omitted scope will fail.
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Select the authentication method you want to use, and enter the required values:
-
OAuth 2.0 (Authorization Code): Enter your Egnyte Domain, the API Key (Client ID), and the Client Secret of your Egnyte API key. Optionally, adjust the Access Scope. When you save, Nexla opens the Egnyte sign-in page in your browser; sign in as the Egnyte user that Nexla should act as, and approve access.
-
OAuth 2.0 (Username and Password, internal apps): Enter your Egnyte Domain, the API Key (Client ID) and Client Secret of an internal Egnyte API key, and the Username and Password of the Egnyte user that Nexla should act as. Optionally, adjust the Scopes.
Changing the Egnyte user's password revokes the token issued with the old password, so update the Password on this credential after a password change. Egnyte allows 10 token requests per user per hour for internal applications.
-
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by reading the signed-in user's profile from Egnyte. The data the credential can read or change is limited to what that Egnyte user can access: for example, non-admin users only see the links they created, and the audit, user creation, user update, and group creation templates require a domain administrator.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Egnyte connector tile, then select the credential that will be used to connect to Egnyte, and click Next; or, create a new Egnyte credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Egnyte endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Egnyte addresses files and folders by path. Unless a template says otherwise, enter paths without a leading slash (for example, Shared/Projects); top-level team content lives under Shared, and each user's own space lives under Private/<username>.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Egnyte data sources can also be manually configured to ingest data from any valid Egnyte Public API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. Egnyte endpoint URLs take the form https://<your-domain>.egnyte.com/pubapi/...; see the Egnyte API documentation for the available endpoints.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Egnyte data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the Egnyte destination, and select the Send to Destination option from the menu. Select the Egnyte connector from the list of available destination connectors, then select the credential that will be used to connect to Egnyte, and click Next; or, create a new Egnyte credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Egnyte endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent as the JSON body of one request, one record at a time. Path and ID settings, such as Source Path or User ID, are fixed on the destination and apply to every record it sends, so each record acts on the same file, folder, user, or group.
Manual configuration
Egnyte destinations can also be manually configured to send data to any valid Egnyte Public API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Egnyte Public API expects JSON request bodies for the operations covered by the templates above. Destination writes count toward the same per-token rate limits as sources: 2 calls per second and a plan-dependent daily quota.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Egnyte endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Egnyte endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.