Create BillJob
Changed onCreate a new BillJob to handle asynchronous bill calculations for a specific Organization.
This operation allows you to initiate the processing of bills according to specified parameters. For example, create a BillJob to run only those bills where billingFrequency is MONTHLY. Note that if you want to run a BillJob for all billing frequencies, simply omit the billingFrequency request parameter.
Once created, the BillJob's progress can be monitored:
- In the Running Tasks panel in the m3ter Console - for more details, see Running Bills Manually
- Queried using the List BillJobs endpoint.
NOTES:
- Consolidated bills. If you've already run billing with the Consolidate bills option disabled for your Organization but you then enable it, subsequent Bills for specific bill dates will now start afresh and not update earlier non-consolidated Bills for the same bill date. To avoid any billing conflicts, you might want to archive these earlier versions or delete them entirely.
- Maximum concurrent BillJobs. If you already have 10 BillJobs currently running, and try to create another one, you'll get an HTTP 429 response (Too many requests). When one of the existing BillJobs has completed, you'll be able to submit another job
Request
- Base URLhttps://api.m3ter.com
- AuthOAuth 2Authorization codehttps://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize, token URL https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/tokenClient credentialsToken URL /oauth/token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
The unique identifier (UUID) for your Organization. The Organization represents your company as a direct customer of our service.
Request body
Example request
{
"currencyConversions": [
{
"from": "EUR",
"to": "USD",
"multiplier": 1.12
}
],
"timezone": "UTC"
}Response
Returns the details of the created BillJob
Example response
{
"currencyConversions": [
{
"from": "EUR",
"to": "USD",
"multiplier": 1.12
}
],
"timezone": "UTC"
}Changes
- breaking
the
request property type changed from no type toobject - breaking
the
response's property type changed from no type toobjectfor status
- breaking
- breaking
the response property
////became optional for the status
- breaking