Resources | Methods |
---|---|
https://localhost:8443/api/rest/billing |
GET
This method is deprecated.
|
https://localhost:8443/api/rest/billing/generate-cdrs |
POST
Initiates the process to generate CDRs matching the input search filter parameters.
|
https://localhost:8443/api/rest/billing/status |
GET Retrieves CDRs generation status.
|
https://localhost:8443/api/rest/billing/download-cdrs |
GET Downloads CDR file [tags: DMA]
Note 1: ETag is currently passed back to the user as a UNIX timestamp.
|
GETThis method is deprecated. API users are highly recommended to use /billing/generate-cdrs and /billing/download-cdrs instead. Retrieves a list of CDRs matching the input search filter parameters. The list as three files inside one zipped file, which is streamed to the user. The three files will separately list calls, conference, and call counts as CSV lists. Note 1: This method's default search will return all CDRs from midnight of the current day to the current time when search criteria are not provided. Note 2: Datetime format is [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]. Examples include: 2001-10-26T21:32:52, 2001-10-26T21:32:52+02:00, 2001-10-26T19:32:52Z, 2001-10-26T19:32:52+00:00, -2001-10-26T21:32:52, or 2001-10-26T21:32:52.12679 [tags: DMA,RPRM] RequestQuery Parameters
Response
|
POSTInitiates the process to generate CDRs matching the input search filter parameters. A URL to check the status of the task will be returned in the location header. Note 1: This method's default search will generate all CDRs from midnight of the current day to the current time when search criteria is not provided. Note 2: Datetime format is [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]. Examples include: 2001-10-26T21:32:52, 2001-10-26T21:32:52+02:00, 2001-10-26T19:32:52Z, 2001-10-26T19:32:52+00:00, -2001-10-26T21:32:52, or 2001-10-26T21:32:52.12679 [tags: DMA,RPRM] RequestQuery Parameters
Response
|
GETRetrieves CDRs generation status. [tags: DMA]RequestResponse
|
GETDownloads CDR file [tags: DMA]Note 1: ETag is currently passed back to the user as a UNIX timestamp. It is not truly an "ETag", but is a placeholder for more correct implementation when billing can be returned as a XML package rather than a set of CSV's. Until then, it is still included as a useful piece of information about when the API got the billing results to the user's query. RequestQuery Parameters
Response
|