Folder Mapping API Reference
This page provides API reference documentation for the folder mapping functionality, which allows you to programmatically manage folder associations for logs objects.
|
Folder mapping requires the |
GraphQL Mutations
The folder mapping feature provides these GraphQL mutations for managing folder associations:
HTTP API Endpoints
Update Folder Mapping
Update the folder mapping for an existing logs object:
curl -X PATCH http://localhost:8083/folder-mappings \
-H "Content-Type: application/json" \
-H "X-Auth-Request-User: user@example.com" \
-d '{
"entityType": "favorite_facet",
"entityName": "response_time::performance",
"newFolderUid": "new-folder-uid"
}'
Remove Folder Mapping
Remove the folder mapping for a logs object (object becomes unmapped):
curl -X DELETE http://localhost:8083/folder-mappings \
-H "Content-Type: application/json" \
-H "X-Auth-Request-User: user@example.com" \
-d '{
"entityType": "favorite_facet",
"entityName": "response_time::performance"
}'
API Parameters
Common Parameters
| Parameter | Type | Description |
|---|---|---|
|
string |
Type of logs object ( |
|
string |
Unique identifier for the logs object |
|
string |
Unique identifier for the target folder |
|
string |
New folder UID when updating folder mappings |
Authentication
All API endpoints require proper authentication:
-
GraphQL: Use your standard GraphQL authentication method
-
HTTP APIs: Include the
X-Auth-Request-Userheader with a valid user identifier
Related Documentation
-
Folder Mapping for Logs Objects - User guide and concepts
-
Managing Folders - Core folder management
-
Role-Based Access Control - Understanding permissions