Export Jobs: Setup
A step-by-step guide to setting up automatic data exports - Catalog, Measurements, Pan42, or Meters - over HTTPS, SFTP, or FTPS.
Written by Shir Goldstein
Updated at May 12th, 2026
Table of Contents
PowerRadar's Auto-Export feature lets you schedule automatic exports of your account's data to a destination of your choice - over HTTPS, SFTP, or FTPS.
This article walks you through the Export jobs list, how to create a new export job, and how to pick the right data transfer method.
What Is Auto-Export?
Auto-Export is a scheduled job runner that pulls data from your PowerRadar account and delivers it to a destination you control. You can use it to feed BI tools, ERP systems, or any third-party application that consumes your energy data.
The service supports four data types (Catalog, Measurements, Pan42 Measurements, Meters Measurements), three transfer protocols (JSON over HTTPS, CSV over SFTP, CSV over FTPS), and a range of frequencies and resolutions.
Where to Find It
In the sidebar, open the Account Dashboard and click Auto-Export. The Export jobs list opens.
The Export Jobs List
The Export jobs screen shows every export job configured on your account.
The list includes the following columns:
- Name - the job's display name.
- Enabled - whether the job is currently active. Disabled jobs show a grey "X" icon next to the name.
- Category - the data type: Catalog, Measurements, Pan42 Measurements, or Meters Measurements.
- Frequency - how often the job runs.
- Resolution - the granularity of each measurement record.
- Format - the transfer method: JSON over HTTPS, CSV over SFTP, or CSV over FTPS.
- Sites - the sites included in the export.
- HTTP URL - the destination URL, for HTTPS jobs only.
- Last Run - the date and time of the most recent run.
From the list, you can:
- Search by job name using the search bar at the top.
- Refresh the list using the circular arrow icon.
- Download the full list as a CSV file using the CSV button. The download includes extra columns not shown on screen: HTTP Method, Catalog Version, Zero Pad Gaps, Job ID, Account ID, Last Run Status, Status Reason, and Exit Message.
- Open the row menu (three dots on the right of any row) to Enable Job, Disable Job, or Delete Job.
Creating a New Export Job
From the Export jobs list, click Create New Export Job in the top right. The New export job page opens.
The right side of the page is a live Data sample preview. As you change settings, the preview updates so you can see exactly what the export will contain before you save.
1. Job Name
Enter a descriptive name in the Job name field. The name appears in the Export jobs list and in any failure notifications, so use something you'll recognize later.
2. Data to Export
Choose what type of data the job exports:
- Catalog - Metadata describing the user data and the topology of the electrical network.
- Measurements - Device level readings measured by Panoramic Power sensors.
- Pan42 Measurements - Actual PAN-42 power meters readings.
- Meters Measurements - Meters readings measured through loggers or bridges.
3. Sites for Data Export
Choose which sites the job covers:
- Toggle All sites on to include every site in the account.
- Toggle it off to pick specific sites from the dropdown.
4. Export Frequency and Data Resolution
- Export frequency - how often the job runs. Options: Every day, Every hour, Every 15 minutes, Every 5 minutes.
- Data resolution - the granularity of each measurement record. Options: 5 min, 15 min, 1 hour.
The available resolution options depend on the frequency you select.
Note: When Catalog is selected as the data type, Export frequency is locked to Every day, and a Version field appears in place of Data resolution:
- v1.0 - Includes data of sites and devices under a specific site.
- v1.1 - Includes account-level data, sites, and devices under a specific site.
5. Zero Pad Measurement Gaps
Tick the Zero pad measurement gaps checkbox to fill missing intervals with zeros instead of leaving them as gaps. This produces a continuous timeline at the chosen resolution, which is useful when downstream tools expect evenly spaced records.
Leave it unchecked to keep gaps in the data wherever measurements are missing.
6. Data Transfer Method
Pick how the file is delivered. Three methods are available:
- JSON over HTTPS - Recommended. Most reliable data transfer option.
- CSV over SFTP - Best FTP protocol. File transfer to your own server or system.
- CSV over FTPS - Old FTP protocol.
Each method has its own configuration fields and a How it works? panel below the cards. See Choosing a Data Transfer Method below for the details of each.
7. Apply
Click Apply at the bottom right to save the job. The same button is used when editing an existing job.
Choosing a Data Transfer Method
JSON over HTTPS
Selecting JSON over HTTPS sends the export as a JSON payload to a URL you control.
Configure:
- HTTPS Method - choose POST, PUT, or POST Multipart.
- HTTPS URL - the URL of your service.
The How it works? panel summarizes what to expect:
- We format your data as JSON and send it over to your designated URL.
- Configure your server to accept a minimum 1MB payload size and return HTTP 200 OK on success.
- Failed deliveries will be included in the next scheduled export and retried for up to one week.
Note: Large exports (over 2,000 measurements) are split into multiple transactions. Each transaction must return a successful response on its own.
Outbound IPs to whitelist. To receive JSON over HTTPS deliveries, allow inbound traffic from these two PowerRadar outbound IPs:
34.237.64.14354.205.225.22
These IPs are stable across all environments and apply globally.
CSV over SFTP
Selecting CSV over SFTP sends the export to a secure SFTP folder hosted by Panoramic Power.
The form shows the SFTP destination folder for your account — for example, ftp.panpwrws.com:22/Measurements — with a copy button next to it.
The How it works? panel summarizes the flow:
- We'll set up a dedicated, secure SFTP folder hosted by us for your exported data.
- Get your SFTP username and password from our Support team.
- Access your data securely using any FTP explorer or using the provided SFTP link.
Toggle Enable to activate the job once your credentials are in place.
Before you connect:
- Credentials are issued by Support. Submit a support ticket to request your SFTP username and password. The same credentials work for both SFTP and FTPS — you don't need to request them twice.
- Firewall configuration. SFTP runs on Port 22 (control channel) and port range 8192–8200 (data channel). Add an outbound firewall rule for these ports.
- Transfer mode. AWS Transfer Family supports binary mode only — ASCII is not supported.
For full setup steps, see the SFTP and FTPs Server Connection Checklist.
CSV over FTPS
Selecting CSV over FTPS sends the export to a secure FTPS folder. The flow is the same as SFTP, with these differences:
-
FTPS destination folder uses port 21 — for example,
ftp.panpwrws.com:21/Measurements. - The same Support-issued credentials are used. If you already have SFTP credentials, no new request is needed.
SFTP vs. FTPS
If you're not sure which protocol to use, the table below compares them.
| Parameter | Secure shell file transfer protocol (SFTP) | File transfer protocol secure (FTPS) |
|---|---|---|
| Network communication approach | SFTP builds on secure shell protocol (SSH) and adds on file transfer capabilities. | FTPS builds on file transfer protocol (FTP) and adds on a security and encryption layer. |
| Firewall support | It uses a single connection through only one port, making it easier to install firewall solutions. | It needs a secondary data connection, and its use of multiple ports makes it difficult for firewalls to work. |
| Transfer speeds | It involves a high resource overhead and slows down file delivery. | It is simple, straightforward, and lean, making it several times faster. |
| Binary and ASCII | It supports only binary transmission, and users cannot choose between different modes. | It supports both binary and ASCII transmissions, making it easier to maintain logs. |
| .NET compatibility | Developers cannot build .NET programs with SFTP functionalities, as compatibility is missing. | .NET includes a number of commands to support file uploads in FTPS modes. |
| Authentication mechanism | It uses out-of-band authentication and does not need signed certificates, as the data is inherently encrypted. | The FTP server must mandatorily provide a public-key certificate to sign off on the authentication. |
| Usage commands | It supports a long list of commands with granular controls, such as defining file permissions. | It supports a relatively limited list of commands, with less control over remote files and directories. |
| Adoption | It is widely adopted, and most servers and cloud storage solutions support SFTP. | It is built on FTP, which is gradually being phased out for HTTPS and other protocols. |
Note: At times, our system sends multiple entries for the same timestamp, or data with incomplete resolution values. Make sure your downstream system always takes the latest version of the data and overrides any previously received entries for the same timestamp.