Testing with Postman
ImportingAccessing the Postman CollectionWorkspace
To get started with testing the SafeSky UAV API, followyou thesecan stepsaccess toour importfully the providedconfigured Postman Collection:workspace with pre-built requests and authentication:
-
Open Postman: LaunchAccess the Workspace:- Visit the SafeSky UAV API Postman
application.Workspace - Click Fork Collection to add it to your own Postman workspace
- Visit the SafeSky UAV API Postman
-
ImportWhat'sthe CollectionIncluded:ClickPre-configuredonAPItherequestsImportwithbuttonHMAC-SHA256in the top left corner of Postman.authenticationPasteAutomaticthesignaturefollowinggenerationURLusingpostmam_collection.jsonpre-request scripts- Sample request bodies and
clickqueryContinueparameters - Environment
completevariablestheforimport.easy configuration
to
Setting Up AuthorizationYour Environment
ToAfter useforking the SafeSky API, you'll need tocollection, configure your APIenvironment key:variables:
-
OpenSelect theImported CollectionEnvironment:Locate- In the top-right corner of Postman, click on the environment dropdown
- Select SafeSky UAV API - Sandbox
collection(orthatcreateyouaimported.new environment)
-
SetConfigureAuthorizationEnvironment Variables:- Click
onthethreeeyedotsicon (👁️) next to thecollectionenvironmentnamedropdown,andthenchooseclick Edit. Go toSet theAuthorizationfollowingtab.variables:Verify
thattheTypeisVariable setInitial toValueCurrent Value APIserverKeyhttps://sandbox-public-api.safesky.app.Enterhttps://sandbox-public-api.safesky.appthefollowing:ss-api-key(leave empty) <your_api_key>KeyImportant: Setx-ss-api-key- as a
Valuesecret:type<your_api_key>(replacevariableto<your_api_key>withkeepthe actualyour API key secure - The
Initial Valuewill be empty when youreceived).share
Current Valuecontains your personal API key - Click
- Click Save
. -
Verify Environment Selection:
- Ensure the correct environment is selected in the top-right corner of Postman
- The environment name should be visible (e.g., "SafeSky UAV API - Sandbox")
Understanding the Authentication
The collection includes a pre-request script that automatically:
- Generates the required HMAC-SHA256 signature for each request
- Sets authentication headers (
Authorization,X-SS-Date,X-SS-Nonce,X-SS-Alg) - Handles timestamp generation for request bodies
- Resolves environment variables in the canonical request
You don't need to manually configure authentication - just ensure your ss-api-key environment variable is set correctly.
Start Testing
Once the collectionenvironment is importedconfigured:
- Select a Request: Choose any request from the collection (e.g.,
POST multiple UAV light - return traffic) - Review the Request: Check the request body and query parameters
- Send the
authorizationRequest: Click Send - View the Response: The API will return nearby aircraft traffic based on your UAV positions
Available Endpoints
The collection includes the following pre-configured requests:
- POST /v1/uav: Submit single or multiple UAV positions and retrieve nearby traffic
- GET /health: Check API health status
- Additional endpoints for various use cases
Troubleshooting
If you encounter authentication errors:
- Verify your
ss-api-keyis correctly setup, you can start sending requests to the SafeSky API. Each requestin thecollectionenvironment - Ensure the correct environment is
pre-configuredselectedwithinsampletheteststop-right corner - Check that
servervariable points tohelphttps://sandbox-public-api.safesky.app - Review
getthestartedPostmaneasily.console for detailed error messages