Intralinks Content Connectors

Name: Intralinks Content Connectors API
Brand: Intralinks Content Connectors
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDocument Managementoauth225 EndpointsREST

For Agents

List, browse, and copy files from a user's connected cloud storage account into an Intralinks data room so an agent can stage deal documents without moving files out of their source system.

Quickstart

Get started with Intralinks Content Connectors in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"copy a file from cloud storage into Intralinks"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Intralinks Content Connectors API.

List the storage providers a user can link, such as the catalogue returned by GET /il-storage/providers

Create or update a per-user storage account connection through POST /il-storage/accounts and the OAuth flow on /il-storage/accounts/authorize/{providerId}

Browse a container's children and metadata using the cdmi_objectid or path-based object endpoints

Create new storage containers under a connected account using path-based POST operations

GET STARTED

Start building with Intralinks Content Connectors API

Explore with Jentic

View OpenAPI Document

Use for: I need to copy a contract from a user's storage account into an Intralinks data room, List the storage providers a user can connect through Intralinks Content Connectors, Set up a new user storage account using OAuth, Find all repositories available under an existing storage account

Not supported: Does not manage Intralinks workspace permissions, user provisioning, or deal-room reporting — use for connecting third-party storage and copying its content into Intralinks only.

Jentic publishes the only available OpenAPI document for Intralinks Content Connectors, keeping it validated and agent-ready.

The Intralinks Content Connectors API exposes Intralinks' bridge between user-owned cloud storage providers and Intralinks workspaces, so files held in third-party storage can be listed, fetched, and copied into a virtual data room (VDR) without leaving the source system. The API surfaces three layers — Storage Providers (the catalogue of supported services), Storage Accounts (per-user OAuth-linked connections), and Storage Content (containers and data objects accessible through those accounts) — together with a Copy operation that moves content into Intralinks. It is intended for due-diligence, M&A, and regulated dealmaking workflows where source-of-truth files live in user storage but must be shared inside a controlled VDR.

Use Cases

Patterns agents use Intralinks Content Connectors API for, with concrete tasks.

★ Stage Diligence Files into a Data Room

Stage diligence files from a deal team's existing cloud storage into an Intralinks workspace without asking team members to download and re-upload. The Content Connectors API lists the user's connected storage accounts, browses containers and objects, and copies selected items into Intralinks via the /il-connectors/copy endpoint. Users authorize each storage account once through the OAuth flow on /il-storage/accounts/authorize/{providerId}.

Call /il-storage/accounts to list the user's connected accounts, then GET /il-storage/accounts/{accountId}/objects/ to list root objects, and finally POST /il-connectors/copy to move the selected object into the target Intralinks workspace.

User Storage Account Onboarding

Walk a user through linking a third-party storage provider to Intralinks so they can later draw files from it into deals. The flow lists supported providers via GET /il-storage/providers, then either accepts credentials through POST /il-storage/accounts or initiates an OAuth handoff via POST /il-storage/accounts/authorize/{providerId}. Once linked, the account ID can be reused on later browse calls.

Call GET /il-storage/providers, present the returned list to the user, then call POST /il-storage/accounts/authorize/{providerId} to start the OAuth flow for the chosen provider.

Folder Browsing UI for Connected Storage

Build a folder-browsing UI for a connected storage account by paging through container objects with the GET endpoints on /il-storage/accounts/{accountId}/objects/{parentContainerPath}/ and /il-storage/accounts/{accountId}/cdmi_objectid/{objectId}/. The fields query parameter controls whether children, metadata, or both are returned, which keeps payloads small for nested folder views. New folders can be created with the matching POST operations.

Call GET /il-storage/accounts/{accountId}/objects/{parentContainerPath}/ with fields=children for the selected folder and render the returned ContainerObjectResponse as a folder listing.

Agent-Driven Deal File Move via Jentic

An AI deal-room agent uses Jentic to discover and call the Intralinks Content Connectors API to move a named contract from a user's connected storage into a target Intralinks workspace. The agent chains list, browse, and copy operations without hardcoding the Intralinks SDK. Through Jentic the OAuth credentials are held in the credential vault and never enter the agent context.

Use Jentic to search for 'copy a file from cloud storage into Intralinks', load /il-connectors/copy, and execute it with the source accountId and objectId together with the destination workspace identifier.

