Mitchell1 Intent Registry

Basic steps

1. Obtain access to the intent from the Mitchell1 Auth team.

Contact Mitchell1 Support to obtain credentials (known as a ClientID/AccessID and ClientSecret/AccessSecret). These credentials are known to both the Mitchell1 Authorization Server and your application.

2. Use Intent Registry’s Discovery service to locate the integration client script end point.

The Mitchell1 Intent Registry Server does not publish endpoints. You should use the discovery service to locate the Integration Client Script.

Please provide endpoint “vendor/vnd.m1.script.integrationclient.v1” to the discovery service to get the location of the integration client script used in the next step.

3. Include Mitchell’s Integration Client Script on consumer page.

Once you have obtained the location of the integration client script in step 2, you will need to include it on your web page using script tag.

<script src="@scriptPath"></script>

where '@scriptPath' is the value retrieved from discovery in step 2.

4. Obtain an access token from the Mitchell1 Authorization Server.

In order to get a shared web component, you will need to obtain an accesstoken for the Mitchell1 Authorization server over a selected workflow. This token then will be required to get passed to the integration client script. The access token submitted with the request will be used to autheticate and authorize the request.

5. Send the access token and shared web component information to the integration client script.

After you get your access token you will provide it to the integration client script along with the shared web component action, shared web component id, method (inline or new window), target containers id and the shared web component dimensions.

The integration client script will take care of obtaining details for the selected shared web component and put its content into the container you supplied or a new window depending on the method you chose.