About Input Objects
Input objects can be described as "composable objects" because they include a set of input fields that define the object.
Input fields
| Name | Description |
|---|---|
| Account number. |
Example
{
"accountNumber": "abc123"
}AccountReferenceInput
The input type for the account reference.
Input fields
| Name | Description |
|---|---|
| The account number. |
| The namespace for the reference. |
| The reference value. |
Example
{
"accountNumber": "abc123",
"namespace": "abc123",
"value": "abc123"
}Input fields
| Name | Description |
|---|---|
| Internal account id (not account number). |
| The account number eg. A-FF15AE70. |
| Account Reference. |
| Bills (Shortcut). |
| Account or Billing name. |
| Business name. |
| Business identifier or number. |
| Device ID. |
| Location (Supply or Billing, full or partial, address or post code). |
| Meter Serial Number. |
| The portfolio number eg. P-A123B456. |
| Statements (Alias for bills). |
| URN Number. |
| The Account User ID (not account number). |
Example
{
"accountNumber": "abc123",
"portfolioNumber": "abc123",
"urn": "abc123",
"user": "abc123",
"account": "abc123",
"bill": "abc123",
"statements": "abc123",
"meterSerialNumber": "abc123",
"location": "abc123",
"billingName": "abc123",
"businessName": "abc123",
"businessNumber": "abc123",
"accountReferences": "abc123",
"device": "abc123"
}AccountUserDetailInput
Identifies an account user by a detail namespace and value.
Input fields
| Name | Description |
|---|---|
| The namespace of the account user detail. |
| The value of the account user detail. |
Example
{
"namespace": "abc123",
"value": "abc123"
}Input fields
| Name | Description |
|---|---|
| The time at which the note will appear to have been added (defaults to now). |
| The content of the note. |
| The relay id of the conversation that will be assigned to the bucket. |
| Is the note pinned, to make it clearer to the support user. |
Example
{
"conversationRelayId": "abc123",
"content": "abc123",
"addedAt": "2020-01-01T00:00:00.000Z",
"isPinned": true
}AddPropertyInput
Input type for adding a new property to an account.
Input fields
| Name | Description |
|---|---|
| The account number to add the property to. |
| The address of the property using the rich address format. |
Example
{
"accountNumber": "abc123",
"address": RichAddressInput
}Input fields
| Name | Description |
|---|---|
| Optional analyzer results from Neuralink. |
| The relay id of the conversation that will be assigned to the bucket. |
| A list of entries to add to the storyline. |
| The time the storyline was generated. |
| A list of knowledge article IDs to associate with the storyline. |
| The Neuralink request ID. |
| The summary of the storyline. |
| The topic of the storyline. |
| The Neuralink trigger ID that caused this storyline to be generated. |
Example
{
"conversationRelayId": "abc123",
"topic": "abc123",
"summary": "abc123",
"generatedAt": "2020-01-01T00:00:00.000Z",
"entries": InkStorylineEntryInput,
"neuralinkRequestId": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"knowledgeArticleIds": [1],
"analyzerResults": InkStorylineAnalyzerResultInput,
"triggerId": "abc123"
}Input fields
| Name | Description |
|---|---|
| An S3 virtual-hosted-style URL pointing to the recording file in the S3ARCHIVEBUCKET, e.g. https:// |
| The vendor's call leg ID, used to find the call participant and associate the recording with the correct call. |
Example
{
"vendorCallLegId": "abc123",
"archivedRecordingFileUri": URI
}Input fields
| Name | Description |
|---|---|
| The name of the bucket to assign the conversation to. |
| The relay id of the conversation that will be assigned to the bucket. |
Example
{
"conversationRelayId": "abc123",
"bucketName": "abc123"
}Input fields
| Name | Description |
|---|---|
| Unique slug identifier for the estimation group. |
| Supply point external identifier. |
| Datetime period start to look for supply point. |
Example
{
"estimationGroupCode": "abc123",
"supplyPointExternalId": "abc123",
"supplyPointPeriodStart": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| The list of external call recordings to associate with calls. |
Example
{
"recordings": ArchivedCallRecordingInput
}Input fields
| Name | Description |
|---|---|
| The account number to associate to the call. |
| The ID of the call. |
Example
{
"callId": "abc123",
"accountNumber": "abc123"
}Input fields
| Name | Description |
|---|---|
| SSO access token for the chosen provider authentication. |
| Provider code from user login used for SSO. |
| SSO token expiry for the provider's authentication (integer in seconds). |
| ID of the device in the external provider system. |
| Full redirect URI (including all query string parameters) from the result of an OAuth 2.0 flow. |
| SSO refresh token for the chosen provider authentication. |
| State from user login used for SSO. |
Example
{
"accessToken": "abc123",
"authorizationCode": "abc123",
"refreshToken": "abc123",
"expiresIn": 1,
"state": "abc123",
"providerDeviceId": "abc123",
"redirectUri": "abc123"
}BackendScreenEventInput
Input for a backend action.
Input fields
| Name | Description |
|---|---|
| The ID of the action to perform. |
| List of key-value pairs (strings) to pass as parameters to the mutation. |
Example
{
"eventId": "abc123",
"params": BackendScreenParamInputType
}BackendScreenParamInputType
A key-value pair (both Strings) which is passed in parameters to a backend action.
Example
{
"key": "abc123",
"value": "abc123"
}Input fields
| Name | Description |
|---|---|
| The key of the business detail. |
| The value of the business detail. |
Example
{
"key": "abc123",
"value": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the call to add the metadata to. |
| List of metadata items to add to the call. |
Example
{
"callId": "abc123",
"metadata": CallMetadataItemInput
}Input fields
| Name | Description |
|---|---|
| Whether this metadata item should be hidden on the support site and kraken phone. |
| The key of the metadata item. |
| The value of the metadata item. |
Example
{
"key": "abc123",
"value": "abc123",
"hideOnSupportSite": true
}Input fields
| Name | Description |
|---|---|
| Brand codes to restrict suggested accounts. When provided, only accounts belonging to one of these brands are suggested for the caller. |
Example
{
"accountBrandCodes": ["abc123"]
}Input fields
| Name | Description |
|---|---|
| The account number of the item. |
| The end of the call window for the item. |
| The start of the call window for the item. |
| The metadata of the item. |
| The phone number of the item. |
Example
{
"phoneNumber": "abc123",
"callWindowStart": "2020-01-01T00:00:00.000Z",
"callWindowEnd": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123",
"metadata": {"key": "value"}
}Input fields
| Name | Description |
|---|---|
| The ID of the SmartFlex onboarding wizard to cancel. |
Example
{
"wizardId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The reason for closing the conversation. |
| The relay id of the conversation to close. |
Example
{
"conversationRelayId": "abc123",
"closeReason": "AGENT_CLOSED"
}Input fields
| Name | Description |
|---|---|
| The number of the Kraken account that the conversation is from. Required for Account User authorization. |
| The relay id of the live chat conversation. |
Example
{
"accountNumber": "abc123",
"liveChatConversationRelayId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The entire continuation URI returned by the vendor. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"continuationUri": "abc123"
}Input fields
| Name | Description |
|---|---|
| Account number that the device is registered to. |
| External reference in the third-party system to identify the device. |
| Postcode of the property (linked to the account) that the device is registered to. |
Example
{
"accountNumber": "abc123",
"postalCode": "abc123",
"externalDeviceIdentifier": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the call to connect the AI agent to. |
| Optional goal for the AI eligibility check. For example, 'submitmeterreading'. |
| Whether to infer the preferred language of the calling account. |
| Whether to infer the operations group attributes of the calling account. |
| The priority with which the call should be routed. A higher number corresponds to a higher routing priority. |
| List of routing attribute references to add to the call. For example, 'SKILL.ENERGY'. Each attribute should already have been created in Kraken. |
| A URL that defines the behaviour of the call when it is in the conference. If not set, audio configured in Kraken will be played to the caller. The URL must return a response that can be interpreted by the vendor handling the call.
For example, if the call is handled by Twilio, TwiML supported by a |
| Optional identifier (slug) of the work schedule associated with this AI agent call. When set, this is passed through to the AI agent so it can take work schedule availability into account during handovers. |
Example
{
"callId": "abc123",
"routingAttributes": ["abc123"],
"priority": 1,
"waitingBehaviourUrl": "abc123",
"inferLanguageAttribute": true,
"inferOperationsGroupAttributes": true,
"goal": "abc123",
"workScheduleIdentifier": "abc123"
}Input fields
| Name | Description |
|---|---|
| The code of the consent type. |
| The source of the consent event. |
| The value to update the consent to. |
Example
{
"consentTypeCode": "abc123",
"value": "ACCEPTED",
"source": "CONSUMER_SITE"
}Input fields
| Name | Description |
|---|---|
| |
| |
| Deprecated The 'clientMutationId' field is deprecated. |
|
Example
{
"filename": "abc123",
"accountNumber": "abc123",
"category": "NONE",
"clientMutationId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The account number to place a manual billing hold on. |
| The code of an active manual hold reason. |
| The start of the hold validity period. Defaults to the current time if not provided. |
| The end of the hold validity period. |
Example
{
"accountNumber": "abc123",
"reasonCode": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| The account number. |
| Pin the note to account. |
| The note to add. |
| When to unpin the note from the account. |
Example
{
"accountNumber": "abc123",
"note": "abc123",
"isPinned": true,
"unpinAt": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| The campaign ID. |
| The items to add. |
Example
{
"campaignId": "abc123",
"campaignItems": CampaignItemInput
}Input fields
| Name | Description |
|---|---|
| Restrictions used to narrow the accounts suggested for the caller. These are supplied by the upstream IVR flow, which knows contextual information about the call (for example, which brand's phone number was dialled). |
| The phone number that the call is from. |
| The phone number that the call is to. |
| The Voice vendor managing the call. |
| The ID of the call in the vendor's system. |
Example
{
"fromPhoneNumber": "abc123",
"toPhoneNumber": "abc123",
"vendor": "TWILIO",
"vendorCallId": "abc123",
"callerIdentificationRestrictions": CallerIdentificationRestrictionsInput
}Input fields
| Name | Description |
|---|---|
| The number of the Kraken account that the message was from. |
| The channel type the posted message should be treated as in Ink. It is used to determine how the message should be processed and what channel-specific features are available for this message. |
| An optional parameter where we can pass the generic message headers if it has one Email channel tries to get the value |
| An arbitrary, unique ID for this message. This must be unique for each message that is supplied using the same organisation; collisions between messages provided by different organisations are tolerated. Stored as vendor_id. |
| The message to ingest. |
| When the message occurred in the system of origin. |
| An optional vendor value to denote which system it originated from. If no vendor is passed, we will get the default generic vendor from the setting called INKDEFAULTGENERICMESSAGEAPI_VENDOR. |
Example
{
"accountNumber": "abc123",
"channel": "EMAIL",
"messageId": "abc123",
"newMessage": InkMessageInput,
"vendor": "abc123",
"messageHeaders": {"key": "value"},
"occurredAt": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| The number of the Kraken account that the message was from. |
| An arbitrary, unique ID for this message. Used in combination with vendor to guarantee uniqueness of the message in Ink. Stored as vendor_id. |
| The message to ingest. |
| When the message occurred in the system of origin. |
| An optional value that is used in conjunction with message_id to guarantee uniqueness of a message in Ink. It is usually name of the system the message originated from. If not supplied, Ink provides a default system value. |
Example
{
"accountNumber": "abc123",
"messageId": "abc123",
"newMessage": InkMessageInput,
"vendor": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| List of post events to create. |
Example
{
"events": PostEventInput
}CreateShellAccountInput
Input fields for creating a shell account.
Input fields
| Name | Description |
|---|---|
| First line of the billing address. |
| Second line of the billing address. |
| Third line of the billing address. |
| Fourth line of the billing address. |
| Fifth line of the billing address. |
| The name to use for billing purposes. |
| Day to fixed bill on if billingperiodlength set. |
| For fixed billing accounts only, the length of their billing period. Can be MONTHLY or QUARTERLY. |
| Month to start billing from if billingperiodlength set to QUARTERLY or the multiplier is > 1. |
| For fixed billing accounts only, the number the period length is to be multiplied by to get the total period length, i.e. for billing every second month, select 2 combined with a billing period length MONTHLY. Can't be > 1 for quarterly billing. |
| The billing address postcode. |
| This must be a string-ified version of the JSON representation of RichAddressInput type. |
| The brand to associate the account with. |
| The type of business for business accounts. |
| A unique identifier for the client performing the mutation. |
| The name of the company for business accounts. |
| The company registration number for business accounts. |
| The user's date of birth. |
| The user's email address. |
| The user's family (last) name. |
| The user's given (first) name. |
| Whether this is a business account. |
| The user's landline phone number. |
| The user's mobile phone number. |
| The password for the new account user. |
| Token required to set a password during account creation. |
| The portfolio number to associate the account with. |
| The tax number for the business account. |
| Unique reference number from a 3rd party enrolment. |
Example
{
"clientMutationId": "abc123",
"portfolioNumber": "abc123",
"givenName": "abc123",
"familyName": "abc123",
"billingName": "abc123",
"email": "abc123",
"mobile": "abc123",
"landline": "abc123",
"brand": "abc123",
"dateOfBirth": "2020-01-01",
"billingAddressLine1": "abc123",
"billingAddressLine2": "abc123",
"billingAddressLine3": "abc123",
"billingAddressLine4": "abc123",
"billingAddressLine5": "abc123",
"billingPostcode": "abc123",
"billingRichAddress": "abc123",
"billingPeriodLength": "abc123",
"billingPeriodMultiplier": 1,
"billingPeriodDay": 1,
"billingPeriodMonth": 1,
"isBusinessAccount": true,
"companyName": "abc123",
"companyNumber": "abc123",
"businessType": "abc123",
"taxNumber": "abc123",
"password": "abc123",
"passwordUpdateToken": "abc123",
"urn": "abc123"
}Input fields
| Name | Description |
|---|---|
| Account number. |
| The most recently registered device of this type will be de-authenticated. |
Example
{
"accountNumber": "abc123",
"deviceType": "BATTERIES"
}Input fields
| Name | Description |
|---|---|
| Device ID. |
Example
{
"deviceId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The account number associated with the removed AccountReference. |
| The namespace associated with the removed AccountReference. |
Example
{
"accountNumber": "abc123",
"namespace": "abc123"
}Input fields
| Name | Description |
|---|---|
| Account number. |
Example
{
"accountNumber": "abc123"
}Input fields
| Name | Description |
|---|---|
| The provider that delivers push notifications for the application, e.g. 'PINPOINT' or 'FCM'. Disambiguates apps that share a bundle ID and service but use different providers. Defaults to 'PINPOINT' when omitted. |
| Device push notification token. |
Example
{
"token": "abc123",
"externalProvider": "abc123"
}Input fields
| Name | Description |
|---|---|
| Supply point external identifier. |
| Datetime period start to look for supply point. |
Example
{
"supplyPointExternalId": "abc123",
"supplyPointPeriodStart": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| Namespace of the detail. |
| Value of the detail. |
Example
{
"namespace": "abc123",
"value": "abc123"
}Input fields
| Name | Description |
|---|---|
| Auxiliary device variant id. |
| Unique device variant id. |
Example
{
"deviceVariantId": "abc123",
"auxDeviceVariantId": "abc123"
}Input fields
| Name | Description |
|---|---|
| Account number. |
| The authentication details required given the chosen provider. |
| The device type specific details required for registering a device. |
| The device type to be registered - batteries, electric vehicles, heat pumps or thermostats. |
| The ID of the property the device belongs to. |
| The provider used to authenticate the device. |
Example
{
"accountNumber": "abc123",
"propertyId": 1,
"deviceType": "BATTERIES",
"provider": "BMW",
"deviceDetails": DeviceDetailsInput,
"authentication": AuthenticationInput
}ElectricityFiltersInput
Filter measurements by electricity parameters.
Input fields
| Name | Description |
|---|---|
| The identifier of the specific device associated to this reading. |
| The identifier of the market supply point associated to this reading. |
| Reading direction is based on the utility generated or consumed by the customer. |
| The frequency of the reading. |
| |
| The identifier of the register associated to this reading. |
Example
{
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "abc123",
"deviceId": "abc123",
"readingDirection": "CONSUMPTION",
"registerId": "abc123",
"readingQuality": "ACTUAL"
}Input fields
| Name | Description |
|---|---|
| Identifier for the call to enqueue, as an integer or a UUID. |
| Whether to infer the preferred language of the calling account. |
| Whether to infer the operations group attributes of the calling account. |
| The priority with which the call should be routed. A higher number corresponds to a higher routing priority. |
| List of routing attribute references to add to the call. For example, 'SKILL.ENERGY'. Each attribute should already have been created in Kraken. |
| A URL that defines the behaviour of the call when it is enqueued and the caller is waiting. If not set, audio configured in Kraken will be played to the caller. The URL must return a response that can be interpreted by the vendor handling the call. For
example, if the call is handled by Twilio, TwiML supported by a |
Example
{
"callId": "abc123",
"routingAttributes": ["abc123"],
"priority": 1,
"waitingBehaviourUrl": "abc123",
"inferLanguageAttribute": true,
"inferOperationsGroupAttributes": true
}Input fields
| Name | Description |
|---|---|
| Account number that requested to escalate the conversation. |
| The relay id of the conversation to escalate to the team leader. |
Example
{
"accountNumber": "abc123",
"conversationRelayId": "abc123"
}Input fields
| Name | Description |
|---|---|
| Payment instruction ID. |
Example
{
"paymentInstructionId": 1
}Input fields
| Name | Description |
|---|---|
| The channel of the contact. |
| The name of the file. |
Example
{
"channel": "EMAIL",
"filename": "abc123"
}InkEmailMessageInput
This type is used to create an email.
Input fields
| Name | Description |
|---|---|
| Message attachments. |
| The carbon copy (cc) email addresses the message was sent to. |
| The email address the message was sent from. |
| The content of the message, as plain text. |
| The S3 bucket in which the original email is stored. |
| The S3 key of the original email. |
| The email subject/title. |
| The email addresses the message was sent to. |
Example
{
"plainTextContent": "abc123",
"attachments": InkGenericMessageAttachmentInput,
"subject": "abc123",
"fromAddress": Email,
"toAddresses": Email,
"ccAddresses": [Email],
"s3Bucket": "abc123",
"s3Key": "abc123"
}Input fields
| Name | Description |
|---|---|
| The S3 bucket of the attachment. |
| The S3 key of the attachment. |
Example
{
"s3Key": "abc123",
"s3Bucket": "abc123"
}InkGenericMessageInput
This type is used to create an generic message.
Input fields
| Name | Description |
|---|---|
| Message attachments. |
| The identity the message was sent from. |
| The content of the message, as plain text. |
| The identity the message was sent to. |
Example
{
"plainTextContent": "abc123",
"attachments": InkGenericMessageAttachmentInput,
"fromHandle": "abc123",
"toHandle": "abc123"
}InkLiveChatMessageInput
This type is used to create a live chat message.
Input fields
| Name | Description |
|---|---|
| Message attachments. |
| The identity the message was sent from. |
| The content of the message, as plain text. |
Example
{
"plainTextContent": "abc123",
"attachments": InkGenericMessageAttachmentInput,
"fromHandle": "abc123"
}InkMessageInput
An Ink message used as an input.
This is intended to be morally equivalent to a tagged union; exactly one of the properties provided here is expected to be provided.
At current, only a few channels are provided. This is intended to be a backwards-compatible extension point to allow other message input types to be added in the future.
Input fields
| Name | Description |
|---|---|
| Input for Email type messages. |
| Input for Generic type messages. |
| Input for Live Chat type messages. |
| Input for Post type messages. |
Example
{
"liveChat": InkLiveChatMessageInput,
"generic": InkGenericMessageInput,
"email": InkEmailMessageInput,
"post": InkPostMessageInput
}InkPostMessageInput
This type is used to create an inbound post.
Input fields
| Name | Description |
|---|---|
| The account number that the letter was sent from. |
| Message attachments. |
| Notes on the letter. |
| The content of the message, as plain text. |
Example
{
"plainTextContent": "abc123",
"attachments": InkGenericMessageAttachmentInput,
"accountNumber": "abc123",
"notes": "abc123"
}InkSendMessageInput
A message that is to be sent. Currently supports only email messages.
Input fields
| Name | Description |
|---|---|
| Input for email type message. |
Example
{
"email": InkEmailMessageInput
}Input fields
| Name | Description |
|---|---|
| The type of analyzer that produced this result. |
| The analyzer result data, structure depends on analyzertype and schemaversion. |
| The schema version of the analyzer result data (e.g., 'v1'). |
Example
{
"analyzerType": "DIAGNOSTIC_QUESTIONS",
"schemaVersion": "abc123",
"data": {"key": "value"}
}Input fields
| Name | Description |
|---|---|
| The content of the storyline entry. |
| The optional related object ID of the entry. |
| The type of the storyline entry. |
| Whether this entry is identified as the root cause of the issue. |
| The datetime when the storyline entry occurred. |
| Optional URL related to the storyline entry. |
Example
{
"contentId": 1,
"entryType": "INBOUND_MESSAGE",
"occurredAt": "2020-01-01T00:00:00.000Z",
"content": "abc123",
"url": "abc123",
"isRootCause": true
}Input fields
| Name | Description |
|---|---|
| UUID of the device. |
| Whether solar curtailment is enabled for this integrated inverter device. |
Example
{
"deviceId": "abc123",
"isSolarCurtailmentEnabled": true
}Input fields
| Name | Description |
|---|---|
| The name of the bucket to move the conversation to. |
| The relay id of the conversation that will be moved to the bucket. |
| Whether to unassign from user buckets. Defaults to False (only unassign from team buckets). |
Example
{
"conversationRelayId": "abc123",
"bucketName": "abc123",
"unassignFromUsers": true
}Input fields
| Name | Description |
|---|---|
| Account number. |
| The OCPP authentication details. |
Example
{
"accountNumber": "abc123",
"details": "abc123"
}ObtainJSONWebTokenInput
The input type for obtaining a Kraken Token (JWT).
The currently supported inputs are: - account user email/password combination - account user API key - organization live secret key - pre-signed key - refresh token
Input fields
| Name | Description |
|---|---|
| API key of the account user. Use standalone, don't provide a second input field. |
| The response from the CAPTCHA challenge. Use with 'email' and 'password' fields. |
| Email address of the account user. Use with 'password' field. Deprecated The 'email' field is deprecated. |
| Live secret key of an third-party organization. Use standalone, don't provide a second input field. |
| Password of the account user. Use with 'email' field. Deprecated The 'password' field is deprecated. |
| Short-lived, temporary key (that's pre-signed). Use standalone, don't provide a second input field. |
| The refresh token that can be used to extend the expiry claim of a Kraken token. Use standalone, don't provide a second input field. |
Example
{
"APIKey": "abc123",
"organizationSecretKey": "abc123",
"preSignedKey": "abc123",
"refreshToken": "abc123",
"email": "abc123",
"password": "abc123",
"captchaResponse": "abc123"
}ObtainLongLivedRefreshTokenInput
The input type for obtaining a long-lived refresh token.
Input fields
| Name | Description |
|---|---|
| The Kraken Token that will be used to generate the long-lived refresh token. |
Example
{
"krakenToken": "abc123"
}Input fields
| Name | Description |
|---|---|
| Account number of the account to update. |
| The language preference to set for the account, from the available options. |
Example
{
"accountNumber": "abc123",
"optionsLanguagePreference": "ENGLISH"
}Input fields
| Name | Description |
|---|---|
| Explanation or context for the event. |
| Unique identifier for this event from the external vendor, if provided. Used for deduplication so that requests can be safely retried without creating duplicate events. |
| Type of post event (ie. 'delivered', 'returned', 'failed'). |
| Unique ID of the message (ie. letter or document) that this post event relates to. |
| The date/time that the post event occurred, if provided. |
Example
{
"messageId": "abc123",
"eventType": "abc123",
"description": "abc123",
"timestamp": "2020-01-01T00:00:00.000Z",
"eventId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The day of the week. |
| The maximum value. |
| The minimum value. |
| Time of day this change should apply. Format: HH:MM. |
Example
{
"dayOfWeek": "MONDAY",
"time": "00:00:00.000Z",
"min": "1.0",
"max": "1.0"
}Input fields
| Name | Description |
|---|---|
| Register a push notification binding. A push notification binding connects an account user to a specific application running on a specific device through a 'registration token' (Android) or 'device token' (iOS). Using this binding we can send push notifications to the account user's devices. |
| The time at which the push notification binding expires. |
| The provider that delivers push notifications for the application, e.g. 'PINPOINT' or 'FCM'. Disambiguates apps that share a bundle ID and service but use different providers. Defaults to 'PINPOINT' when omitted. |
| The push notification service the application is registered with. For iOS applications this will be 'APNS' and for Android applications this will be 'GCM'. For iOS Sandbox applications, the value is 'APNS_SANDBOX'. |
| Device push notification token. |
Example
{
"token": "abc123",
"bundleId": "abc123",
"service": "abc123",
"externalProvider": "abc123",
"expiresAt": "2020-01-01T00:00:00.000Z"
}Input fields
| Name | Description |
|---|---|
| The campaign ID. |
| The IDs of the items to remove. |
Example
{
"campaignId": "abc123",
"campaignItemIds": "abc123"
}RequestPasswordResetInput
Input type for the RequestPasswordReset mutation.
Input fields
| Name | Description |
|---|---|
| The URL from which the reset was requested. If supported, it is used as the base URL to generate the reset link in the email sent to the user. |
| The email requesting a password reset email. Provide either this or the userNumber. |
| The number of the user requesting a password reset email. Provide either this or the email. |
Example
{
"email": "abc123",
"userNumber": "abc123",
"baseUrl": "abc123"
}Input fields
| Name | Description |
|---|---|
| The account number. |
| The ID of the billing document to request a printed bill for. |
Example
{
"billingDocumentId": "abc123",
"accountNumber": "abc123"
}Input fields
| Name | Description |
|---|---|
| The new password. |
| The token from the presigned url. |
| A base64 bytestring representing the user's unique id. |
Example
{
"newPassword": "abc123",
"userId": "abc123",
"token": "abc123"
}RichAddressInput
A postal address.
This data model is based on the structure used by Google's libaddressinput library—so you can use it, or other libraries that use its data model and reference data, to accept input.
All fields can be blank, except for country which must
always be supplied.
This type is the input equivalent of RichAddressType; all
the fields here are semantically equivalent to fields
there, except where documented.
Input fields
| Name | Description |
|---|---|
| Top-level administrative subdivision, e.g. US state, AU state/territory, NZ region, IT region, JP prefecture. |
| ISO 3166-1 alpha-2 code of the country this address belongs
to, e.g. |
| Identifier used by the local postal service for this address, e.g. AU DPID, GB postcode + Delivery Point Suffix, US Zip-9 + Delivery Point. This is the value that gets encoded in the barcode printed on the envelope by large-volume bulk mail providers. |
| UK dependent localities, or neighbourhoods or boroughs in some other locations. |
| Identifier for this address in its territory's official address register, e.g. DAR ID in DK, UPRN in GB, G-NAF ID in AU. |
| City or town portion of an address, e.g. US city, AU suburb/town, NZ suburb and city/town, IT comune, UK post town. |
| A personal name. |
| The name of a business or organisation. |
| Postal code (ZIP code in the US). |
| Sorting code, e.g. FR CEDEX code. This field is not used in many countries. |
| At most one of this field and This is a divergence from |
| At most one of this field and
|
Example
{
"name": "abc123",
"organization": "abc123",
"streetAddress": "abc123",
"structuredStreetAddress": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"dependentLocality": "abc123",
"locality": "abc123",
"administrativeArea": "abc123",
"postalCode": "abc123",
"sortingCode": "abc123",
"country": "abc123",
"deliveryPointIdentifier": "abc123",
"geographicalId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}SelectVehicleOrChargePointInput
Options for selecting the user's vehicle or charge point.
Input fields
| Name | Description |
|---|---|
| User selected integration option. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedIntegration": "ELECTRIC_VEHICLE"
}Input fields
| Name | Description |
|---|---|
| The ID of the selected option from the list. |
| The ID of the SmartFlex onboarding step to complete. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"selectedOption": "abc123"
}Input fields
| Name | Description |
|---|---|
| The message to send. |
| The relay ID of the message we want to reply to. |
| Whether to close the conversation. |
| Whether to attach the full reply thread to an email reply. |
Example
{
"newMessage": InkSendMessageInput,
"shouldCloseConversation": true,
"replyToMessageRelayId": "abc123",
"useFullReplyThread": true
}Input fields
| Name | Description |
|---|---|
| The smart control action, i.e. suspend or unsuspend. |
| The ID of the device. |
Example
{
"deviceId": "abc123",
"action": "SUSPEND"
}Input fields
| Name | Description |
|---|---|
| The ID of the device. |
| The mode of the schedule. |
| The schedule with the preference details. |
| The unit of the min and max values in the preferences schedule. |
Example
{
"deviceId": "abc123",
"mode": "CHARGE",
"unit": "CELSIUS",
"schedules": PreferencesScheduleInput
}Input fields
| Name | Description |
|---|---|
| The account number associated with the device. |
| The ID of the device to re-authenticate. |
| The property where the device is located/charged. |
Example
{
"accountNumber": "abc123",
"propertyId": 1,
"deviceId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The account to which the device should be registered. |
| The property where the device is located/charged. |
Example
{
"accountNumber": "abc123",
"propertyId": 1
}TargetInput
Input for specifying which target to query billing configurations for.
Exactly one of accountnumber, portfolionumber, or ledger_id must be provided.
Input fields
| Name | Description |
|---|---|
| Account number. |
| Supplementary ledger ID. |
| Portfolio number. |
Example
{
"accountNumber": "abc123",
"portfolioNumber": "abc123",
"ledgerId": "abc123"
}Input fields
| Name | Description |
|---|---|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
Example
{
"emailFormat": "abc123",
"isUsingInvertedEmailColours": true,
"fontSizeMultiplier": 1.0,
"isOptedInMeterReadingConfirmations": true,
"isOptedInToSmsMessages": true,
"preferredHoldMusic": "abc123",
"isOptedInToClientMessages": true,
"isOptedInToOfferMessages": true,
"isOptedInToRecommendedMessages": true,
"isOptedInToUpdateMessages": true,
"isOptedInToThirdPartyMessages": true,
"clientMutationId": "abc123"
}Input fields
| Name | Description |
|---|---|
| The boost action. |
| Device ID. |
Example
{
"deviceId": "abc123",
"action": "BOOST"
}UpdateCommsDeliveryPreferenceInput
Input fields for updating comms delivery preferences for an account
Input fields
| Name | Description |
|---|---|
| |
|
Example
{
"accountNumber": "abc123",
"commsDeliveryPreference": "EMAIL"
}Input fields
| Name | Description |
|---|---|
| Device ID. |
| Whether or not the device grid export is enabled. |
Example
{
"deviceId": "abc123",
"enabled": true
}Input fields
| Name | Description |
|---|---|
| The ID of the device to update. |
| Whether to enable charging duration capping. |
Example
{
"deviceId": "abc123",
"enabled": true
}Input fields
| Name | Description |
|---|---|
| The message to set the tags on. |
| The tag names to set on the message. |
| The tag code to set on the message. |
| The tag version to set on the message. |
Example
{
"messageRelayId": "abc123",
"tagNames": "abc123",
"taggerCode": "abc123",
"taggerVersion": "abc123"
}Input fields
| Name | Description |
|---|---|
| |
| User details. |
| |
| |
| |
| A free text field to help identifying the customer (e.g. for a job title). |
| Because this field is clearable, null and the empty string are treated differently; passing null or omitting the field leaves the value as-is, but explicitly passing an empty string clears this value. |
| Because this field is clearable, null and the empty string are treated differently; passing null or omitting the field leaves the value as-is, but explicitly passing an empty string clears this value. |
| How the user would like us to address them (e.g. 'she/her', 'they/them'). Because this field is clearable, null and the empty string are treated differently; passing null or omitting the field leaves the value as-is, but explicitly passing an empty string clears this value. |
| The user's title. |
| The user for whom to perform the update. This is only needed when using an Organisation role. |
Example
{
"givenName": "abc123",
"familyName": "abc123",
"pronouns": "abc123",
"email": "abc123",
"mobile": "abc123",
"dateOfBirth": "2020-01-01",
"landline": "abc123",
"userId": "abc123",
"title": "abc123",
"label": "abc123",
"details": DetailsInputType
}Input fields
| Name | Description |
|---|---|
| The key of the user input, matching the key of the requested input. |
| The value provided by the user for this input. |
Example
{
"key": "abc123",
"value": "abc123"
}Input fields
| Name | Description |
|---|---|
| The ID of the SmartFlex onboarding step to complete. |
| A list of user input key-value pairs where each key should match the key of the requested input. |
| The ID of the SmartFlex onboarding wizard. |
Example
{
"wizardId": "abc123",
"stepId": "abc123",
"userInput": UserInput
}UtilityFiltersInput
Filter measurements by the given utility parameters.
Input fields
| Name | Description |
|---|---|
| Filter measurements by electricity parameters. |
Example
{
"electricityFilters": ElectricityFiltersInput
}Input fields
| Name | Description |
|---|---|
| Account number. |
| |
| |
| |
| |
|
Example
{
"accountNumber": "abc123",
"weekdayTargetTime": "abc123",
"weekdayTargetSoc": 1,
"weekendTargetTime": "abc123",
"weekendTargetSoc": 1,
"targetType": "abc123"
}