Key Endpoints

25 endpoints — the intralinks content connectors api exposes intralinks' bridge between user-owned cloud storage providers and intralinks workspaces, so files held in third-party storage can be listed, fetched, and copied into a virtual data room (vdr) without leaving the source system.

METHOD

PATH

DESCRIPTION

GET

/il-storage/providers

List storage providers a user can link

GET

/il-storage/accounts

List the current user's connected storage accounts

POST

/il-storage/accounts

Create a new storage account using supplied provider credentials

POST

/il-storage/accounts/authorize/{providerId}

Initiate the OAuth flow for a storage provider

GET

/il-storage/accounts/{accountId}/objects/

List root-level objects in a connected storage account

GET

/il-storage/accounts/{accountId}/cdmi_objectid/{objectId}/

Retrieve a container or object by its CDMI object id

POST

/il-connectors/copy

Copy a selected storage object into an Intralinks workspace

GET

/il-storage/providers

List storage providers a user can link

GET

/il-storage/accounts

List the current user's connected storage accounts

POST

/il-storage/accounts

Create a new storage account using supplied provider credentials

POST

/il-storage/accounts/authorize/{providerId}

Initiate the OAuth flow for a storage provider

GET

/il-storage/accounts/{accountId}/objects/

List root-level objects in a connected storage account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OAuth 2.0 access tokens for `ilAuthCode` and any underlying storage provider tokens are held encrypted in the Jentic vault. Agents receive scoped access at execution time and raw tokens never enter the agent context or logs.

Intent-based discovery

Agents search Jentic with an intent like 'copy a file from cloud storage into Intralinks' and receive the matching /il-connectors/copy or /il-storage/accounts/{accountId}/objects operations with their input schemas.

Time to first call

Direct integration with Intralinks Content Connectors: 1-2 days for OAuth wiring, CDMI semantics, and error handling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Box Content API

Source-side cloud storage commonly linked as a provider in Intralinks Content Connectors.

Choose Box directly when the workflow only needs to manipulate files inside Box without staging them into an Intralinks data room.

Complementary

Dropbox API v2

Another commonly linked storage provider for diligence files staged into Intralinks.

Choose Dropbox directly when the source workflow does not require an Intralinks data room destination.

Alternative

Box Content API

Direct cloud-storage and document-collaboration platform used as a standalone alternative to a VDR.

Choose Box directly when a controlled-access shared workspace is sufficient and an Intralinks-grade VDR is not required.

FAQs

Specific to using Intralinks Content Connectors API through Jentic.

What authentication does the Intralinks Content Connectors API use?

Every operation in the spec is secured by the `ilAuthCode` OAuth 2.0 scheme with the `ilservices` scope. Through Jentic the OAuth tokens are held in the credential vault and injected at execution time, so raw access tokens never enter the agent context.

Can I copy files from a connected storage account into Intralinks with this API?

Yes. Once a storage account is linked, /il-connectors/copy accepts a source object reference and a destination Intralinks workspace identifier and performs the copy server-side. There is no need to download the file to the agent first.

What are the rate limits for the Intralinks Content Connectors API?

The OpenAPI spec does not declare numeric rate limits. Practical throughput depends on the underlying storage provider and the Intralinks tenant configuration. Refer to your Intralinks account team for production limits.

How do I browse a connected storage account through Jentic?

Install the SDK with `pip install jentic`, search for 'browse files in a connected Intralinks storage account', load /il-storage/accounts/{accountId}/objects/{parentContainerPath}/, and execute it with the path of the folder to list. The fields query parameter controls whether children, metadata, or both are returned.

How do I create a new folder in a connected storage account?

Use the path-based POST on /il-storage/accounts/{accountId}/objects/{parentContainerPath}/ or the CDMI-id-based POST on /il-storage/accounts/{accountId}/cdmi_objectid/{objectId}/. The Content-Type must be `application/cdmi-container`. The response is a ContainerObjectNoMetadataResponse describing the new folder.

Does the API expose individual file uploads?

The spec exposes container and data-object endpoints under /il-storage/accounts/{accountId}/cdmi_objectid/{objectId}/ and the path-based variants. End-to-end content upload semantics depend on the underlying storage provider; this API is primarily a connector to existing storage rather than a full upload pipeline.