Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

B

bulk

Bulk APIs are the Cloud Elements APIs used to move large amounts of data. You can upload and download data in bulk from an endpoint in a normalized way. We leverage the provider bulk endpoints whenever available. But, when the API provider has no bulk endpoints, we provide a pseudo bulk service. Cloud Elements stores the files (encrypted) on Cloud Elements servers for a maximum of seven days.

C

canonical

The standardized version of a specific resource unrelated to a specific API provider, but broadly applicabele to all providers with similar reources. Canonical resources can be broadly authorative, as in VDR Catalog resources intended to aggregate common fields from multiple API providers. They can also be specifically authorative in relation to your data model, such as any VDRs in your My VDRs list.

canonicalized

The standardized version of a specific resource unrelated to a specific API provider, but broadly applicabele to all providers with similar reources. Canonical resources can be broadly authorative, as in VDR Catalog resources intended to aggregate common fields from multiple API providers. They can also be specifically authorative in relation to your data model, such as any VDRs in your My VDRs list.

ceql

Cloud Elements Query Language. The search and filter language used by Cloud Elements to standardize searching across all our different elements.

D

discovery service

Cloud Elements includes a comprehensive data discovery service that provides normalized metadata, such as the list of field names and types. Additional information, if available from an endpoint, may also be obtained such as: display name, read-only, etc. If an endpoint doesn’t provide discovery service APIs, Cloud Elements will still provide a minimum set of metadata about the given resource (e.g., name and type). Cloud Elements also allows you to discover custom fields (as long as the values are not empty), by supplying an object Id when a native discovery service is not available. The Discovery Service is used along with the Transformation Service to normalize the responses across endpoints.

E

element

A prebuilt API integration that enables a connection into a specific cloud application or cloud service endpoint (such as Box or Salesforce.com). We organize our Elements into categories called ‘Hubs’, which allow you to integrate an entire category through a single, uniform API.

Element Builder

The Cloud Elements feature that enables you to extend the capabilities of existing Cloud Elements integrations or build a new element from scratch.

element card

Each element appears in the elements catalog on its own card that shows basic information about the element and enables access to the ways that you can your with an element.

element instance

An Authenticated Element Instance is single authenticated connection of an element between Cloud Elements and an account at an API provider such as a Salesforce

element instance token

The unique identifier of a specific authenticated element instance.

endpoint

A unique URI that represents a resource and includes the HTTP method and resource. it includes the method (GET, PUT, PATCH), (sometimes) the base URL, and the resource. For example, GET https://api.cloud-elements.com/elements/api-v2/instances, or shortened to GET /instances.

event

An action that occurs at an API provider associated with an authenticated element instance and is monitored either through Polling or Webhooks.

event polling refresh interval

The number in minutes that specifies how often the poller should check for changes.

event resource name

The name of the resource that you want to monitor at the API provider.

F

field

Data within a resource.

formula instance

A specific instance of a formula template configured with explicit variables and associated with specific element instances.

formula step

An individual step within a formula workflow that can include branches to subsequent success and failure steps.

formula template

A Formula Template is a reusable workflow that is independent of the element and includes the triggers

formula trigger

An action that occurs and kicks off a formula. Triggers can be events set up on an element instance

formula variable

Variables that represent either element instances or specific values that must be supplied for each formula instance.

H

hub

A collection of elements where the APIs of those elements have been normalized to a standard defined by the Hub.

M

map

The process of associating objects within a vendor's resource to objects in a common resource so the vendor objects can be transformed.

N

normalize

Relates to transforming information from vendors to a common language within Cloud Elements.

O

oauth proxy

The OAuth Proxy feature gives you the capability to have multiple environments

one-to-many

Enables developers to write to one API to integrate multiple elements.

organization

The top level of the accounts and users hierarchy that represents the Cloud Elements customer.

organization administrator

The user that can manage accounts and is associated with the initial sign up with Cloud Elements.

P

payload

The data returned from an API response. Or

polling

An event option where Cloud Elements checks for changes to a resource in a configurable duration and captures the changed information

R

resource

An object or entity that can be accessed via a URI request.

T

transformation

The result of mapping an API provider resource to a common resource.

U

user

The third level of the accounts and users hierarchy that represents individual instances of elements and transformations.

V

virtual data resource (VDR)

A custom object, such as a contact, employee, or product that represents the source of truth for how your company views data about that object. Fields within the object are mapped to similar objects at API providers, enabling you to create integrations to the custom object.

W

webhooks

An event option where the service provider notifies Cloud Elements that changes to a resource occurred. Typically you must configure webhooks settings at the service provider prior to implementing webhooks for your authenticated element instance.