Developer API

Build custom integrations, automate workflows, and extend Orangescrum functionality using our REST APIs.

Overview

The Orangescrum Developer API allows developers to programmatically interact with Orangescrum data and features.

Using the API, you can:

  • Integrate Orangescrum with third-party applications
  • Automate project and task operations
  • Sync data between Orangescrum and external systems
  • Build custom dashboards, reports, or internal tools

The API is designed for secure, scalable, and flexible access to your Orangescrum workspace.

API Documentation

All technical details, endpoints, and examples are available in our official API documentation:

This documentation includes:

  • Authentication methods
  • Request & response formats
  • Endpoint references
  • Sample payloads
  • Error handling details

Developers should always refer to the documentation for the most up-to-date API specifications.

Supported API Capabilities

Using the Orangescrum API, you can work with the following core modules:

Projects

  • Create, update, and fetch projects
  • Access project status and metadata
  • Retrieve project lists for reporting or synchronization

Tasks

  • Create and manage tasks programmatically
  • Update task status, priority, and assignments
  • Fetch task details for automation or analytics

Users & Teams

  • Retrieve user details
  • Map users to projects and tasks
  • Enable external user synchronization

Time Tracking

  • Log time entries via API
  • Fetch timesheet data for billing or payroll systems
  • Generate time-based analytics

Reports & Data Access

  • Extract project and task data
  • Build custom reports or dashboards
  • Sync Orangescrum data with BI tools

Authentication & Security

The Orangescrum API uses secure authentication mechanisms to protect your workspace data.

  • API access is restricted to authorized users
  • Requests must include valid authentication credentials
  • All API communication is encrypted using SSL/TLS

Authentication details, including token usage and headers, are documented here:

Never expose API credentials in client-side code or public repositories.

Common Use Cases

The Developer API is commonly used for:

  • CRM, ERP, and accounting system integrations
  • Automated task creation from external apps
  • Syncing users, projects, and time logs
  • Building internal tools on top of Orangescrum
  • Custom workflow automation

The API enables Orangescrum to fit seamlessly into your existing tech stack.

Rate Limits & Best Practices

To ensure platform stability, API usage follows standard limits.

Best practices:

  • Cache responses wherever possible
  • Avoid excessive polling
  • Handle API errors gracefully
  • Use pagination for large data sets
  • Test integrations in a controlled environment before production use

Refer to the official documentation for rate limit guidelines and response codes.

Versioning

  • Current version: API v1
  • Backward compatibility is maintained within the same version
  • New features and improvements are released incrementally

Always use versioned endpoints as documented:

Troubleshooting

Issue Solution
Authentication failed Verify API credentials and headers
Invalid request error Check request payload format
Data not updating Confirm permissions and endpoint usage
Rate limit exceeded Reduce request frequency

For unresolved issues, review the API logs and documentation before contacting support.

Support

If you need help with API access or integration:

Summary

Capability Developer API Benefit
Integration Connect Orangescrum with external systems
Automation Reduce manual work through API-driven actions
Data Access Extract real-time project and task data
Scalability Build custom solutions on top of Orangescrum
Security Encrypted, authenticated API communication

The Orangescrum Developer API empowers teams to extend, automate, and integrate Orangescrum according to their business needs.

Troubleshooting

Even with a smooth installation, self-hosted environments can occasionally run into configuration conflicts, permission issues, or dependency mismatches.

This section helps system administrators quickly identify and resolve the most common issues that arise during installation, configuration, and daily operations of Orangescrum Self-Hosted.

Scaling

As your user base grows, Orangescrum can scale flexibly depending on the deployment model.

Vertical Scaling

Upgrade resources on a single host:

  • Increase CPU, RAM, and disk I/O
  • Move database to a dedicated instance
  • Use NVMe or SSD storage for faster query response

Example: Move from 4C/8GB to 8C/32GB to handle 3x user load.

Horizontal Scaling

Distribute load across multiple servers or containers:

  • Deploy multiple app nodes behind a load balancer (HAProxy or Nginx)
  • Use shared storage (NFS/GlusterFS) for uploads
  • Implement MySQL/PostgreSQL replication for database redundancy
  • Run Redis/Memcached for session caching if needed

Scaling in Kubernetes

If using K8s, simply scale pods:

kubectl scale deployment orangescrum –replicas=3 -n orangescrum

Tip: Monitor latency, concurrent sessions, and database performance as leading indicators for scaling decisions.

Summary

Maintaining Orangescrum Self-Hosted is about discipline and consistency:

  • Back up your database and upload regularly.
  • Restore carefully and test before going live.
  • Keep your system patched and Orangescrum version current.
  • Monitor logs proactively to prevent downtime.
  • Scale vertically or horizontally as your teams grow.

These practices ensure that your Orangescrum environment remains secure, resilient, and high-performing — ready for long-term enterprise adoption.

Log Management

Monitoring your Orangescrum instance helps detect issues early and maintain optimal performance.

Application Logs

Located at:

/app/tmp/logs/

Or inside the Docker container:

docker exec -it orangescrum-app tail -f /var/www/html/app/tmp/logs/error.log

Use these logs to troubleshoot errors related to tasks, authentication, or integrations.

Web Server Logs

Apache/Nginx logs are typically found at:

/var/log/apache2/access.log
/var/log/apache2/error.log

Monitoring Tools

For production-grade observability:

  • Prometheus + Grafana → CPU, memory, container metrics
  • Uptime Kuma / Nagios → Service uptime
  • Elastic Stack (ELK) → Centralized log analytics

Recommended Practice: Configure alerts for CPU >80%, memory >75%, or disk >90% utilization.

Upgrading Orangescrum Versions

Orangescrum frequently releases new updates for features, performance, and security. Keeping your instance up-to-date ensures you benefit from the latest improvements.

Before Upgrading

  1. Take a full backup of both database and uploads.
  2. Notify users and schedule downtime.
  3. Note your current version (Settings → About Orangescrum).

Upgrade Steps (Docker Method)

Pull the latest image:

docker pull orangescrum:latest

1. Stop existing containers:


docker compose down

2. Start new containers with updated image:


docker compose up -d –build

3. Verify the version from the web UI.

Upgrade Steps (Manual Installation)

  1. Backup /config and /uploads.
  2. Download the latest release from Orangescrum’s release page or your customer portal.
  3. Replace application files except /config and /webroot/uploads.
  4. Run database migration scripts if included.

Restart web services:


sudo systemctl restart apache2

Version Compatibility: Always check the release notes for required PHP or DB version changes before upgrading.

For enterprise users, staging upgrades are highly recommended.

Restore Procedures

Restoring from a backup is straightforward, but it must be executed carefully to avoid data mismatch or corruption.

Restore Database

MySQL:

mysql -u root -p yourorganization < /backup/yourorganization_backup.sql

PostgreSQL:

psql -U postgres yourorganization< /backup/yourorganization_backup.sql

Restore Files

tar -xzvf /backup/os_files_latest.tar.gz -C /var/www/yourorganization/app/webroot/uploads/

Restart your Orangescrum services or Docker containers afterward:

docker restart orangescrum-app

Pro Tip: Always restore backups in a staging environment first to verify data consistency before applying to production.