# Integrating with OPSCOM

## <span class="legacy-color-text-blue3">Considerations for Scoping an Integration </span>

<span class="legacy-color-text-blue3">Regardless of the integration we are scoping we need the following questions answered.</span>

1. <span class="legacy-color-text-default">What are the endpoints; where will we connect and send data? </span>
    1. <span class="legacy-color-text-default">What system or URL are we querying?</span>
    2. <span class="legacy-color-text-default">Test system logins and a test endpoint address to which we can send queries to.</span>
        1. <span class="legacy-color-text-default">we will need the same for production systems </span>
2. <span class="legacy-color-text-default">Are there additional (special) API endpoints and/or API tokens to access the system? </span>
3. <span class="legacy-color-text-default">What API/SDK is recommended?</span>
    1. <span class="legacy-color-text-default">at the core the OPSCOM platform is built on PHP; we also work with Java and many other languages</span>
4. <span class="legacy-color-text-default">Supporting documentation for the API/SDKs that we are integrating with</span>
    1. technical contact(s); either on location and/or for the vendor.
5. <span class="legacy-color-text-default">How will the data (or user) flow through the system? ie. business logic/flow</span>

## For Network Administrators

Our development servers are behind:

- 208.124.170.242
- 178.128.233.75

Our production servers are behind:

- 209.217.117.82
- 159.203.14.67

## <span class="inline-comment-marker" data-ref="b8fa4083-47d7-433f-b638-85bc55645de8">Information Flow</span> through OPSCOM

This example shows the flow of information through the integrated system of record and OPSCOM.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/bfhimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/bfhimage.png)

### Sample: SSO Integration

This example shows the flow of a user through the system, and at what points the client wanted us to apply business logic.

Notice that in their implementation they also described the flag that would be used to designate special users in the system.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/D7Eimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/D7Eimage.png)

### Sample: LDAP/Active Directory Integration

This represents a standard flow of information to support LDAP/AD user validation.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/eJ9image.png)](https://opscom.wiki/uploads/images/gallery/2024-06/eJ9image.png)

## Current APIs Available

**<span data-colorid="qqf7mq8vfi">Operations</span>**<span class="legacy-color-text-red2">Commander</span><span data-colorid="ylh3whlu13"> </span><span data-colorid="wq2melhhao">(OPSCOM)</span><span class="legacy-color-text-blue3"> has made APIs (Application Programming Interface) available that allow for third-parties with proper authentication to interact and manipulate data in OPSCOM as needed to accomplish specific functions, for example adding valid permits from pay and display machines.</span>

## Other Integrations Available

OPSCOM has integrations with third-parties. Your Sales Rep can discuss how you can make use of these integrations.

- T2 Luke II Meters
- CALE Meters
- MacKay Meters
- Tattile Cameras
- Vaxtor Cameras
- gTechna Cameras
- HotSpot Temporary Permits