...
Filtering and attribute selection rules are described in the TMF REST Design Guidelines.
Notifications are also described in a subsequent section.
...
GET /usageManagement/usage/{ID}
The resource is used to retrieve the usage entities.
Filtering is allowed on all attributes.
Attribute selection is possible for all attributes.
GET /usageManagement/usage/{ID}/{attributeSelector}?{filtering expression}
...
All standard error codes apply.
...
...
GET /usageManagement/usageSpecification/{ID}
The resource is used to retrieve the usage specification entities.
Filtering is allowed on all attributes.
Attribute selection is possible for all attributes.
...
All standard error codes apply.
...
POST /usagemanagement/usage
The resource is used to create usage entities.
POST without specifying the ID of the usage record must result in the system generating the ID for the usage The resource is used to create usage entities.
POST without specifying the ID of the usage record must result in the system generating the ID for the usage record (typical). In a specific case, the ID can also be included in the POST (optional)
Attribute selection is possible for all attributes.
POST /usageManagement/usage/{ID}/{attributeSelector}
...
REQUEST |
POST usageManagement/usage Content-type: application/json
{ "date": "2013-04-19T16:42:23-04:00", |
RESPONSE |
201 |
...
...
POST usageManagement/usageSpecification/
The resource is used to create usage specification entities.
Attributes:
...
Example REQUEST |
POST usageManagement/usageSpecification/ Accept: application/json
{{ |
Example RESPONSE |
201 |
...
...
PATCH usagemanagement/USAGE
The resource is used to modify usage entities.
PATCH /usageManagement/usage/{ID}/?{filtering expression}
Attributes and Rules
...
REQUEST A – "rate" a single usage record |
PATCH usageManagement/usage/1234/ Content-type: application/json
{ |
RESPONSE |
201 |
...
ID |
DELETE usagemanagement/USAGESPECification
The resource is used to DELETE a usage specification entity.
DELETE /usageManagement/usageSpecification/ID/
Delete a usage specification
Deletion of usage specifications is only allowed by specifying the ID in the URL, deleting a single usage specification.
If DELETE is implemented at all, a check must be implemented that verifies that no usage records exist in the system that depend on the usage specification to be deleted – otherwise a 409 (Conflict) HTTP error code should be sent.
REQUEST |
DELETE usageManagement/usageSpecification/1234/ |
RESPONSE |
200 |
...
POST usageManagement/importJob
ImportJob Tasks are created as resources.
The ImportJob is attached to the URL of the root resource where the content of the file specified by the ImportJob will be applied.
For example to apply the content of the import file located at ftp://ftp.myUsage.com/usage/54 to the usageManagement root.
REQUEST |
POST ../usageManagement/importJob |
RESPONSE |
201 Content-Type: application/json Location: ../usageManagement/importJob/54
{ "url": "ftp://ftp.myUsage.com/usage/54" |
...
POST usageManagement/exportJob
ExportJob Tasks are created as resources.
The ExportJob is attached to a specific resource acting as the root for the collection of resources to be streamed to a File.
For example:
REQUEST |
POST ../usageManagement/exportJob |
RESPONSE |
201 Content-Type: application/json Location: ../usageManagement/exportJob/54
{ |
...
GET usageManagement/exportJob
ExportJob resources can be found under the API/exportJob collection and may be retrieved using the normal GET constructs.
For example:
REQUEST |
GET ../usageManagement/exportJob/54 |
RESPONSE |
200 Content-Type: application/json
{ |
...
GET usageManagement/IMPORTJob
ImportJob resources can be found under the API/importJob collection and may be retrieved using the normal GET constructs.
For example:
...