• What is Integration Server?
• Getting Started
  • Session management
  • Versioned calls
  • Interface versioning
  • Licensing
  • Unicode data
• Operations
• Reference
  • Data types
  • Request headers
  • Response headers
  • Errors
• History
  • Changelog
  • Version lookup

Data types

Integration Server uses the data types itemized in the following table. All encoding must be in UTF-8 or ISO-8859-1. Perceptive Software recommends UTF-8.

Data Type	Definition
Integer	Integer values are signed 32-bit integers with a value range from -2,147,483,648 through 2,147,483,647.
Long	Integration Server uses the Long data type for date/time values. The Long value is the precise date/time value expressed in milliseconds from the UNIX epoch (January 1, 1970). Negative numbers are used for date/time values before the epoch. The Long data type is a 64-bit integer with a value range from -9,223,372,036,854,775,808 through 9,223,372,036,854,775,807.
Boolean	Integration Server uses the Boolean data type as a flag to indicate a true or false value. Integration Server uses true and false, not 1 and 0 (zero).
String	The String data type is a string of characters to represent an item such as a name or a description.
Enumeration	Integration Server uses enumerations for data elements that have an exact set of possible values. For example, the possible values for the columnSortDirection enumeration are ASCENDING and DESCENDING. The values for enumerations are consistent throughout Integration Server.
Custom	Integration Server has a wide variety of custom data types. These data types are named to be easily understood, and are often comprised of multiple words joined using camel case, such as documentType or captureGroup. Note that the definition and data elements for custom data types may vary between Integration Server calls. You can find all definitions and descriptions for custom objects in the Operations section of this guide.