API Documentation

Comprehensive guide for EngOTSS API developers

Overview

EngOTSS API suite provides secure, enterprise-grade programmatic access to our cloud infrastructure. This reference covers authentication, endpoints, and usage limitations.

⚠️ Important

All API calls require valid bearer tokens. See the Authentication section for implementation details.

API Categories

Infrastructure Management

Control cloud resources, server clusters, and network configuration at scale.

/api/v2/infra

Security & Compliance

Auditing, access control, and data encryption management system integration.

/api/v2/sec

Data Analytics

Business intelligence and system metrics analysis across enterprise workloads.

/api/v2/analytics

Identity Management

User authentication, role-based access control, and SSO integration frameworks.

/api/v2/identity

AI/ML Services

Pretrained models and custom ML workflows for production deployment systems.

/api/v2/ai

DevOps Tools

CI/CD pipeline automation for infrastructure as services in hybrid environments.

/api/v2/ci

Authentication

All API requests must be authenticated using Bearer token in the Authorization header

Example

curl -X GET 'https://api.engotss.eu/v2/infra/status' \
  -H 'Authorization: Bearer YOUR_API_KEY'

Rate Limiting

Standard

1500

Requests/minute

Enterprise

25,000

Requests/minute

Burst

5000

Requests/second

Header responses: X-RateLimit-Remaining, X-RateLimit-Limit

API Versioning

All API endpoints use semantic versioning through URL paths. We ensure backward compatibility between patches and minor versions within a major release.

Stable

v2.12.3

2025-06-01

Beta

v3.0.0-alpha

2025-09-01

Feedback accepted

Code Examples


curl -X POST 'https://api.engotss.eu/v2/identity/users' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "username": "new_user",
    "role": "developer"
  }'
                

Contributing to the API Docs

All documentation is maintained in our public repository. Contributions welcome in the form of error fixes, code samples, and feature documentation updates.