anchor.diff:  |ACCOUNT_CHANGE
   |Occurs when a customer account is modified
   |BLOCKING_STATE
  -|Occurs when there is a change in the state of an entitlement (It becomes BLOCKED or UNBLOCKED)
  +|Occurs when there is a change in the state of an entitlement or billing . See https://killbill.github.io/slate/#account-blocking-state[Blocking States] to know more
   |BROADCAST_SERVICE
   |Used to broadcast an event to other Kill Bill nodes (Typically used for plugin related events like plugin installation, plugin uninstallation, plugin start, plugin stop, etc. )
   |SUBSCRIPTION_CREATION
  
positive.code: [source, java]
  killbillAPI.getSecurityApi().login(login, password);
  
  * The `AccountUserApi#getAccountById` method requires as parameter a `TenentContext`. So, the code above creates a `TenantContext` object with the account id and tenant id and passes it to the `AccountUserApi#getAccountById` method. 
  
  * In general, all the API operations require either a `TenantContext` or a `CallContext` object. A `TenantContext` is mandatory for read only operations (operations which retrieve some data from Kill Bill) like the `AccountApi#getAccountById` used above. A `CallContext` is mandatory for read/write operations and contains additional metadata (user doing the change, reason code, etc.). These values are used for auditing purposes.
  
  
negative.code: 
  == Kill Bill Events Handled by Notification Plugin
  
  The following table lists all the events that the notification plugin is capable of handling. These are actually just enum constants defined in https://github.com/killbill/killbill-plugin-api/blob/d9eca5af0e37541069b1c608f95e100dbe13b301/notification/src/main/java/org/killbill/billing/notification/plugin/api/ExtBusEventType.java[ExtBusEventType]
  
  |===
  |Event Name | Event Description
  