Egnyte | Operate As Docs

Connect your client's Egnyte with a sign-in, and call its API through Operate As.

Website: egnyte.com
Connects by: Signing in with Egnyte
Category: Files and docs
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Egnyte	`egnyte`	`https://{domain}.egnyte.com/pubapi`

Your client also types their egnyte domain (The start of your Egnyte address, before .egnyte.com).

Connecting

Your client presses Connect on their link and approves on Egnyte's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "egnyte"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "egnyte"    ]  }]

Permissions

What the client reads	Permission it asks for
See, add and change your files and folders	`Egnyte.filesystem`
Make and manage share links	`Egnyte.link`
See your Egnyte users	`Egnyte.user`

Pass-through

Egnyte has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

Add the client

In Clients, add your client and select Egnyte. Then send them their link.

Your client connects

They sign in with Egnyte and approve.

Find the endpoint

Pick the call from Egnyte's own API docs. Your path is everything after https://{domain}.egnyte.com/pubapi, with the parts in braces filled in from your client's account.

Send it through Operate As

Use the client's ID, the service key egnyte and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../egnyte/v1/userinfo" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../egnyte/v1/userinfo" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Egnyte refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Egnyte access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Egnyte access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "egnyte",
    "services": [
      "egnyte"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "egnyte",    "services": [      "egnyte"    ],    "reconnectUrl": "https://…"  }}