When to de-scope monitoring on an access token
After de-scoping monitoring for a given access token, you will no longer receive notifications for Account or Policy events related to the insurance account linked to that access token. How and when you de-scope depends on what you passed in asuser.id
during Start Ignition:
-
If you passed a user ID to
user.id
: De-scope the access token when you want to stop receiving notifications for the user’s insurance account across all entities.For example, if a user offboards from your platform entirely, you should de-scope monitoring on their access token to stop tracking their account across all associated trips, loans, or reservations.
-
If you passed an entity ID (e.g. trip, loan number, reservation) to
user.id
: De-scope the access token when the lifetime of that entity is over, and you no longer want to track insurance for it.For example, if the user’s insurance account was linked for a trip and the trip has ended, you should de-scope the access token associated with that trip.
Authorizations
Your secret API key. This will be shared with you during onboarding and should be considered sensitive - it’s a password after all! Your secret will be matched with your client ID to authenticate your requests.
Headers
Your client ID. This will be shared with you during onboarding.
The client ID of the destination client. This is optional and only used by platform clients. See the Axle for Platforms guide for more information.
The access token required for access to the requested Account. Returned as part of Exchange Token.
Body
Scope to descope from the access token.
monitoring