Skip to main content
In the Bango Platform, entitlements describe a user’s ability to access a service provided by a merchant. In some circumstances you might not be able to implement our API methods and want to use an alternative solution to carry out actions on your entitlements. To support this, Bango Resale includes a batch processing feature that reads and writes files to your own dedicated Amazon S3 bucket. Input files define the actions to take, and output files describe the results.

​
Access control

When you sign up to use the Bango Resale API for resellers, Bango Support will supply you with:
  • Amazon S3 endpoint: you upload all your batch processing data here, and the results appear here after processing
  • Access key: your unique username for accessing the S3 endpoint
  • Secret key: your unique password for accessing the S3 endpoint

​
Locations

Files related to batch processing are stored at:
Where:
  • customer is your unique Amazon S3 bucket
  • processing_step is one of:

​
Input files

Your batch processing input files, uploaded to the input folder of your S3 bucket, must be Windows-1252 encoded and contain RFC 4180-compliant comma-separated values (CSV). Use the following filename format:
Where:
  • customer is your organization name or a similar reference for your own use
  • action describes the action or set of actions included in the file – see below. It doesn’t need to match any action type names
  • timestamp is a UTC datetime in the form YYYYMMDDHHMMSS
For example, MyReseller-CANCELLATIONS-20200902120000.csv. Each input file must contain a header row, and up to 250 action rows. The header row defines the columns used by every action row. There are five different types of actions. Four action types use the same columns (and can be included in the same input file or in separate files) and the fifth action type uses a different set of columns (and all actions of this type must be in the same input file, with no other action types). The table shows the actions and their columns: Except for action, the column names correspond to the fields you would include in the equivalent API call. The action value is always one of the five action types. Here are some example input files: MyReseller-TERMINATE-20191012112013.csv
MyReseller-SUSPEND-RESUME-20191123170452.csv
MyReseller-UPDATE-20191207095617.csv

​
File processing

Here’s how your input files are processed:
  1. The Bango Platform moves each file from the input folder to a temporary folder for processing
  2. The Bango Platform performs each action in a file, in turn
  3. If the action succeeds (HTTP status 2xx), a file is created or updated in output/success with the same name as the input file, and a row is added that shows the entitlement record after the action
  4. If the action fails (any non-2xx HTTP status), a file is created or updated in output/error with the same name as the input file, and a row is added that shows the entitlement record after the action
  5. After the Bango Platform has performed all actions in a file, it is moved to the archive folder
  6. When all processing is complete, the Bango Platform removes all temporary folders

​
Output files

The batch processing output files, stored in the output folder of your S3 bucket, are Windows-1252 encoded and contain RFC 4180-compliant comma-separated values (CSV). Every output file includes the action in the first column, and all the fields of the affected entitlement record in the subsequent columns. Here are some example output files: MyReseller-TERMINATE-20191112112013.csv
MyReseller-SUSPEND-RESUME-20191123170452.csv
MyReseller-UPDATE-20191207095617.csv

​
Coming soon

Support for creating entitlements using batch processing.