How can we help? πŸ‘‹

Sending files to Scaler over SFTP

How your data provider connects to Scaler's SFTP server, uploads files and reads the receipt or error file Scaler returns for each one.

Purpose of this article

This article is for the technical team that sends files to Scaler: how to connect to Scaler's SFTP server, upload a file and read the answer Scaler returns for it. File formats, file rules and onboarding requirements are in SFTP file delivery requirements.


Connection and access

Topic
Detail
SFTP server, port 22
EU: sftp.scalerglobal.com. AU: sftp.au.scalerglobal.com. Your login details name your region.
Web upload page
EU: https://sftp-web.scalerglobal.com. AU: https://sftp-web.au.scalerglobal.com.
IP addresses for your firewall
EU: 52.211.214.252, 108.133.63.191. AU: 13.236.104.127, 13.55.239.10.
Login
One login per client and data provider. A login sees only its own folder.
Authentication
SFTP accepts an SSH key only, never a password. The web upload page uses the username and password.
Ways to upload
A scheduled export, any SFTP program (for example FileZilla, WinSCP or Cyberduck), or the web upload page
Key changes
Send the new public key to integrations@scalerglobal.com. Scaler adds it, you confirm you can log in, then Scaler removes the old key.

Rotate keys once a year, and whenever the person holding the private key leaves your organization.

Creating an SSH key pair

Run this on Mac, Linux or Windows PowerShell:

ssh-keygen -t ed25519 -C "scaler-sftp" -f scaler_sftp

This writes scaler_sftp, the private key you keep, and scaler_sftp.pub, the public key you send to Scaler. An RSA key also works.

Checking the server on first connection

The first time you connect, your SFTP program shows the server's key fingerprint and asks you to confirm it. Compare it with the values below. If it matches, confirm and connect. If it does not match, do not connect, and email integrations@scalerglobal.com.

Server
Key type
Fingerprint
EU, sftp.scalerglobal.com
ED25519
SHA256:jS0mCmG+o09Da+MUnzU9o+vyYGM9Ncy2i0Allqgjc/M
EU, sftp.scalerglobal.com
RSA
SHA256:qbg1P/TWUCifOPZz5Ad8vIinHHchbi/uiI/nZ5TGmDA
AU, sftp.au.scalerglobal.com
ED25519
SHA256:Ow5xk5Cdwiy3i/6+yoNCIpBHRwb6eBrYtD5iPDjNd3k
AU, sftp.au.scalerglobal.com
RSA
SHA256:jN5qpJK2oGGuyRP+Zkq+3uLZr81ZM6ekTTNVX0tFjzY

Your program shows one of the two lines for your server, usually ED25519.

Folders

Folder
Purpose
You can
inbox
Upload files here
Upload, list, download, overwrite
landed
Scaler's copy of each file it picked up from inbox
List, download
receipts
Scaler's answer for each file it read
List, download
errors
Scaler's answer for each file it refused
List, download

Upload files directly to inbox. Files cannot be deleted or renamed, and they stay in inbox after Scaler reads them. Every file in these four folders is deleted 90 days after it arrives there, so keep your own copy of anything you need for longer.


Uploading a file

By SFTP, from a scheduled export or an SFTP program

  1. Connect to your region's SFTP server on port 22 with your username and private key.
  1. Upload the file to inbox.
  1. After a few minutes, read the answer in receipts or errors.

On the web upload page

  1. Open your region's web upload page and sign in with your username and password.
  1. Open inbox and upload the file.
  1. After a few minutes, open receipts or errors to read the answer.

Give every upload a new file name, for example companyname_2026-10.xlsx, so each file keeps its own receipt.


What you get back after each file

Every file gets one answer within minutes. One bad row does not stop a file: Scaler sets the row aside, stores the other rows and reports the row.

Outcome
What you find in your folder
What to do
Processed
A receipt in receipts
Nothing
Processed, some rows set aside
A receipt in receipts listing up to 100 set-aside rows, each with row number, column and reason
Correct those rows and upload the file again
Identical file already received
A duplicate receipt in receipts
Nothing. The first upload's data is stored.
Refused because of the file
An error file in errors explaining the problem
Fix the file and upload it again
Problem on Scaler's side
An error file in errors saying the problem is on the Scaler side, with a reference
Nothing to fix in your file. Email the reference to integrations@scalerglobal.com.

The receipt is a JSON file for your automation. The error file comes as JSON and as a text file for people.

Common reasons a row is set aside
Reason
Meaning
Fix
row_unreadable
No Asset ID or Meter ID, or no value in Consumption, Redelivery To Grid, Production or Meter Reading
Fill the missing cell
period_invalid
A date is empty, not yyyy-mm-dd, or End Date is before Start Date
Correct the date
period_overlaps
The period overlaps another period of the same meter, already stored or in the same file
Send the row with the stored period's dates, or with the stored row's Record ID. To change a period stored without a Record ID, contact the Scaler client service team.
value_invalid
A number holds commas, text or a unit
Write a plain number
unit_unknown
Unit is empty or not recognized
Write the unit, for example kWh
row_duplicate
The same meter and period appear twice in the file. Scaler keeps the later row.
Keep one row per meter and period
meter_not_found, record_unstorable
Scaler could not store the row
Nothing to fix in your file. Email integrations@scalerglobal.com with the file name.

Corrections, duplicates and re-sends

  • A corrected row replaces the earlier value only when it has the same meter, Start Date and End Date. A row with a Record ID replaces the earlier row with the same meter and ID, and can change its period too. Send the full corrected value, not the difference.
  • Always use the same period boundaries. Without a Record ID, a row for other dates that overlap a stored period does not replace the stored row: Scaler sets it aside as period_overlaps.
  • An identical file sent again within 90 days stores nothing, and you get a duplicate receipt. A corrected file differs, so Scaler reads it.
  • A file adds or updates data. It never removes data: a value missing from a later file stays in Scaler. To remove a value, contact the Scaler client service team.
  • An upload under an earlier file name is read, and its receipt replaces the earlier receipt.

Troubleshooting and common mistakes

  • No receipt or error file after 15 minutes β†’ check the file sits directly in inbox, then email integrations@scalerglobal.com with the file name and upload time.
  • SFTP refuses the login β†’ SFTP accepts the SSH key only. Check you use the private key that matches the public key you sent.
  • The error file says the header is not the Scaler template β†’ the header must be the first row and include Asset ID, Meter ID, Unit, and at least one of Consumption, Redelivery To Grid, Production or Meter Reading.
  • Duplicate receipt and nothing stored β†’ that exact file was already processed. Send a corrected file instead.
  • A value still shows after you left it out of a file β†’ files never remove data. Contact the Scaler client service team.
  • Data stored but not visible in Scaler β†’ the meter is not mapped yet. The client's admin maps it on the Automations page.
  • A NEM12 file is refused as incomplete β†’ the file has no 900 end-of-file record. Write the export fully before you transfer it.

Contact

Logins, SSH keys, passwords, files without an answer and Scaler-side errors: integrations@scalerglobal.com. File format, scope and fees: the Scaler client service team.


Additional resources

Did this answer your question?
😞
😐
🀩