As you become more familiar with using the command line to automate the queuing of certain jobs, it becomes obvious that you can build a greater automated pipeline on top.
Example uses:
A script or program which lists all the files in a folder and queues them up.
A script which runs through the lines in a file and queues them up as storefronts.
A script or program which automatically keeps track of the most recent update to results from a particular (set of) suppliers and runs them again as and when necessary.
Exit codes
When a run is completed, the CLI will return with one of the following exist codes:
Code | Meaning | Detail |
|---|---|---|
200 | SUCCESS | Completed with results |
204 | NO CONTENT | Completed, but there were no results, so no output file |
400 | BAD REQUEST | There was a problem with your command |
500 | INTERNAL ERROR | Something went wrong |
In additiona, the last two lines in the output contain the final job status, and the location of the output file (if any) on disk.
Status can be one of: NEW, QUEUED, READING, PAUSED, RUNNING, COMPLETE, CANCELLED, ERROR.
By parsing the exit code and these lines you will be able to take further action in your automation script, depending on the outcome of the run/job.
While the actual implementation of automation software is beyond the scope of this article, feel free to contact support for assistance with Price Checker CLI integration.