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

Infisical Folders API

The Folders API from Infisical — 16 operation(s) for folders.

Infisical Folders API is one of 73 APIs that Infisical publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Folders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 24 operations across 16 paths. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against 3 base URLs: https://us.infisical.com, https://eu.infisical.com, http://localhost:8080.

24 operations 16 paths 0 schemas 4 DELETE10 GET6 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://app.infisical.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Infisical Folders API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — An access token in Infisical

Paths & Operations 24

Across 16 paths, the API surfaces 24 operations — 4 DELETE, 10 GET, 6 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Folders 24
POST
/api/v1/folders
Create api folders
postApiV1Folders body → 200400401403404422500
GET
/api/v1/folders
Get api folders
getApiV1Folders 6 params → 200400401403404422500
PATCH
/api/v1/folders/{folderId}
Update api folders by folder id
patchApiV1FoldersByFolderId 1 param body → 200400401403404422500
PATCH
/api/v1/folders/batch
Update api folders batch
patchApiV1FoldersBatch body → 200400401403404422500
DELETE
/api/v1/folders/{folderIdOrName}
Delete api folders by folder id or name
deleteApiV1FoldersByFolderIdOrName 1 param body → 200400401403404422500
GET
/api/v1/folders/{id}
Get api folders by id
getApiV1FoldersById 1 param → 200400401403404422500
GET
/api/v1/workspace/{projectId}/tags
Get api workspace by project id tags
getApiV1WorkspaceByProjectIdTags 1 param → 200400401403404422500
POST
/api/v1/workspace/{projectId}/tags
Create api workspace by project id tags
postApiV1WorkspaceByProjectIdTags 1 param body → 200400401403404422500
GET
/api/v1/workspace/{projectId}/tags/{tagId}
Get api workspace by project id tags by tag id
getApiV1WorkspaceByProjectIdTagsByTagId 2 params → 200400401403404422500
PATCH
/api/v1/workspace/{projectId}/tags/{tagId}
Update api workspace by project id tags by tag id
patchApiV1WorkspaceByProjectIdTagsByTagId 2 params body → 200400401403404422500
DELETE
/api/v1/workspace/{projectId}/tags/{tagId}
Delete api workspace by project id tags by tag id
deleteApiV1WorkspaceByProjectIdTagsByTagId 2 params → 200400401403404422500
GET
/api/v1/workspace/{projectId}/tags/slug/{tagSlug}
Get api workspace by project id tags slug by tag slug
getApiV1WorkspaceByProjectIdTagsSlugByTagSlug 2 params → 200400401403404422500
GET
/api/v1/projects/{projectId}/tags
List secret tags
listSecretTags 1 param → 200400401403404422500
POST
/api/v1/projects/{projectId}/tags
Create secret tag
createSecretTag 1 param body → 200400401403404422500
GET
/api/v1/projects/{projectId}/tags/{tagId}
Get secret tag by id
getSecretTagById 2 params → 200400401403404422500
PATCH
/api/v1/projects/{projectId}/tags/{tagId}
Update secret tag
updateSecretTag 2 params body → 200400401403404422500
DELETE
/api/v1/projects/{projectId}/tags/{tagId}
Delete secret tag
deleteSecretTag 2 params → 200400401403404422500
GET
/api/v1/projects/{projectId}/tags/slug/{tagSlug}
Get secret tag by slug
getSecretTagBySlug 2 params → 200400401403404422500
POST
/api/v2/folders
Create secret folder
createSecretFolder body → 200400401403404422500
GET
/api/v2/folders
List secret folders
listSecretFolders 5 params → 200400401403404422500
PATCH
/api/v2/folders/{folderId}
Update secret folder
updateSecretFolder 1 param body → 200400401403404422500
PATCH
/api/v2/folders/batch
Update secret folders batch
updateSecretFoldersBatch body → 200400401403404422500
DELETE
/api/v2/folders/{folderIdOrName}
Delete secret folder
deleteSecretFolder 1 param body → 200400401403404422500
GET
/api/v2/folders/{id}
Get secret folder by id
getSecretFolderById 1 param → 200400401403404422500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

infisical-folders-api-openapi.yml Raw ↑

Other APIs Infisical publishes across the network.

Infisical Admin API
Infisical Alibaba Cloud Auth API
Infisical App Connections API
Infisical Audit Logs API
Infisical AWS Auth API
Infisical Azure Auth API
Infisical Cert Manager API
Infisical Dynamic Secrets API
Infisical Environments API
Infisical Event Subscriptions API
Infisical GCP Auth API
Infisical Groups API
Where this information came from

This is an independent, third-party profile of Infisical Folders 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.