Uptick
Uptick is a field service management platform for the fire protection, HVAC, and building compliance industries, covering asset inspections, defects, work orders, quotes, and invoicing. The Uptick API exposes this data over REST, letting you read and write tasks, clients, properties, assets, and related records. Nexla connects to Uptick using a 3-legged OAuth2 authorization flow.
Power end-to-end data operations for your Uptick API with Nexla. Our bi-directional Uptick connector is purpose-built for Uptick, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Uptick or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Uptick workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating an Uptick credential in Nexla, you need an OAuth2 application registered in your Uptick workspace, along with the base URL for that workspace. Uptick uses a 3-legged OAuth2 authorization flow, so you supply the application's Client ID and Client Secret, and then authorize Nexla to access Uptick on your behalf.
To register an application and obtain your credentials, follow these steps:
-
Sign in to Uptick with an account that has administrator access to the Control Panel.
-
Navigate to Control Panel > Uptick API.
-
Click Create Application. Uptick automatically generates a Client ID and Client Secret for the new application.
-
Enter a name for the application (for example, "Nexla Integration"), then click Save New Application.
-
The application now appears on the Uptick API page. Copy the Client ID and Client Secret and store them securely, as you will need them to configure your Nexla credential.
-
Note the base URL of your Uptick workspace. This is your company's Uptick domain, in the form
https://yourcompany.onuptick.com.
If you later need to revoke access, return to the Uptick API page in the Control Panel, then click Edit > Delete > Confirm for the relevant application. For more information, see the Uptick API getting started guide and the Uptick API help center.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Authorization URL | No | No | The URL endpoint where users authenticate and authorize access |
| Client ID | Yes | Yes | A unique public identifier assigned to your application |
| Access Scope | No | No | A space-separated list of permissions your application requests |
| Token URL | No | No | The URL endpoint where authorization codes are exchanged for access tokens |
| Client Secret | No | Yes | A private key used to authenticate your application when requesting tokens |
| Base URL | Yes | No | The base URL for your Uptick workspace (e.g. https://yourcompany.onuptick.com). |
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter the Client ID and Client Secret from the application you registered in Prerequisites, and set the Base URL to your Uptick workspace domain (for example,
https://yourcompany.onuptick.com). Provide the Authorization URL, Token URL, and Access Scope if your Uptick workspace requires values other than the defaults. -
Complete the 3-legged OAuth2 flow when prompted. You will be redirected to Uptick to sign in and grant Nexla permission to access your workspace on your behalf, then returned to Nexla once authorization is complete.
If your Client Secret is compromised, delete the application in the Uptick Control Panel under Uptick API and create a new one, then update your Nexla credential with the new values.
For detailed information about Uptick API authentication and available resources, see the Uptick API help center.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Uptick connector tile, then select the credential that will be used to connect to the Uptick instance, and click Next; or, create a new Uptick credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Uptick endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Uptick data sources can also be manually configured to ingest data from any valid Uptick API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Uptick data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Use as a destination
Click the + icon on the Nexset that will be sent to the Uptick destination, and select the Send to Destination option from the menu. Select the Uptick connector from the list of available destination connectors, then select the credential that will be used to connect to the Uptick workspace, and click Next; or, create a new Uptick credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Uptick endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Manual configuration
Uptick destinations can also be manually configured to send data to any valid Uptick API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Uptick APIs typically expect JSON format for write operations. For update operations, include the ID of the record to be updated in the request URL.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Uptick endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Uptick endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.