Skip to main content

Sensolus Source

Connect Sensolus as a source to bring asset-tracking and location data into your warehouse. Inventory snapshots and time-windowed tracker data can be selected independently in the pipeline wizard.

For an overview of capabilities and use cases, see the Sensolus connector page. For Sensolus integration information, see the Sensolus integrations page.

Prerequisites​

Before you begin, ensure you have:

  • A Sensolus account with API access enabled
  • A Sensolus API key created by an administrator in the Sensolus developer/API access area
  • Your Sensolus organization ID, used to retrieve geozone definitions
  • If you are connecting to a sandbox or private deployment, the corresponding devices and visits service base URLs

Sensolus API availability and plan entitlements are managed by Sensolus. See the Sensolus platform plans or contact Sensolus if API access is not available in your account.

Supported Objects​

ObjectSync ModeDescription
DevicesFull RefreshThe complete tracker inventory, including tracker status and device metadata.
GeozonesFull RefreshGeozone definitions for the configured organization.
Geozone VisitsIncrementalVisit events for eligible tracker serials, including entry and exit times, duration, and geozone information.
Device LocationsIncrementalLocation observations for eligible tracker serials, including coordinates, timestamps, accuracy, and location context.

Not Yet Supported​

The current connector exposes the four objects listed above. Sensolus push events, alert resources, reports, device-configuration resources, and other APIs are not currently available as selectable objects.

Contact us with the objects you need -- expansion is prioritized by customer demand.

Incremental Sync​

Devices and Geozones run as full-refresh inventory snapshots. Geozone Visits and Device Locations sync incrementally, with progress tracked separately for each eligible tracker serial.

On the first incremental read for a serial, the connector requests the number of days set in Initial Sync Days (90 days by default). Later reads start from that serial's saved position and overlap the Late Arrival Lookback Days window (90 days by default). Set the lookback to 0 when you do not want an overlap.

Incremental overlap and destination load mode

The lookback intentionally re-reads records. If the selected destination uses APPEND, the overlapping rows remain and can create duplicates. When the destination supports a deduplicating load strategy such as MERGE, use it for pipelines that include Geozone Visits or Device Locations. Otherwise, set Late Arrival Lookback Days to 0 or account for the repeated rows.

Geozone Visits use each visit's entry timestamp to advance its per-tracker cursor. Device Locations use each location's insert timestamp to advance its cursor. Because visit data is fetched for each eligible serial, a large tracker fleet can take longer to sync; selecting only the tracker resources you need helps control sync time and API usage.

The Include Offline Trackers setting applies to Geozone Visits and Device Locations. When enabled, offline trackers are included in those resources; the Devices object remains a complete inventory snapshot regardless of this setting.

Authentication​

Sensolus uses API key authentication. Supaflow reads data from Sensolus and does not write back to the source.

Create an API Key​

Create an API key in the Sensolus developer/API access area, then copy it into Supaflow. If your Sensolus account does not show API access, ask a Sensolus administrator or contact Sensolus support. See the Sensolus integrations documentation for vendor guidance.

Permissions​

Use an API key that can access the tracker, location, visit, and geozone data you want to sync. Keep the key scoped to the account and data required by this source, and use a dedicated service credential when your organization supports one.

Configuration​

In Supaflow, create a new Sensolus source with these settings:

API Key*

The API key created in Sensolus.
Stored encrypted

Organization ID*

The Sensolus organization whose geozones should be synchronized.
Example: 1234

Devices API Base URL

The base URL for devices and geozones. Leave the production default unless Sensolus gives you a sandbox or private-deployment URL.
Default: https://internal.sensolus.com

Visits API Base URL

The base URL for visits and device locations. Override this together with the Devices API Base URL when using a sandbox or private deployment.
Default: https://cloud.sensolus.com

Sync Settings​

Initial Sync Days

How many days of history to request for each tracker on its first incremental read.
Default: 90 days
Range: 1 to 3650 days

Late Arrival Lookback Days

How many days before each serial's saved position to re-read on later incremental runs. Use this when tracker data can arrive after the event occurred.
Default: 90 days
Range: 0 to 365 days

Include Offline Trackers

Whether Geozone Visits and Device Locations include trackers whose current status is OFFLINE.
Default: enabled

Advanced Settings​

Schema Refresh Interval

How often to refresh Sensolus schema metadata before a pipeline runs.
Options:

  • 0 - Refresh before every pipeline execution
  • -1 - Disable automatic schema refresh
  • Positive value - Refresh at that interval in minutes (for example, 60 = hourly or 1440 = daily)

Default: 60 minutes

Test & Save​

After entering the API key and organization ID, click Test & Save to verify the connection and save the source.

After the schema refresh completes, create an ingestion pipeline and select the Sensolus objects you need.

Rate Limiting​

Sensolus applies API quotas and rate limits to its integration APIs. Supaflow handles transient rate limiting, server errors, and request timeouts with bounded retry and backoff, but large tracker fleets may take longer or benefit from narrower object selection and off-peak scheduling. See the Sensolus integrations page and Sensolus platform plans for current API availability and quota information.

Schema Evolution​

The connector exposes a stable set of known fields for the four supported objects. Nested Sensolus objects and arrays remain JSON fields rather than becoming additional tables.

  • Device custom data is retained in the Devices object when Sensolus returns it.
  • New vendor fields are not inferred from every read. They become available when the connector's declared schema is updated in a later release.
  • Schema Refresh Interval controls when Supaflow refreshes the connector metadata; it does not add unsupported Sensolus resources.

Troubleshooting​

Authentication failed​

Problem:

  • Test & Save reports an authentication or authorization failure

Solutions:

  1. Confirm the API key is active and copied without extra spaces.
  2. Verify that the key belongs to the Sensolus organization you entered.
  3. Ask a Sensolus administrator to confirm that API access and read permissions are enabled.
  4. If you use a sandbox or private deployment, confirm both base URLs are correct.

Geozones are empty or missing​

Problem:

  • The Geozones object returns no rows or does not contain the expected definitions

Solutions:

  1. Confirm the Organization ID matches the Sensolus organization that owns the geozones.
  2. Verify that the API key can read geozone definitions for that organization.
  3. Refresh the schema and reselect the object in the pipeline wizard after changing the organization.

Recent visits or locations are missing​

Problem:

  • A recent tracker event is not present after an incremental run

Solutions:

  1. Confirm the tracker is included by Include Offline Trackers when its current status is OFFLINE.
  2. Increase Late Arrival Lookback Days when tracker data can arrive after the event timestamp.
  3. Confirm that the tracker serial is present in the Sensolus Devices inventory.
  4. Review the per-object job details to see whether the visit or location read completed successfully.

Sync is slow or hits a rate limit​

Problem:

  • A large sync takes longer than expected or the job reports a rate-limit error

Solutions:

  1. Select only the Sensolus objects required by the pipeline.
  2. Schedule large tracker syncs during off-peak periods.
  3. Reduce the initial or lookback window when your retention and late-arrival requirements allow it.
  4. Review the current API quota with Sensolus and retry the job after the quota window resets.

Fields are missing from the schema​

Problem:

  • A field visible in Sensolus is not available in the pipeline wizard

Solutions:

  1. Set Schema Refresh Interval to 0 and refresh the schema.
  2. Confirm the field is part of one of the four supported objects and is returned by the API key's account.
  3. Contact support if the field is a newly introduced Sensolus field that is not yet in the connector's declared schema.

Support​

Need help? Contact us at support@supa-flow.io

Last updated on by pungaa
AI Tools
Ask ChatGPTClaudeAsk Claude
On this page