Process Import Cost Account Job

Request

This operation processes (executes) the existing Batch job. The {jobID} path parameter is required to identify which batch job to process. The payload for this endpoint is an empty JSON object {} because it does not require any additional data to be sent in the request body. Once the job is processed, system will read the uploaded csv file, validate the data and create cost accounts based on that. In case of any error in the file, cost account will not be created and error csv file will be generated for details of error. The payload for this endpoint is an empty JSON object {} because it does not require any additional data to be sent in the request body. The jobId parameter in the endpoint URL specifies which batch of shipments to process.

Security

bearerAuth

Path

jobIDstringrequired

A unique identifier assigned to job which is automatically assigned by system while it is processed.

X-PB-Developer-Partner-IDstring

This is the Developer Partner ID. When the developer is the only partner, this field is not required.

curl -i -X POST \
  'https://api-sandbox.sendpro360.pitneybowes.com/costaccountmgmt/api/v1/costAccounts/batch/{jobID}/process' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'X-PB-Developer-Partner-ID: string'

Responses

Process Import cost Account

Bodyapplication/json

jobIDstring

It displays the jobID for which processing is requested

Example:"L86wbedwBon"

statusstring

It displays Job Status of submission, on successful submission it would show as Submitted

Example:"SUBMITTED"

Response

{
  "jobID": "L86wbedwBon",
  "status": "SUBMITTED"
}