API to Place an order for internal and external vendors to NCC

To place a new order to NCC, please use /v1/client-orders API. This API would need to have the pre-defined order components from the pre-requisite set up and the uploaded roster file to the defined ECG location.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

ClientOrderRequest: Request object for the client-orders api, please see schema for details

string
required

Type of the vendor for which the order is placed. It can be either external or internal and should not have any other value.

int64
required

NCC tenant ID for which the order is to be placed.

int64
required

NCC Client org ID for which the order is to be placed.

int64
required

Campaign ID to place order. Either one of campaignId or campaignName is required. If both are present, then preference will be given to campaign ID.

string

Campaign name to place order. Either one of campaignId or campaignName is required. If both are present, then preference will be given to campaign ID.

int64
required

Requesting party ID to place order. Either one of requestingPartyId or requestingPartyName is required. If both are present, then preference will be given to requestingPartyId.

string

Requesting party name to place order. Either one of requestingPartyId or requestingPartyName is required. If both are present, then preference will be given to requestingPartyId.

string
required

The file path of ABS where the roster file is present. Roster file should be available at this location before placing the request.

string
required

Unique name of the client order to be created.

date
required

Service start date.

date
required

Service end date.

vendors
array of objects
required
vendors*
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json