- Docs
- API reference
- Endpoints and schemas
- GraphQL
- Selection
OperatingLocationTechnologiesUsed
Indicates third-party technologies being used at a particular operating location.
Selection. This type is a selection. You reach it through a connection, and you choose which of its fields come back.
Indicates third-party technologies being used at a particular operating location.
Time Structure
Section titled “Time Structure”This attribute also includes a historical component through the rank property:
- Rank = 0: Reflects Enigma’s most recent, validated observation of a technology being used at a location.
- Higher ranks (1, 2, etc.): Represent older, previously recorded periods of usage, preserved for reference and limited historical tracking.
Maintaining multiple ranks helps you see how a location’s technology usage may have changed over time, such as switching from one payment provider to another.
Data Sources
Section titled “Data Sources”Technologies are determined by parsing merchant identifiers from credit card transaction data.
Methodology
Section titled “Methodology”This data is sourced from private vendors that we independently verify for accuracy. Currently we provide information only for payments-related technologies.
We currently identify Clover, Paypal, Shopify, Square, Stripe, and Toast.
Where it appears
Section titled “Where it appears”Shortest path from a primary entity: Brand → operatingLocations → OperatingLocation → technologiesUseds → OperatingLocationTechnologiesUsed.
OperatingLocation.technologiesUseds
Fields
Section titled “Fields”| Field | Label | Type | Description |
|---|---|---|---|
id |
ID | UUID! |
The unique identifier of this object. |
firstObservedDate |
First Observed Date | String |
The earliest date of a source record that supports this attribute or relationship. The source date is, for example, the date when Enigma collected the record or when the source last updated it. Most values have a date, a time, and a UTC offset, but some have the date only. |
lastObservedDate |
Last Observed Date | String |
The latest date of a source record that supports this attribute or relationship. It uses the same source dates and the same format as firstObservedDate. |
rank |
Rank | Int |
Determines the display order of the attribute, with lower values shown first |
technology |
Technology | String |
This field represents the specific third-party technology being used by the location. |
category |
Category | String |
This field represents the category of the third-party technology being used by the location. |
internalId |
String |
A numeric identifier that Enigma assigns to this object when it builds its data. On most attribute objects, id is the UUID form of this number. |
|
internalOperatingLocationId |
String |
The internalId of the operating location that this attribute describes. |
Math fields
Section titled “Math fields”Every record of this type answers count, countDistinct, has, sum, min, max, avg, collect, minDateTime, maxDateTime. Each takes field and an optional conditions. See Selection.
Example
Section titled “Example”query { search(searchInput: { entityType: BRAND name: "Safeway" conditions: { limit: 1 } }) { ... on Brand { id operatingLocations(first: 1) { edges { node { technologiesUseds(first: 1) { edges { node { id firstObservedDate lastObservedDate rank technology } } } } } } } }}Response, as returned:
{ "data": { "search": [ { "id": "0f26fbef-3436-4f85-8bcd-31fe12a4f99a", "operatingLocations": { "edges": [ { "node": { "technologiesUseds": { "edges": [] } } } ] } } ] }}