Events

EVENTS are generated for the asynchronous events, in particular for:

• ORDER – order life cycle

• SERVICE – service life cycle

Events on orders

The main events applying to orders are described below.

Event Type	Label	Event description
order-submitted	SUBMITTED	The draft order was successfully submitted.
order-acknowledged	ACKNOWLEDGED	The order was acknowledged by Covage.
order-running	IN PROGRESS	The order is in progress.
order-rejected	REJECTED	The order was rejected.
order-completed	COMPLETED	The order was successfully completed.

See the complete description of the events events API.

Events on services

A service may be subject to modifications or terminations not requested by the operator.

The operator can search for the events issued by the Covage platform. You can search for the events issued after a specific date.

Type	Trigger
service-activated	creation by Covage of an order-completed event on an order of the type activate
service-terminated	creation by Covage of an order-completed event on an order of the type terminate
service-slammed	loss of access, generally due to slamming by another operator. (**)

(**) In cases where the loss of access was not desired by the end customer, and where, upon reception of the loss-of-access notification (service-slammed), TELCO complains of slamming (not requested by the customer), it is recommended to trigger a slamming procedure, which consists in gathering information about the slamming operator and restoring the service.

See the complete description of the events API.