Page Comparison

This template should be used when responding to a request for API access for organizations who are not listed on this sheet. Organizations on the sheet are already working with Tim/Ryan on an API integration and we should make sure to give a "normal" initial reply and then re-assign to Ryan. 

For any organizations that are not on the sheet, please reassign to Ryan Izuno, but we can send out an initial response to help ensure the customer know what is entailed in having API access and setting up a custom integration.

...

If you receive an API Access Request you must proceed with the following steps depending on the applicable scenario:  

If the Requestor is an Org Admin and THEY ARE already on this sheet  Installer - API Integration Tracker.xlsx :

• Tag Ruel.Balicas, Charles Bazile, Nathan Dubbs, Eric Suarez (So they will be responsible for following the process for /wiki/spaces/CX/pages/2954035234)

If the Org is NOT on this Sheet  Installer - API Integration Tracker.xlsx :

• It means that this is a new integration & CS should hold a kick-off so the following canned response should be sent to the Org

...

In the meantime, we wanted to share more information with you regarding API access.  Here is a link to more information.  Additionally, to hasten the process, can you please respond to the following questions:

• Are you aware of the additional $200 per month charge for API access and still want to proceed?
• Do you have an internal development team or external development resources to complete the integration?
• What services or portals are you looking to integrate with Sighten?
• Do you plan to send information to the Sighten portal via the API?
• Do you plan to pull information from a job to store in another portal?

Thanks in advance for your reply and have a great day!

...

• Once the canned response has been sent you will need to re-assign the ticket to John Kilfoil