> For the complete documentation index, see [llms.txt](https://documentation.hak5.org/wifi-pineapple-pager/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.hak5.org/wifi-pineapple-pager/wifi-pineapple-commands/wigle.md).
# WIGLE
`WIGLE_LOGIN` - log into a [Wigle](https://wigle.net/) account and obtain an API key
`WIGLE_LOGOUT` - delete any saved API keys
`WIGLE_UPLOAD` - upload Wigle csv logs to the Wigle service
`WIGLE_START` - Start a new log file
`WIGLE_STOP` - Stop logging
### When to use them
[Wigle](https://wigle.net/) is a service for collecting wardriving logs. Coupled with a [GPS](https://docs.hak5.org/wifi-pineapple-pager/device/gps/), the Pager can generate Wigle-compatible logs, and with a network connection with Internet access, upload them directly to the Wigle service.
{% hint style="info" %}
Please remember: Hak5 is not officially affiliated with Wigle. Accounts you create and information you share with Wigle are subject to the [Wigle End User Agreement](https://wigle.net/eula.html). The WiFi Pineapple Pager will never automatically interact with Wigle - even when creating a Wigle log file - unless you log into a Wigle account and choose to upload using the DuckyScript commands or a payload.
{% endhint %}
### Syntax
```none
WIGLE_LOGIN {username} {password}
```
**username (optional)**
An existing Wigle username
**password (optional)**
Password for the Wigle user
If a username and password are not provided as command line arguments, then `WIGLE_LOGIN` will offer an interactive login where the user is prompted to enter the username and password.
Interactive mode is typically not appropriate for use in payloads.
The API key of the login is saved to the payload config.
```none
WIGLE_LOGOUT
```
Delete any saved API keys, logging out of the Wigle service.
```none
WIGLE_UPLOAD {--archive} {--remove} [path to file] ... [path to fileN]
```
**–archive**
If `--archive` is used, `WIGLE_UPLOAD` will automatically move the file to the loot archive (`/root/loot/archive/wigle/`) directory after uploading.
**–remove**
If `--remove` is used, `WIGLE_UPLOAD` will automatically remove the file after uploading.
**path-to-file**
One or more files to upload; use the complete path (such as `/root/loot/wigle/*` to upload all files in the Wigle loot directory).
```none
WIGLE_START
```
Start a Wigle log, or start a new Wigle log if logging is already enabled.
```none
WIGLE_STOP
```
Stop and close a Wigle log
### Results
The `LOGIN` and `UPLOAD` commands require an active Internet connection to interact with the online service, and will return an error if one is not available.
The `WIGLE_LOGIN` command will return an error if there is an issue logging in using the supplied username or password.
`WIGLE_START` returns the name of the Wigle log file created.
A Wigle log may be created without a physical GPS receiver, or without a valid GPS position lock, however it will remain empty until a GPS position is found.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.hak5.org/wifi-pineapple-pager/wifi-pineapple-commands/wigle.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.