When an OAuth integration is installed, they will direct the user to the OAuth Authorize page. From there, when the user accepts the installation. integrations.authorize is called from the acceptance page and will generate an access code that will be redirected to the integrations authorizationURL. From there, the integration is able to exchange the access code for an OAuth Authorization token for future use.

An integration can only have one of Repairer or Supplier scope in this iteration. Attempting to have either without their respective business will result in an Invalid Scopes error as well as attempting to have both in the same integration. An integration must also have atleast one scope. All of these are limitations of the current integrations table.