How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Conga File Store API

The File Store API from Conga — 17 operation(s) for file store.

Conga File Store API is one of 347 APIs that Conga publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include File Store. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 20 operations across 17 paths, and defines 45 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://rls.congacloud.com.

20 operations 17 paths 45 schemas 5 DELETE7 GET7 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://rls.congacloud.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Conga File Store API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

  • Bearer — Please insert JWT with Bearer into field

Paths & Operations 20

Across 17 paths, the API surfaces 20 operations — 5 DELETE, 7 GET, 7 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

File Store 20
DELETE
/api/filestore/v1/files
Delete a file from the file store
body → 200400403404500503
DELETE
/api/filestore/v1/files/bulk
Delete multiple files from the file store
body → 200400403404500503
POST
/api/filestore/v1/files/bulk
Upload multiple files
body → 200400403404500503
GET
/api/filestore/v1/files/limits
Retrieve file size limitation information
→ 200400403404500503
DELETE
/api/filestore/v1/files/multipart-uploads
Abort an incomplete multipart upload process
body → 200400403404500503
POST
/api/filestore/v1/files/multipart-uploads
Initiate a multipart upload process for a large file
body → 200400403404500503
PUT
/api/filestore/v1/files/multipart-uploads
Upload a single part of a large file in a multipart upload process
4 params → 200400403404500503
POST
/api/filestore/v1/files/multipart-uploads/complete
Complete a multipart upload process by combining all uploaded parts into the final file
body → 200400403404500503
POST
/api/filestore/v1/files/shareduri
Provide time-based public access to a file
body → 200400403404500503
GET
/api/filestore/v1/files/{filePath}/download
Download multiple files as a ZIP archive
2 params → 200400403404500503
GET
/api/filestore/v1/files/{filePath}/filenames/list
Get list of file names
4 params → 200400403404500503
GET
/api/filestore/v1/files/{filePath}/{fileName}/download
Download a file using the specified file path and file name
2 params → 200400403404500503
GET
/api/filestore/v1/files/{filePath}/{fileName}/exists
Check if a file exists in the file store
2 params → 200400403404500503
GET
/api/filestore/v1/files/{filePath}/{fileName}/info
Retrieve detailed information about a specific file in the file store
2 params → 200400403404500503
POST
/api/filestore/v1/files/{filePath}/{fileName}/upload
Upload a file to the file store with specified metadata and settings
2 params body → 200400403404500503
GET
/api/filestore/v1/folder-operation/{trackingId}/status
Get status of a folder operation by tracking ID
1 param → 200400403404500503
DELETE
/api/filestore/v1/folders
Delete all files in a specified folder location
body → 200400403404500503
POST
/api/filestore/v1/folders/create
Create a new folder in the file store at the specified path
body → 200400403404500503
DELETE
/api/filestore/v1/folders/delete
Delete the contents of a specified folder in the file store
body → 200400403404500503
POST
/api/filestore/v1/folders/{folderName}/list
Get all contents of a given folder
1 param body → 200400403404500503

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are FolderOperationTrackingInfoResponse (10 properties), GetFileNamesResponseAPIResponse (10 properties), CreateFileResponseListAPIResponse (10 properties), CreateFileResponseAPIResponse (10 properties). Each schema is shown below with its type and property counts.

FileUploadPartResponse
object
2 properties
FileInitiateMultipartUploadResponseAPIResponse
object
10 properties
Stream
object
8 properties
FileInfoAPIResponse
object
10 properties
BulkDeleteFileRequest
object
2 properties
GetFileNamesResponse
object
3 properties
CreateFolderResponse
object
2 properties
FileSharedURIRequest
object
3 properties
FileLimits
object
2 properties
DeleteFileResponse
object
3 properties
CreateFolderRequest
object
2 properties
GetFileResponse
object
5 properties
FolderContentInfo
object
4 properties
FolderOperationTrackingInfoResponse
object
10 properties
DeleteFileRequest
object
2 properties
GetFileNamesResponseAPIResponse
object
10 properties
CreateFileResponseListAPIResponse
object
10 properties
GetFolderContentsResponse
object
5 properties
DeleteFolderContentsResponse
object
4 properties
FileUploadPartResponseAPIResponse
object
10 properties
BulkCreateFileRequest
object
2 properties
CreateFolderResponseAPIResponse
object
10 properties
GetFolderContentsRequest
object
3 properties
GetFolderContentsResponseAPIResponse
object
10 properties
DeleteFolderContentsRequest
object
2 properties
CreateFileResponseAPIResponse
object
10 properties
FileExpirationRequest
object
2 properties
BaseCreateRequest
object
6 properties
FileAbortMultipartUploadRequest
object
3 properties
ErrorDetail
object
1 property
DeleteFolderContentsResponseAPIResponse
object
10 properties
FileCompleteMultipartUploadRequest
object
5 properties
StringAPIResponse
object
10 properties
FileLimitsAPIResponse
object
10 properties
FolderOperationTrackingInfoResponseAPIResponse
object
10 properties
FileSharedURIResponseAPIResponse
object
10 properties
CreateFileResponse
object
3 properties
FileInitiateMultipartUploadResponse
object
3 properties
FileCreateSharedURIRequest
object
4 properties
FileInitiateMultipartUploadRequest
object
4 properties
DeleteFileResponseAPIResponse
object
10 properties
GetFileResponseAPIResponse
object
10 properties
FileInfo
object
6 properties
BooleanNullableAPIResponse
object
10 properties
FileSharedURIResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

conga-file-store-api-openapi.yml Raw ↑

Other APIs Conga publishes across the network.

Conga Advantage Platform MCP Server
Conga GraphQL API
Conga 2. Order Actions API
Conga 3. Order Line Items API
Conga Account API
Conga Account Attachments Blacklist API
Conga Account Attachments Whitelist API
Conga Account Designer Settings API
Conga Account Email Reminder Settings API
Conga Account Feature Settings API
Conga Account Package Settings API
Conga Account Roles API
Where this information came from

This is an independent, third-party profile of Conga File Store API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.