Skip to content

Schema Types

Query

Field Argument Type Description
getVisionLiveCall VisionLiveCallResult!
input GetVisionLiveCallInput!

Mutation

Field Argument Type Description
prepareVisionLiveCall VisionLiveCallResult!
input PrepareVisionLiveCallInput!

Objects

IntegrationEntityId

Field Argument Type Description
namespace String!
id ID!

LiveCallInvitation

Field Argument Type Description
type LiveCallInvitationType!
recipient String!

VisionLiveCall

Field Argument Type Description
id ID!
createdAt AWSDateTime!
createdBy String!
invitations [LiveCallInvitation!]
integrationEntityId IntegrationEntityId
callMetadataJSON AWSJSON
visionLiveLink String

VisionLiveCallResult

Field Argument Type Description
visionLiveCall VisionLiveCall!

Inputs

GetVisionLiveCallInput

Field Type Description
id ID!

IntegrationEntityIdInput

These two parts of the composite ID must be universally unique

Field Type Description
namespace String! Must be 10 or more characters - should be unique to your integration and must be a single, eternal, shared value across your entire integration.
id ID! Your actual ID within your system. Must be unique within the universe of IDs that share the above namespace.

LiveCallInvitationInput

Field Type Description
type LiveCallInvitationType!
recipient String!

PrepareVisionLiveCallInput

Field Type Description
integrationEntityId IntegrationEntityIdInput
invitations [LiveCallInvitationInput!]
callMetadataJSON AWSJSON

Enums

LiveCallInvitationType

Value Description
sms
email

Scalars

AWSDateTime

The AWSDateTime scalar type provided by AWS AppSync, represents a valid extended ISO 8601 DateTime string. In other words, this scalar type accepts datetime strings of the form YYYY-MM-DDThh:mm:ss.SSSZ. The scalar can also accept "negative years" of the form -YYYY which correspond to years before 0000. For example, "-2017-01-01T00:00Z" and "-9999-01-01T00:00Z" are both valid datetime strings. The field after the two digit seconds field is a nanoseconds field. It can accept between 1 and 9 digits. So, for example, "1970-01-01T12:00:00.2Z", "1970-01-01T12:00:00.277Z" and "1970-01-01T12:00:00.123456789Z" are all valid datetime strings. The seconds and nanoseconds fields are optional (the seconds field must be specified if the nanoseconds field is to be used). The time zone offset is compulsory for this scalar. The time zone offset must either be Z (representing the UTC time zone) or be in the format ±hh:mm:ss. The seconds field in the timezone offset will be considered valid even though it is not part of the ISO 8601 standard.

AWSJSON

The AWSJSON scalar type provided by AWS AppSync, represents a JSON string that complies with RFC 8259. Maps like "{\"upvotes\": 10}", lists like "[1,2,3]", and scalar values like "\"AWSJSON example string\"", "1", and "true" are accepted as valid JSON and will automatically be parsed and loaded in the resolver mapping templates as Maps, Lists, or Scalar values rather than as the literal input strings. Invalid JSON strings like "{a: 1}", "{'a': 1}" and "Unquoted string" will throw GraphQL validation errors.

Boolean

Built-in Boolean

ID

Built-in ID

String

Built-in String