Scalars

Navixy Repository API defines these custom scalar types in addition to the standard GraphQL scalars. See GraphQL basics for the description of the predefined scalars (String, Int, Float, Boolean, ID).

DateTime

An ISO 8601arrow-up-right datetime string with timezone (RFC 3339arrow-up-right). Example: 2024-01-15T10:30:00Z.

Property
Value

Format

YYYY-MM-DDTHH:mm:ss.sssZ

Example

2025-01-15T14:30:00.000Z

Date

An ISO 8601arrow-up-right date string without time component (RFC 3339arrow-up-right). Example: 2024-01-15.

Property
Value

Format

YYYY-MM-DD

Example

2025-01-15

JSON

An arbitrary JSON value. Can be an object, array, string, number, boolean, or null.

Property
Value

Format

Any valid JSON

Example

{"key": "value", "count": 42}

GeoJSON

A GeoJSONarrow-up-right geometry object (RFC 7946arrow-up-right). Supports Point, LineString, Polygon, and other geometry types.

Property
Value

Format

GeoJSON geometry object

Example

{"type": "Point", "coordinates": [125.6, 10.1]}

Latitude

A geographic latitude coordinate in decimal degrees. Valid range: -90.0 to 90.0.

Property
Value

Format

-90.0 to 90.0

Example

37.7749

Longitude

A geographic longitude coordinate in decimal degrees. Valid range: -180.0 to 180.0.

Property
Value

Format

-180.0 to 180.0

Example

-122.4194

Locale

A BCP 47arrow-up-right language tag identifying a user locale. Example: en-US, ru-RU.

Property
Value

EmailAddress

An email address conforming to RFC 5322arrow-up-right. Example: user@example.com.

Property
Value

Format

user@domain

Example

user@example.com

HexColorCode

A hexadecimal color code. Supports 3-digit (#RGB) or 6-digit (#RRGGBB) format.

Property
Value

Format

#RRGGBB

Example

#FF5733

CountryCode

An ISO 3166-1arrow-up-right alpha-2 country code. Example: US, GB, ES.

Property
Value

Format

Two uppercase letters

Example

US

Code

A machine-readable identifier code.

Constraints:

  • Allowed characters: ASCII letters (a-z, A-Z), digits (0-9), underscore (_), dot (.), hyphen (-)

  • Must start with a letter or digit

  • Case-insensitive for uniqueness checks

  • Maximum length: 64 characters

Naming conventions:

  • System items: UPPER_SNAKE_CASE (e.g., DEVICE_TYPE, ACTIVE)

  • User items: any valid format (e.g., vehicle_car, sensor-v2)

Examples: DEVICE_TYPE, vehicle_car, status.active, sensor-v2, ABC123

Property
Value

Format

lowercase_snake_case

Example

vehicle_type

ScheduleData

A schedule data structure containing time intervals and recurrence rules.

Property
Value

Format

iCalendar-compatible JSON

JSON example:

Last updated

Was this helpful?