User event notification flow

All user event notifications follow the same general flow:

1. A user action triggers an event for example, a Company Administrator assigns a user to a product, unassigns a user, or updates user information.

2. The AppDirect marketplace sends a user event notification to the vendor. This event is uniquely identified by an eventUrl.

3. Vendors must validate the request based on the authorization type configured for their product. See the following topics for more information on how to securely receive event notifications (select the topic based on whether you use shared or separate credentials):

   • Validate outbound event notifications (separate credentials)
   • Validate outbound event notifications (legacy) (shared credentials)
     After validation is complete, the vendor can read the eventUrl from the parameters to send an HTTP GET request for more information about the specific user event. Vendors can specify the format of the response they receive from AppDirect.
   • Add Accept: application/json in your HTTP GET request to receive the response from AppDirect in JSON format
   • Add Accept: application/xml in your HTTP GET request to receive the response from AppDirectin XML format
     If vendors do not specify the content type, an XML payload will be returned.

4. The AppDirect marketplace sends a JSON or XML response to the vendor.

5. The vendor sends a POST request back to the AppDirect marketplace with the account information, status information, or both.

6. The AppDirect marketplace conveys the status information to the customer through the AppDirect user interface.