Overview
The General Configuration API manages system-wide settings and organization-specific configurations that don’t fit into forest-specific categories.This section is reserved for future configuration endpoints such as system preferences, notification settings, and organization-level defaults.
Organization Settings
GET /api/config/organization
Retrieve organization-level settings.
Authentication: RequiredPermissions: User must belong to the organization
Response
Organization UUID
Organization name
Organization code
Organization-specific settings (JSON object)
Whether the organization is active
Example: Get Organization Settings
cURL
Response
User Preferences
GET /api/config/user/preferences
Retrieve current user’s preferences.
Authentication: Required
Response
User UUID
User preference settings:
language: Preferred language codetheme: UI theme preferencenotifications: Notification settings
PATCH /api/config/user/preferences
Update current user’s preferences.
Authentication: Required
Request Body
Preferred language:
es, en, etc.UI theme:
light, dark, autoNotification preferences:
email: Enable/disable email notificationsinApp: Enable/disable in-app notifications
System Configuration (Admin Only)
GET /api/config/system
Retrieve system-wide configuration.
Authentication: RequiredPermissions:
SUPER_ADMIN role only
Response
Application version
Environment:
production, staging, developmentFeature flags for enabled/disabled functionality
Maintenance mode settings:
enabled: Whether maintenance mode is activemessage: Message to display during maintenancescheduledEnd: Estimated end time
Configuration Best Practices
Future Configuration Endpoints
The following endpoints are planned for future releases:-
Notification Templates (
/api/config/notifications)- Manage email and in-app notification templates
- Customize messaging for different event types
-
Report Templates (
/api/config/reports)- Define custom report layouts and data sources
- Schedule automated report generation
-
Integration Settings (
/api/config/integrations)- Configure third-party integrations (GIS providers, accounting systems)
- Manage API keys and connection settings
-
Workflow Rules (
/api/config/workflows)- Define approval workflows for patrimony changes
- Set up automated triggers and notifications
Suggest additional configuration needs by contacting the CONFOR development team.
Related Endpoints
- Forest Configuration - Forest-specific reference data
- User Management - User account and role management