Scroll Ignore |
---|
Hide If |
---|
| Note |
---|
title | To access this API specification you wil need to be logged in |
---|
| To login with your TM Forum account please click on the Login button below Button Hyperlink |
---|
title | Login |
---|
type | primary |
---|
url | https://projects.tmforum.org/wiki/login.action?os_destination=%2Fdisplay%2FAPI%2FOpen%2BAPI%2BTable |
---|
|
Don't have an account? You can register by clicking here: Button Hyperlink |
---|
title | Register |
---|
type | primary |
---|
url | https://www.tmforum.org/user-registration/ |
---|
target | true |
---|
|
|
|
|
Show If |
---|
|
For every single of operation on the entities use the following templates and provide sample REST notification POST calls. It is assumed that the Pub/Sub uses the Register and UnRegister mechanisms described in the REST Guidelines reproduced below. REGISTER LISTENER POST for customerManagementDescription : Sets the communication endpoint address the service instance must use to deliver information about its health state, execution state, failures and metrics. Subsequent POST calls will be rejected by the service if it does not support multiple listeners. In this case DELETE /api/hub/{id} must be called before an endpoint can be created again. Behavior : DELETE customer hub REQUEST | DELETE /customerManagement/customer/hub/{id} Accept: application/json | RESPONSE | Status:204 |
DELETE customer account hub
REQUEST | DELETE /customerManagement/customerAccount/hub/{id} Accept: application/json | RESPONSE | Status:204 |
DELETE payment mean hub
REQUEST | DELETE /customerManagement/paymentMean/hub/{id} Accept: application/json | RESPONSE | Status:204 |
|
© TM Forum 2015. All Rights Reserved.