All Collections
Pledge platform
Importing your data
How to use Pledge for emissions measurement
How to use Pledge for emissions measurement

Understand the different ways of using Pledge to calculate emissions for your shipment data

Updated over a week ago

Options for getting your data into Pledge

There are 6 ways to get your data into Pledge so that we can compute emissions for you:

File upload from the app

Pledge supports the upload of data files containing bulk items (in CSV or XLSX format) directly from within the Pledge App. Once the file is uploaded, it will then be processed and imported. The emissions results will then be available to review within the app shortly thereafter.

Warning: File upload is subject to certain limitations eg. a maximum file size of 6MB.

To learn more, head to the import area in the Pledge App and follow the instructions.

File import by email

Pledge supports the import of data files containing bulk items (in CSV or Excel format) directly from email as an attachment where the address to send emails is:

{activity_type}@{mode}.pdx.pledge.io

Where:

  • {activity_type} is one of: freight, last_mile, ride_hailing etc.

  • {mode} is either test or not specified depending on which mode you want to

AWS S3 bulk file import/export

Note: This feature is only available on custom plans. Please contact support@pledge.io to inquire

Pledge supports the import of data files containing bulk items (in CSV format) by file transfer via Amazon S3 bucket. Once your file is dropped into the designated S3 bucket and folder, it will be picked up, processed and imported. The emissions results will then be available in a results file (in CSV format) in another folder shortly thereafter for you or your server process to pick up. You can also review the progress and status of imports by heading to the import area in the Pledge App.

To learn more, start here.

Portal or TMS integration via Pledge's Open API

Pledge has an open API that allows you to calculate the emissions for a given item (journey, shipment, ride, stay, transaction etc.) in real-time - you call the API with the relevant parameters and you get back an estimate of emissions right away for that one item.

This API allows seamless integration with your customer or internal facing portals, TMS, ERP or other systems with full flexibility.

To learn more, head over to our API reference.

CargoWise integration via eAdaptor

This feature is currently under development. If you would like to get early access and join the beta program please contact support@pledge.io to inquire

To learn more, start here.

CargoWise, Descartes, Magaya, Other TMS integration via Chain.io

Supported TMS include CargoWise, Descartes, Magaya and more.

This feature is currently under development. If you would like to get early access please contact support@pledge.io to inquire

To learn more, start here.

Choosing the right option

Each option is better suited to different scenarios. Here's a quick cheat sheet to help you decide which option to use:

Option

When to use

In-app file upload or import by email

  • When you want to compute emissions for bulk items periodically or on an ad-hoc basis

  • When your file sizes are less than 6MB

  • When you want to try Pledge out without needing to do any integration work

  • When you don't need or want an automated process

  • When you don't have engineering resources to consume a simple REST API or set up an automated server-to-server file exchange

AWS S3 bulk file import/export

  • When you want to compute emissions for bulk items periodically or on an ad-hoc basis

  • When you potentially have file sizes that are larger than 6MB

  • When you want to set up an automated process without using human intervention

  • When you have engineering resources to implement the file exchange protocol

  • When you want to ingest emissions data into your own data warehouse or ETL pipelines

Pledge's Open API

  • When you need to compute emissions for single items in real-time

  • When you want to embed emissions estimates into your customer journey either for indicative quotes or at the point-of-sale or otherwise

  • When you have engineering resources who can consume a simple REST API

CargoWise integration via eAdapter

  • When you use CargoWise and want to set up an automated process without human intervention

TMS integration via Chain.io

  • When you want to set up an automated process without human intervention

  • When you already or would like to set up an integration with Chain.io and your TMS is supported

Did this answer your question?