---
title: "Create flight authorization from flight plan"
method: POST
path: "/flight-auths"
tags: ["flight-authorization"]
---

# Create flight authorization from flight plan

`POST /flight-auths`

## Request

- Base URL: `http://localhost:8486`
- URL: `http://localhost:8486/flight-auths`
- Auth: API key in header `x-auth-token`

Creates a new flight authorization from a ready flight plan JSON file

## Request body `multipart/form-data`

- object
  - `flightAuthorization` CreateFlightAuthorizationRequestDTO, required: Flight authorization data as JSON string
    - `shortName` string, required: Short name for the flight authorization
    - `timeStart` string, date-time, required: Flight start time in ISO-8601 format
    - `timeEnd` string, date-time, required: Flight end time in ISO-8601 format
    - `category` 'OPEN_CATEGORY_A1' | 'OPEN_CATEGORY_A2' | 'OPEN_CATEGORY_A3' | 'SPECIFIC_CATEGORY' | 'CERTIFIED_CATEGORY', required: Category of the flight authorization
    - `pilotId` integer, required: ID of the pilot
    - `client` string, required: Client name
    - `droneId` integer, required: ID of the drone
    - `organizationId` integer: Organization ID. Required for Super Admin; ignored for users creating within their own organization
    - `droneWeight` number, double, required: Drone weight in kg
    - `droneSpeed` number, double: Drone speed in m/s
    - `missionDescription` string, required: Mission description
    - `processingType` 'SEGMENTS' | 'CIRCLE' | 'CUSTOM_CIRCLE' | 'CUSTOM_POLYGON': Processing type for the flight
  - `importingFile` string, binary, required: Flight plan JSON file

## Response `201`

Flight authorization created successfully

- CreateFlightAuthResponseDTO
  - `id` string

## Other responses

- `400`: Error in parsing request or flight plan conflicts detected
- `401`: Authentication required
- `403`: Authorization denied
- `404`: Resource not found
- `409`: Flight authorization collision or lock acquisition failed
- `422`: Validation error - Invalid JSON, missing drone/pilot, or parsing errors
- `451`: Terrain data unavailable - Coordinates outside HREF coverage area

---

[API](https://skmtc.dev/airdodge/apis/api-core.md) - [All operations](https://skmtc.dev/airdodge/apis/api-core/llms.txt) - [OpenAPI document](https://skmtc.dev/airdodge/apis/api-core/revisions/fb3c5a1055cc?raw)