Reference · built on requestConnectorFiles, documents & spreadsheets

Egnyte

Files, folders, permissions, and events from an Egnyte domain through the Public API, with webhooks for file activity.

Request accessPricing ↗

About

Egnyte is a governed file platform. A domain holds shared and private folders with file versions, locks, folder permissions, links, comments, custom metadata, and workflows. The Public API reads and writes that file system by path or persistent id, streams changes through the Events API, and pushes them through webhooks.

Through Fibric, an operator reads folders, versions, and permission changes, checks them against your policies, and proposes a move, a folder, an upload, or a lock. You approve. The file operation runs once, and a receipt records what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Egnyte and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Files and folders by path or persistent id through GET /pubapi/v1/fs/{path}, with versions, locks, permissions, and custom metadata on request
  • File bytes through GET /pubapi/v1/fs-content/{path}, with Range and If-None-Match, and a SHA512 checksum in the response
  • Domain activity through the Events API cursor: file_system, note, and, on v2, permission_change events
  • Webhook deliveries for fs:add_file, fs:move_file, fs:delete_file, link:create_download_link, comment:set_comment, and permission:permission_change
  • Workflow events workflow:created, workflow:completed, workflow:approvaltask_approved, and workflow:approvaltask_rejected
  • Folder size and item counts through GET /pubapi/v1/fs/ids/folder/{FOLDER_ID}/stats
  • Content search across filenames, metadata, and text through the Search API

Proposed actions

  • Target capability: propose creating a folder through POST /pubapi/v1/fs/{path} with action add_folder
  • Target capability: propose moving or copying a file or folder, with permissions set to keep_original or inherit_from_parent
  • Target capability: propose uploading a file through POST /pubapi/v1/fs-content/{path}, chunked above 100 MB
  • Target capability: propose locking a file with action lock for a set lock_timeout, releasing it later with the same lock_token
  • Target capability: propose moving a file or folder to the trash through DELETE /pubapi/v1/fs/{path}

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Evidence packet from a controlled folder

    The operator lists a policy folder with versions and custom metadata, downloads the current version of each file with its SHA512 checksum, and proposes an evidence packet naming folder path and version ids.

    With Compliance Evidence

  • Review who can see a folder

    permission:permission_change webhooks and v2 events carry the old and new privilege. The operator compiles changes per folder for the review period and proposes which grants to confirm or remove.

    With Access Review

  • Keep an audit trail of file moves

    Every fs:move_file and fs:delete_file delivery is recorded with actor, source path, target path, and eventId. The operator proposes a weekly digest of moves out of restricted folders.

    With Audit Trail

  • Watch folders that keep growing

    The operator reads folder stats for the shares you name and proposes an alert when allVersionsSize outgrows its usual pace, with the largest subfolders listed.

    With Storage Growth

Requirements

  • An Egnyte domain and an API key registered for the application; an unapproved key works only on the domain registered in its profile
  • An OAuth 2.0 flow that fits the app: Authorization Code for public apps, Resource Owner Password Credentials for an internal app
  • Scopes Egnyte.filesystem for files, events, search, comments, and trash; Egnyte.webhooks for webhooks; Egnyte.permission for folder permissions
  • A callback endpoint with a CA-signed TLS certificate for webhooks; self-signed certificates are rejected
  • A user account whose folder permissions cover what the operator reads, since calls run in that user's permission context
Authentication
An OAuth 2.0 access token from /puboauth/token on your Egnyte domain, sent as Authorization: Bearer, scoped to APIs such as Egnyte.filesystem, Egnyte.permission, and Egnyte.webhooks.

Limits

  • Standard calls are limited to 1,000 per day and 2 per second per access token; higher limits are arranged with Egnyte
  • Webhook delivery retries four times (immediate, 1 minute, 10 minutes, 1 hour), then the registration is disabled
  • The event stream keeps the latest 500,000 events for up to 30 days, and Egnyte asks for polling intervals of 5 minutes or more
  • Access tokens expire after 30 days and are revoked when the user changes a password

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Egnyte ↗

Questions and answers

What is the difference between the Events API and webhooks?
Events is pull: you poll GET /pubapi/v1/events with a cursor, at 5 minutes or more between calls, and can read back up to 30 days. Webhooks are push: Egnyte POSTs to your endpoint in near real time, filtered by eventType and up to 100 paths, with four delivery attempts.
How do rate limits work?
Per access token: 1,000 standard calls per day and 2 per second. Each response carries X-Accesstoken-Qps-Allotted, X-Accesstoken-Qps-Current, X-Accesstoken-Quota-Allotted, and X-Accesstoken-Quota-Current. The token endpoint has its own limits and answers throttled requests with 409 and Retry-After.
How are large files uploaded?
Above 100 MB, Egnyte documents a chunked upload: chunks between 10 MB and 1 GB, all the same size except the last, each with an X-Egnyte-Chunk-Sha512-Checksum header. The first chunk returns X-Egnyte-Upload-Id, and chunks expire 24 hours after the first one.
Ask about Egnyte

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Egnyte through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy