### GET /data/exports/scenery

Source: https://vamsys.co.uk/docs/data-operations/scenery-import-export

Downloads all existing airport scenery recommendations as a CSV file.

```APIDOC
## GET /data/exports/scenery

### Description
Downloads the current scenery configuration for your airline in CSV format for editing or auditing.

### Method
GET

### Endpoint
/data/exports/scenery

### Response
#### Success Response (200)
- **Content-Type** (text/csv) - CSV file containing all scenery records including internal info columns.
```

--------------------------------

### Custom CSS Implementation for vAMSYS

Source: https://vamsys.co.uk/docs/orwell/branding

Example of how to structure a custom CSS file to override default vAMSYS styles. This snippet demonstrates targeting specific UI elements for colour customisation.

```css
/* Example of overriding vAMSYS theme variables */
:root {
  --primary-color: #0056b3;
  --body-background: #f4f4f4;
}

/* Targeting specific elements */
.navbar {
  background-color: var(--primary-color) !important;
}

body {
  background-color: var(--body-background);
  color: #333;
}
```

--------------------------------

### Engine Scoring Rules - Sequence

Source: https://vamsys.co.uk/docs/orwell/scoring-rules

Rules for evaluating the correct sequence of engine starts.

```APIDOC
## Engine Scoring Rules — Sequence

### Description
Engine sequence rules check that engines were started in the correct order. Pick the most applicable sequence for the fleets using the scoring group. Only one engine sequence rule can be added per scoring group.

### Method
N/A (Configuration within a Scoring Group)

### Endpoint
N/A

### Parameters
#### Request Body
- **Time between engine starts** (string HH:MM:SS) - Required - Minimum time that must elapse between each engine start.
- **Points** (integer) - Required - Base points awarded if the sequence is correct.
- **Penalise Out of Sequence** (boolean) - Optional - If enabled, deducts points when engines are started in the wrong order.
  - **Name** (string) - Required if Penalise Out of Sequence is enabled - How the penalty shows in the scorer.
  - **Points** (integer) - Required if Penalise Out of Sequence is enabled - Penalty points (negative).
- **Penalise Insufficient Time** (boolean) - Optional - If enabled, deducts points when the time between starts is too short.
  - **Name** (string) - Required if Penalise Insufficient Time is enabled - How the penalty shows in the scorer.
  - **Points** (integer) - Required if Penalise Insufficient Time is enabled - Penalty points (negative).

### Available Engine Start Sequences

- **Any Engine Started**: Any engine (base rule)
- **Number 1 First of 2**: 1 → 2
- **Number 2 First of 2**: 2 → 1
- **Number 1 First, Then 2**: 1 → 2
- **Number 1, Then 2, Then 3**: 1 → 2 → 3
- **Number 1, Then 2, Then 3, Then 4**: 1 → 2 → 3 → 4
- **Number 1, Then 2, Then 4, Then 3**: 1 → 2 → 4 → 3
- **Number 1, Then 3, Then 2**: 1 → 3 → 2
- **Number 2 First, Then 3 Dual**: 2 → 3 (dual spool)
- **Number 2, Then 3, Then 1, Then 4**: 2 → 3 → 1 → 4
- **Number 3 First of 3**: 3 → (others)
- **Number 3, Then 1, Then 2**: 3 → 1 → 2
- **Number 3, Then 2, Then 1**: 3 → 2 → 1
- **Number 3, Then 4**: 3 → 4
- **Number 3, Then 4, Then 2, Then 1**: 3 → 4 → 2 → 1
- **Number 4, Then 2, Then 1, Then 3**: 4 → 2 → 1 → 3
- **Number 4 First, Then 3**: 4 → 3
- **Number 4 First, Then 3 Dual**: 4 → 3 (dual spool)
- **Number 4, Then 3, Then 2, Then 1**: 4 → 3 → 2 → 1

### Request Example
```json
{
  "ruleType": "EngineSequence",
  "name": "Correct Engine Start Order",
  "uiName": "Engine Sequence",
  "timeBetweenEngineStarts": "00:01:30",
  "points": 100,
  "penaliseOutOfSequence": true,
  "penaliseOutOfSequenceName": "Incorrect Engine Start Order",
  "penaliseOutOfSequencePoints": -50,
  "penaliseInsufficientTime": true,
  "penaliseInsufficientTimeName": "Engine Start Too Fast",
  "penaliseInsufficientTimePoints": -25,
  "engineStartSequence": "1,2,3,4"
}
```

### Response
#### Success Response (200)
- **Rule Configuration**: Details of the configured rule.

#### Response Example
```json
{
  "ruleType": "EngineSequence",
  "name": "Correct Engine Start Order",
  "uiName": "Engine Sequence",
  "timeBetweenEngineStarts": "00:01:30",
  "points": 100,
  "penaliseOutOfSequence": true,
  "penaliseOutOfSequenceName": "Incorrect Engine Start Order",
  "penaliseOutOfSequencePoints": -50,
  "penaliseInsufficientTime": true,
  "penaliseInsufficientTimeName": "Engine Start Too Fast",
  "penaliseInsufficientTimePoints": -25,
  "engineStartSequence": "1,2,3,4"
}
```
```

--------------------------------

### POST /data/imports/scenery

Source: https://vamsys.co.uk/docs/data-operations/scenery-import-export

Uploads a CSV file to bulk create or update airport scenery recommendations.

```APIDOC
## POST /data/imports/scenery

### Description
Uploads a CSV file to bulk manage scenery entries. The system identifies existing entries by the combination of airport, type, simulator, and developer.

### Method
POST

### Endpoint
/data/imports/scenery

### Parameters
#### Request Body (CSV Format)
- **ICAO/IATA** (string) - Required - Airport code configured in your airline.
- **Type** (string) - Required - Scenery type (e.g., "Freeware", "Payware").
- **Simulator** (string) - Required - Simulator name (e.g., "MSFS 2020").
- **URL** (string) - Required - Valid link to the scenery package.
- **Developer** (string) - Required - Developer or publisher name.
- **_delete** (boolean) - Required - Set to TRUE to delete the entry, FALSE to create or update.

### Request Example
ICAO/IATA,Type,Simulator,URL,Developer,_delete
EGLL,Freeware,MSFS 2020,https://example.com/scenery,DeveloperName,FALSE

### Response
#### Success Response (200)
- **status** (string) - Confirmation of import processing.
```

--------------------------------

### GET /data/exports

Source: https://vamsys.co.uk/docs/data-operations/route-import-export

Exports existing flight routes based on specified filters such as status, airport, and tags.

```APIDOC
## GET /data/exports

### Description
Downloads a CSV file containing flight routes filtered by the provided criteria.

### Method
GET

### Endpoint
/data/exports

### Parameters
#### Query Parameters
- **route_status** (string) - Optional - Filter by: All, Active, or Future
- **missing_routings** (string) - Optional - Filter by: All, Empty, or Full
- **departure_airport** (string) - Optional - ICAO/IATA code
- **arrival_airport** (string) - Optional - ICAO/IATA code
- **tags** (string) - Optional - Comma-separated tags

### Response
#### Success Response (200)
- **Content-Type** (text/csv) - CSV file containing route data
```