Objects
Objects in GraphQL represent the resources you can access. An object can contain a list of fields, which are specifically typed.
API Site
Fields
| Name | Description |
|---|---|
|
Code name of the sensor. |
|
User determined name for a sensor. |
|
Whether or not a sensor is enabled. |
|
Sensor type (NTC). |
Example
{
"code": "abc123",
"displayName": "abc123",
"type": "ZIGBEE",
"enabled": true
}Fields
| Name | Description |
|---|---|
|
The API type effected by this brownout. |
|
For GraphQL APIs this will be a field identifier in the format |
|
The iso formatted datetime at which this brownout will end. |
|
The iso formatted datetime at which this brownout will take effect. |
|
The current status of this brownout. |
Example
{
"disablesRequestsTo": NonEmptyString,
"status": "SCHEDULED",
"apiType": "GRAPHQL",
"startsAt": NonEmptyString,
"endsAt": NonEmptyString
}APIBrownoutConnection
Paginator of API brownouts.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": APIBrownoutEdge,
"totalCount": 1,
"edgeCount": 1
}APIBrownoutEdge
A Relay edge containing a APIBrownout and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": APIBrownout,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Storage for the API client to submit any contextual information. |
|
The request's correlation id. |
|
|
|
|
|
Input data for the API call if any. |
|
Free field for the API caller to categorise their own operation name. This field can be used to filter entries on the UI. |
|
The response from the API call if any. |
Example
{
"id": "abc123",
"correlationId": "abc123",
"operationName": "abc123",
"inputData": {"key": "value"},
"response": {"key": "value"},
"context": {"key": "value"},
"createdAt": "2020-01-01T00:00:00.000Z"
}APIExceptionConnectionTypeConnection
Paginator of API exceptions.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": APIExceptionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}APIExceptionConnectionTypeEdge
A Relay edge containing a APIExceptionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": APIExceptionType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The category of the event. |
|
A JSON context to be provided with the event, if any. |
|
|
|
A description of the event. |
|
The type of the event. |
|
Example
{
"id": "abc123",
"eventType": "abc123",
"category": "abc123",
"description": "abc123",
"context": {"key": "value"},
"createdAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The content of the API Exception note. |
|
Timestamp of when the API Exception note was created. |
|
The ID of the API Exception note. |
Example
{
"id": "abc123",
"body": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The account number provided to the exception. |
|
The API calls associated with this exception if any. |
|
The user assigned to handle this exception if any. |
|
Category associated with this exception. |
|
Free field for the API caller to categorise a channel. This could be (but not limited to) the client's team that calleded the API, the name of the 'flow' the call belongs to, etc. |
|
Storage for the API client to submit any contextual information. |
|
|
|
The customer contact provided to the exception. |
|
The events associated with this exception if any. |
|
External identifier submitted by the API client to track this exception on their end. |
|
|
|
The key date associated with the exception, if available. |
|
Notes associated with this exception if any. |
|
The operations team assigned to this exception if any. |
|
The current priority for the API exception. |
|
The current resolution status for the API exception. |
|
The current resolution type for the API exception. |
|
The supply point identifier provided to the exception. |
|
Tags associated with this exception if any. |
|
The user id provided to the exception. |
Example
{
"id": "abc123",
"externalIdentifier": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"channel": "abc123",
"category": "UNKNOWN",
"accountNumber": "abc123",
"userId": 1,
"customerContact": "abc123",
"supplyPointIdentifier": "abc123",
"resolutionStatus": "ASSIGNED",
"resolutionType": "AUTOMATIC",
"priority": "LOW",
"apiCalls": [APICallType],
"events": [APIExceptionEventType],
"tags": "MOVE_IN",
"notes": [APIExceptionNoteType],
"operationsTeam": OperationsTeamType,
"context": {"key": "value"},
"keyDate": "2020-01-01",
"assignedUser": AssignedUserType
}AcceptGoodsQuote
The possible errors that can be raised are:
- KT-CT-8223: Unauthorized.
- KT-CT-8201: Received an invalid quoteId.
- KT-CT-8224: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Goods purchase created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"goodsPurchase": GoodsPurchase
}AcceptOfferForQuoting
Accept a quoting offer in an offer group.
The possible errors that can be raised are:
- KT-CT-12402: Unable to accept offer.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Accepted quoting offer. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"offer": OfferType
}AcceptTermsAndConditions
Record the terms have been accepted and progress the workflow.
Fields
| Name | Description |
|---|---|
|
Version of terms and conditions that were accepted. |
Example
{
"acceptedVersion": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountApplicationConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountApplicationConnectionTypeEdge
A Relay edge containing a AccountApplicationConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountApplicationType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Last day of the cooling off period. Barring changes or objections, the account will be gained on the next business day after this date. This value will only be returned for current applications. |
|
Date at which this account decided to switch to us. |
|
Whether this account application represents a migration into the current system or a regular gain. |
|
The source system for a migrated account. This could be the previous supplier or the previous account management system. |
|
Preferred supply start date. If null, it means ASAP. |
|
|
|
The sales subchannel used when signing up. This could for example be a price comparison site. |
|
Example
{
"status": "CURRENT",
"salesChannel": "abc123",
"salesSubchannel": "abc123",
"dateOfSale": "2020-01-01",
"coolingOffEndDate": "2020-01-01",
"isMigrated": true,
"migrationSource": "abc123",
"preferredSsd": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
Debit details. |
|
Credit details. |
|
Balance transfer ID. |
|
The reason for the balance transfer. |
Example
{
"id": "abc123",
"accountCharge": AccountChargeType,
"accountCredit": AccountCreditType,
"reason": "abc123"
}AccountCampaignConnectionTypeConnection
Paginator of Account Campaigns
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountCampaignConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountCampaignConnectionTypeEdge
A Relay edge containing a AccountCampaignConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountCampaignType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The date on which the associated campaign itself concludes. |
|
The date on which the account's participation in the campaign ends. |
|
The name of the campaign. |
|
The slug of the campaign. |
|
The date that the account's link to the campaign started. |
Example
{
"campaignExpiryDate": "2020-01-01",
"name": "abc123",
"slug": "abc123",
"expiryDate": "2020-01-01",
"startDate": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
A JSON object containing unstructured data about the account charge. |
|
The date and time the metadata was last updated. |
Example
{
"data": {"key": "value"},
"updatedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The climate change levy amount of the charge. |
|
The display note for the charge. |
|
The gross amount of the charge. |
|
The ID of the account charge. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The net amount of the charge. |
|
The note for the charge. |
|
The reason for the charge. |
|
The sales tax amount of the charge. |
Example
{
"id": "abc123",
"netAmount": 1,
"grossAmount": 1,
"salesTaxAmount": 1,
"cclAmount": 1,
"reason": "abc123",
"note": "abc123",
"displayNote": "abc123",
"metadata": AccountChargeMetadataType
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountConnectionTypeEdge
A Relay edge containing a AccountConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"data": {"key": "value"},
"updatedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"grossAmount": 1,
"netAmount": 1,
"salesTaxAmount": 1,
"note": "abc123",
"reason": "abc123",
"metadata": AccountCreditMetadataType
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountEventConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountEventConnectionTypeEdge
A Relay edge containing a AccountEventConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountEvent,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
The ID of the object |
|
Is the file ready for use / downloadable? |
|
Is the file uploaded to S3? |
|
Example
{
"id": "abc123",
"filename": "abc123",
"category": "abc123",
"isUploaded": true,
"isReady": true,
"fetchUrl": "abc123",
"sizeInBytes": 1
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountFileAttachmentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountFileAttachmentConnectionTypeEdge
A Relay edge containing a AccountFileAttachmentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountFileAttachment,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether account is eligible to register devices with Intelligent Octopus or not. |
Example
{
"isEligibleForIo": true
}Fields
| Name | Description |
|---|---|
|
The number of loyalty points the account (or user with the given id) has. |
|
The net monetary value of the loyalty points in the currency's sub-units. |
Example
{
"loyaltyPoints": 1,
"totalMonetaryAmount": 1
}Example
{
"body": "abc123",
"isPinned": true,
"createdAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountPaymentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountPaymentConnectionTypeEdge
A Relay edge containing a AccountPaymentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountPaymentType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Amount of payment in pence |
|
|
|
The date this payment is scheduled to be debited |
|
The payment instruction that was used to make this payment. |
|
|
|
The current status of the payment. |
|
Surcharge amount generated by this payment. |
|
The transaction type of the payment. |
Example
{
"id": "abc123",
"amount": 1,
"paymentDate": "2020-01-01",
"reference": "abc123",
"transactionType": "DD_FIRST_COLLECTION",
"status": "SCHEDULED",
"paymentInstruction": PaymentInstructionType,
"surchargeAmount": 1
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Example
{
"namespace": "abc123",
"value": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z",
"account": AccountType
}Fields
| Name | Description |
|---|---|
|
Reminder content. |
|
When the reminder is due. |
|
The reminder type. |
Example
{
"reminderType": "AD_HOC",
"content": "abc123",
"dueAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountReminderConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountReminderConnectionTypeEdge
A Relay edge containing a AccountReminderConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Reminder,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountRepaymentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountRepaymentConnectionTypeEdge
A Relay edge containing a AccountRepaymentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountRepaymentType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Amount of payment in pence |
|
|
|
The date this payment is scheduled to be debited |
|
The current status of the repayment. |
Example
{
"id": "abc123",
"amount": 1,
"paymentDate": "2020-01-01",
"status": "REQUESTED"
}AccountSearchItemType
A single accout search hit
Fields
| Name | Description |
|---|---|
|
The account found. |
|
How well the account matched the search terms. |
Example
{
"account": AccountType,
"score": "1.0"
}AccountType
The account object can be one of several attached to a Portfolio (which usually has an AccountUser which is used to authenticate access to the Portfolio's accounts). Typically a person has a single account attached to a portfolio and properties on the same account will appear on the same bill. Where separate bills are desired, multiple accounts are created and added to the same portfolio of accounts.
Fields
| Name | Description |
|---|---|
|
The type of account. |
|
List of active hardship agreements for the user when isinhardship is True. |
|
The referral schemes currently active for this account. |
|
The billing address of this account, stored in the new libaddressinput-based format. Note that |
|
Fetch annual statements for the account. |
|
Applications by this account to become our customer. More recent applications will be listed first. |
|
Assistance agreements for account. |
|
The current account balance. |
|
Fetch a specific issued bill (invoice/statement) for the account. |
|
The billing address of the account. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The billing email of the account. |
|
The billing name of the account. |
|
Information about the account's billing cycle. |
|
The postcode of the billing address. |
|
The billing sub name of the account. |
|
Fetch issued bills (invoices/statements) for the account. |
|
The brand of the account. |
|
Business info related to a business account. |
|
The company type of a business account. Deprecated The 'businessType' field is deprecated. |
|
The campaigns associated with an account. |
|
Whether an account can be withdrawn. |
|
Whether an account can change their payment schedule. |
|
Whether on not the meter readings can be input via IVR. |
|
Data about whether or not an account can modify their payments. |
|
Whether the account is eligible for tariff renewal. |
|
Whether the account can request a credit refund. |
|
The method the account has specified they prefer we contact them. |
|
Deprecated The 'communicationDeliveryPreference' field is deprecated. |
|
The complaints associated with an account. |
|
Consents linked to this account. |
|
Contribution agreements for account. |
|
The number of days around a move out a final meter reading can be given for. |
|
The datetime that the account was originally created. |
|
The current estimated supply start day on an account. |
|
Debt collection proceedings for account. |
|
The direct debit instructions of the account |
|
The document accessibility preference of the account. |
|
The earliest possible supply start day on an account. |
|
The electricity agreements belonging to the account |
|
Whether the account is eligible to apply for Warm Home Discount as part of the Scottish Broader Group. |
|
The account events that were recorded for the account. |
|
Files attached to this account. |
|
The gas agreements belonging to the account |
|
The green benefits achieved over the lifetime of an account. |
|
Whether or not the account has active collections proceedings. |
|
Whether or not the account has an active Dunning process. |
|
|
|
Whether or not an account is eligible for an electricity reading incentive. Deprecated The 'isEligibleForElectricityReadingIncentive' field is deprecated. |
|
Whether or not an account is eligible for a gas reading incentive. Deprecated The 'isEligibleForGasReadingIncentive' field is deprecated. |
|
Whether or not the account is a part of a migration for which we want to switch supplier without customer actions. |
|
True if there is an active Hardship Agreement for this account. False otherwise. |
|
The latest possible supply start day on an account. |
|
Ledgers provide the foundation of bookkeeping functionality. Similar to a bank account, they allow us to keep track of financial activity on a particular customer account. |
|
Retrieve all market supply agreements under this account. Note that when |
|
The maximum amount a customer is allowed to request as a refund and the reason why that's the maximum amount. |
|
Metadata associated with the account. |
|
Notes for the account. |
|
A code that uniquely identifies the account. |
|
The operations team that the account belongs to. |
|
The current account overdue balance. |
|
Files attached to this account. |
|
Paginated payment forecasts for an account. Starts from today's date (inclusive). The interface supports |
|
Results of the latest review of the account's payments. |
|
A list displaying the payment forecast for an account. The list starts from today's date (inclusive). Deprecated The 'paymentForecast' field is deprecated. |
|
The payment instructions of the account. |
|
The payment plans that have been created for this account. |
|
The schedules that describe how we would expect to take payments for an account on a given month. |
|
The payments made into an account from a payment instruction. |
|
The portfolio this account is linked to. |
|
The language that the account preferred for communications. |
|
Expected balance in a year's time. |
|
Properties linked to the account now and in the future. |
|
|
|
Top up payment amount in pence that we recommend for an account. |
|
Account references linked to this account. |
|
The referrals created by this account. |
|
Number of referrals created by this account. |
|
The reminders associated with an account. |
|
The repayments that have been requested for this account. |
|
Details about the eligibility status for requesting a refund. |
|
The rewards applied to this account. |
|
Whether the account's payment should be adjusted. |
|
The interest of an account in procuring smart meters. |
|
The reason why the account holder is not interested in having a smart meter installed. |
|
List of billing address lines. |
|
The current status of the account. |
|
Only relevant for Kraken instances that support daily tracker tariffs. Returns null if not applicable. |
|
Fetch transactions that have taken place on the account. |
|
Unique reference number from a 3rd party enrolment. |
|
|
|
Get details about warm home discount applications and records. |
Example
{
"id": "abc123",
"number": "abc123",
"status": "PENDING",
"paymentSchedules": PaymentScheduleConnectionTypeConnection,
"users": AccountUserType,
"complaints": ComplaintConnectionTypeConnection,
"brand": "abc123",
"balance": 1,
"overdueBalance": 1,
"urn": "abc123",
"billingName": "abc123",
"billingSubName": "abc123",
"billingEmail": "abc123",
"billingAddress": "abc123",
"billingAddressLine1": "abc123",
"billingAddressLine2": "abc123",
"billingAddressLine3": "abc123",
"billingAddressLine4": "abc123",
"billingAddressLine5": "abc123",
"billingAddressPostcode": "abc123",
"billingCountryCode": "abc123",
"billingDeliveryPointIdentifier": "abc123",
"splitBillingAddress": ["abc123"],
"address": RichAddressType,
"portfolio": PortfolioType,
"ledgers": [LedgerType],
"metadata": [Metadata],
"canRequestRefund": true,
"requestRefundEligibility": RequestRefundEligibilityType,
"payments": AccountPaymentConnectionTypeConnection,
"repayments": AccountRepaymentConnectionTypeConnection,
"paymentPlans": PaymentPlanConnectionTypeConnection,
"paymentForecast": [PaymentForecastType],
"paginatedPaymentForecast": PaymentForecastConnectionTypeConnection,
"referrals": ReferralConnectionTypeConnection,
"referralsCreated": 1,
"rewards": [RewardType],
"activeReferralSchemes": ReferralSchemeTypes,
"transactions": TransactionConnectionTypeConnection,
"provisionalTransactions": ProvisionalTransactionConnectionTypeConnection,
"annualStatements": AnnualStatementConnectionTypeConnection,
"bills": BillConnectionTypeConnection,
"billingOptions": BillingOptionsType,
"bill": BillInterface,
"directDebitInstructions": DirectDebitInstructionConnectionTypeConnection,
"paymentMethods": PaymentInstructionConnectionTypeConnection,
"events": AccountEventConnectionTypeConnection,
"applications": AccountApplicationConnectionTypeConnection,
"accountType": "BUSINESS",
"businessType": "SOLE_TRADER",
"business": BusinessType,
"commsDeliveryPreference": "EMAIL",
"communicationDeliveryPreference": "abc123",
"documentAccessibility": "LARGE_PRINT",
"references": [AccountReferenceType],
"fileAttachments": [AccountFileAttachment],
"paginatedFileAttachments": AccountFileAttachmentConnectionTypeConnection,
"maximumRefund": MaximumRefundType,
"campaigns": [AccountCampaignType],
"isInHardship": true,
"activeHardshipAgreements": [HardshipAgreementType],
"notes": [AccountNoteType],
"contributionAgreements": [ContributionAgreementType],
"assistanceAgreements": [AssistanceAgreementType],
"debtCollectionProceedings": [DebtCollectionProceedingType],
"createdAt": "2020-01-01T00:00:00.000Z",
"preferredLanguageForComms": "abc123",
"consents": ConsentType,
"reminders": AccountReminderConnectionTypeConnection,
"properties": [PropertyType],
"marketSupplyAgreements": AgreementConnection,
"canModifyPayments": CanModifyPaymentsType,
"projectedBalance": 1,
"shouldReviewPayments": true,
"recommendedBalanceAdjustment": 1,
"electricityAgreements": [ElectricityAgreementType],
"gasAgreements": [GasAgreementType],
"warmHomeDiscount": WarmHomeDiscount,
"eligibilityForWarmHomeDiscount": WarmHomeDiscountEligibility,
"billingPostcode": "abc123",
"canRenewTariff": true,
"trackerTariffDailyPricing": TrackerTariffDailyPricing,
"paymentAdequacy": PaymentAdequacyType,
"smets2Interest": "PRIORITY",
"smets2RefusalReason": "SMETS2_INTEREST_REASON_DO_NOT_OWN_HOME",
"greenAccomplishments": GreenAccomplishmentsType,
"canChangePayments": true,
"cotReadingWindowDays": 1,
"canBeWithdrawn": true,
"currentEstimatedSsd": "2020-01-01",
"earliestPossibleSsd": "2020-01-01",
"latestPossibleSsd": "2020-01-01",
"operationsTeam": OperationsTeamType,
"canInputMeterReadingsViaIvr": true,
"hasActiveDunningProcess": true,
"hasActiveCollectionsProceedings": true,
"isEligibleForElectricityReadingIncentive": true,
"isEligibleForGasReadingIncentive": true,
"isInBlockingMigration": true
}AccountUserCommsPreferences
Information about the preferences set up for a user.
Fields
| Name | Description |
|---|---|
|
What format the user would like to receive their emails in. |
|
This setting allows the user to adjust the default font size of the communications sent to them. |
|
Whether the user has opted in to receive meter reading confirmation emails. |
|
Whether a user has opted in to receive messages from the client or client group. For example, for Octopus Energy this describes whether a user is opted in to offers from Octopus Investments. |
|
Whether a user has opted in to receive messages offering discounts or other services not directly related to the services the client provides. |
|
Whether a user has opted in to receive messages we recommend they read, but are not vital to the utilities the client provides. For example, these could be reminders that the client will take a payment. |
|
Whether the user has opted in to receive SMS messages. |
|
Whether a user has opted in to receive messages from the client's preferred third parties. |
|
Whether a user has opted in to receive messages updating them on client activities. |
|
Whether a user has opted to have inverted colours in their emails. This is currently only relevant to the Octopus Energy brand, whose emails have a dark background by default. |
|
Song which will be used as hold music for the user. |
Example
{
"isOptedInToClientMessages": true,
"isOptedInToOfferMessages": true,
"isOptedInToRecommendedMessages": true,
"isOptedInToUpdateMessages": true,
"isOptedInToThirdPartyMessages": true,
"emailFormat": "TEXT",
"isUsingInvertedEmailColours": true,
"fontSizeMultiplier": 1.0,
"isOptedInMeterReadingConfirmations": true,
"isOptedInToSmsMessages": true,
"preferredHoldMusic": "NO_SONG_PREFERRED"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AccountUserConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AccountUserConnectionTypeEdge
A Relay edge containing a AccountUserConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AccountUserType,
"cursor": "abc123"
}AccountUserConsents
Information about the consents for an account user.
Fields
| Name | Description |
|---|---|
|
Consents linked to this user. |
Example
{
"consents": ConsentType
}Fields
| Name | Description |
|---|---|
|
Whether the value is sensitive and encrypted. |
|
The namespace for the property. |
|
The property value. |
Example
{
"namespace": "abc123",
"value": "abc123",
"isSensitive": true
}AccountUserPermission
Holds information about a specific permission.
Fields
| Name | Description |
|---|---|
|
The short name of the permission |
Example
{
"permission": "abc123"
}AccountUserRoleType
The role a user has in association with one account.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
The account role. |
|
Example
{
"id": "abc123",
"user": AccountUserType,
"account": AccountType,
"role": RoleString
}AccountUserType
User objects are the core of the authentication system. They typically represent a customer who manages a portfolio of one or more accounts.
Fields
| Name | Description |
|---|---|
|
List of roles a user has for each account they're linked to. |
|
List of accounts that the user is linked to either via portfolio role or account role. |
|
List of alternative phone numbers for the account user. |
|
Consents linked to this user. |
|
AccountUser's date of birth. |
|
List of details linked to this user. |
|
We recommend you use fullName instead of this field. Deprecated The 'displayName' field is deprecated. |
|
|
|
|
|
We recommend you use preferredName or fullName instead of this field. Deprecated The 'firstName' field is deprecated. |
|
The user's full name. |
|
|
|
Whether there are family issues. |
|
List of hold music options. |
|
|
|
Designates whether this user is deceased. |
|
True if user is linked to an account with an active hardship agreement. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
|
|
The user's landline phone number. Deprecated The 'landlinePhoneNumber' field is deprecated. |
|
We recommend you use preferredName or fullName instead of this field. Deprecated The 'lastName' field is deprecated. |
|
The user's secret key to access the Developer API. |
|
|
|
A code that uniquely identifies the account user. |
|
List payment instructions linked to this user. |
|
Holds information about the permissions of the current viewer. |
|
We recommend you use portfolioIds instead of this field. Deprecated The 'portfolioId' field is deprecated. |
|
List of portfolio ids that the user is linked to via their portfolio roles. |
|
List of roles a user has for each portfolio they're linked to. |
|
List of portfolios that the user is linked to via their portfolio roles. |
|
|
|
The user's preferred name. |
|
The user's pronouns e.g. 'she/her', 'he/him', 'they/them'. |
|
|
|
Example
{
"id": "abc123",
"number": "abc123",
"accounts": AccountInterface,
"givenName": "abc123",
"familyName": "abc123",
"email": "abc123",
"mobile": "abc123",
"landline": "abc123",
"title": "abc123",
"pronouns": "abc123",
"isDeceased": true,
"liveSecretKey": "abc123",
"portfolios": PortfolioConnectionTypeConnection,
"dateOfBirth": "2020-01-01",
"details": [AccountUserDetailType],
"permissions": [AccountUserPermission],
"displayName": "abc123",
"firstName": "abc123",
"lastName": "abc123",
"fullName": "abc123",
"preferredName": "abc123",
"portfolioId": "abc123",
"portfolioIds": ["abc123"],
"specialCircumstances": SpecialCircumstancesType,
"preferences": AccountUserCommsPreferences,
"landlinePhoneNumber": "abc123",
"alternativePhoneNumbers": ["abc123"],
"hasFamilyIssues": true,
"isInHardship": true,
"accountUserRoles": [AccountUserRoleType],
"portfolioUserRoles": [PortfolioUserRoleType],
"consents": ConsentType,
"paymentMethods": PaymentInstructionConnectionTypeConnection,
"holdMusicChoices": [TrackOptionType],
"isOptedInToWof": true
}AccountWithStatusInfoType
An object holding a subset of account.
Fields
| Name | Description |
|---|---|
|
The active payment method for the account. |
|
The current balance of the account. |
|
Data about whether or not an account can modify their payments. |
|
Retrieve all market supply agreements under this account. Note that when |
|
|
|
Properties linked to the account now and in the future. |
|
The current status of the account. |
Example
{
"number": "abc123",
"status": "PENDING",
"properties": [PropertyType],
"marketSupplyAgreements": AgreementConnection,
"canModifyPayments": CanModifyPaymentsType,
"balance": 1,
"activePaymentMethod": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
The reason the appointment was cancelled (category). |
|
The reason the appointment was cancelled (sub-category). |
|
|
|
|
|
|
|
Is the appointment switching from a traditional (not SMETS1) meter to a smart meter? |
|
|
|
The current status of the Siteworks application. |
|
|
|
|
|
The category of work the appointment has been booked for. |
Example
{
"id": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"appointmentDate": "2020-01-01",
"timeSlotStart": "00:00:00.000Z",
"timeSlotEnd": "00:00:00.000Z",
"createdAt": "2020-01-01T00:00:00.000Z",
"agent": "GENERIC_AGENT",
"workCategory": "EXCHANGE",
"status": "BOOKED",
"date": "2020-01-01",
"isTradToSmartExchange": true,
"requestId": "abc123",
"agentReference": "abc123",
"cancellationCategory": "CANCELLED_BY_CUSTOMER",
"cancellationSubCategory": "abc123"
}Fields
| Name | Description |
|---|---|
|
Address line 1 of the associated property of the COS loss process. |
|
Address line 2 of the associated property of the COS loss process. |
|
Address line 3 of the associated property of the COS loss process. |
|
The fuel type of the meter associated with the COS loss process. |
|
The id of the 'Change Of Supplier Loss' process. |
|
A flag for whether or not the meter point has an open ET associated with it. |
|
Postcode of the associated property of the COS loss process. |
|
The date the supply ends. |
Example
{
"cosLossProcessId": 1,
"cosLossProcessFuelType": "ELECTRICITY",
"addressLine1": "abc123",
"addressLine2": "abc123",
"addressLine3": "abc123",
"postcode": "abc123",
"supplyEndDate": "2020-01-01",
"hasOpenErroneousTransfer": true
}Fields
| Name | Description |
|---|---|
|
The time the data was reported. |
|
The latest reported activity of the heat pump. |
Example
{
"value": "PRE_HEATING",
"timestamp": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Username of the Actor. |
Example
{
"username": "abc123"
}AddBusinessToSegmentMutation
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11107: Unauthorized.
- KT-CT-11111: Segment does not exist.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The business segment period that was created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"businessSegmentPeriod": BusinessSegmentPeriodType
}AddCampaignToAccount
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-7427: No campaign found with given slug.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the campaign was successfully added. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"campaignAdded": true
}AddCreditToSmartMeter
Add credit to a smart prepayment meter.
Fields
| Name | Description |
|---|---|
|
Top-up amount in pence to add to smart meter. |
Example
{
"amount": 1
}AddEvPublicChargingToken
Add an EV Public Charging token.
The possible errors that can be raised are:
- KT-CT-5817: External Account not found.
- KT-CT-5812: Token with this value already exists within this period.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"token": Token
}AddItemsToRiskList
Add new items to risk list.
The possible errors that can be raised are:
- KT-CT-12105: Risk list item addition failed.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
List of successfully added risk identifiers. |
Example
{
"possibleErrors": [PossibleErrorType],
"riskIdentifiers": [RiskListItemType]
}Example
{
"note": InkNote,
"clientMutationId": "abc123"
}AddSignupReferralOnAccount
Create a referral scheme reward for an organization. This allows businesses to issue rewards based on a referral scheme.
The possible errors that can be raised are:
- KT-CT-6723: Unauthorized.
- KT-CT-6729: This scheme cannot be applied to given account.
- KT-CT-6710: Unable to create referral.
- KT-CT-6728: This referral scheme's usage is at capacity.
- KT-CT-6712: Invalid reference.
- KT-CT-6713: Referring and referred account brands do not match.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created account referral instance. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountReferral": ReferralType
}Example
{
"mpan": "abc123",
"profileClass": "abc123"
}AddressConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AddressConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AddressConnectionTypeEdge
A Relay edge containing a AddressConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AddressType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
First address line. |
|
Second address line. |
|
Third address line. |
|
Fourth address line. |
|
Fifth address line. |
|
Postcode. |
|
Unique Property Reference Number. |
Example
{
"uprn": "abc123",
"addressLine1": "abc123",
"addressLine2": "abc123",
"addressLine3": "abc123",
"addressLine4": "abc123",
"addressLine5": "abc123",
"postcode": "abc123"
}Fields
| Name | Description |
|---|---|
|
List of energised electricity meter points associated with the address. |
|
List of gas meter points associated with the address. |
Example
{
"electricityMeterPoints": [ElectricMeterTechnicalDetails],
"gasMeterPoints": [GasMeterTechnicalDetails]
}Fields
| Name | Description |
|---|---|
|
A unique ID per address using part of the address with spaces removed. |
|
The type of address (domestic, business or unknown). |
|
The complete and human-legible address in a single string. |
|
|
|
|
|
The ID of the Grid Supply Point Group that the address belongs to. |
|
|
|
The identifier for a property. The house number consists of the part of line 1 of the address that is not the street name. This includes sub-building names, building names, deliver point aliases and building numbers. For example, the house number for the property 'Flat 12 100 Example St' would be 'Flat 12 100'. |
|
Line 1 of the address. This is generally the house number and street name. |
|
Line 2 of the address. This is generally the area or village. |
|
Line 3 of the address. This is generally the area or village. |
|
Line 4 of the address. This is generally the city. |
|
Line 5 of the address. This is generally the county. |
|
|
|
The street name for a property. The street name consists of the part of line 1 of the address that is not the house number. For example, the house number for the property 'Flat 12 100 Example St' would be 'Example St'. |
Example
{
"addressKey": "abc123",
"addressType": "DOMESTIC",
"display": "abc123",
"gspGroupId": "abc123",
"line1": "abc123",
"line2": "abc123",
"line3": "abc123",
"line4": "abc123",
"line5": "abc123",
"postcode": "abc123",
"houseNumber": "abc123",
"streetName": "abc123",
"hasPrepaidMeters": true,
"gasMeterPoints": [AddressAPIGasMeterPointType],
"electricityMeterPoints": [AddressAPIElectricityMeterPointType]
}AddressUPRNTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AddressUPRNTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AddressUPRNTypeEdge
A Relay edge containing a AddressUPRNType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": UniqueRELAddressType,
"cursor": "abc123"
}AffiliateAudioRecordingPresignedPostType
Metadata returned when generating a pre-signed post URL for an affiliate.
Fields
| Name | Description |
|---|---|
|
The S3 bucket. |
|
The fields to be included in the pre-signed post. |
|
The S3 bucket key. |
|
The pre-signed S3 URL. |
Example
{
"key": "abc123",
"bucket": "abc123",
"fields": {"key": "value"},
"preSignedUrl": "abc123"
}AffiliateLinkType
Affiliate link for the organization.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
Affiliate Organisation. |
|
|
|
Example
{
"id": "abc123",
"organisation": AffiliateOrganisationType,
"subdomain": "abc123",
"trainingStatus": "NOT_APPLICABLE",
"isBusiness": true,
"contactName": "abc123",
"contactEmail": "abc123",
"landingUrl": "abc123"
}Fields
| Name | Description |
|---|---|
|
Is this partner allowed to specify payment methods other than Direct Debit in the import csv or API. |
|
Are meter point registrations limited for profile classes 1 and 2 for registrations from csv or API. |
|
Allow registration requests with customers without an email address. |
|
Allow registration requests with exiting account user emails to add to the portfolio belonging to the account user. |
|
Allow performing tariff renewals via API. |
|
Allow this partner access to the IVR support API (modify their own IVR handling through third party 'IVR Flow Editor'). |
|
The primary contact email for the organisation. |
|
Default Account Type. |
|
|
|
Restrict to field-sales-only products? This is only allowed for the 'field-sales' and 'events' sales channels. |
|
|
|
Sales Channel. Deprecated The 'salesChannel' field is deprecated. |
|
Sales Channel Code. |
|
Allow this partner to skip validation that ensures all meter points belong to the same address. |
Example
{
"id": "abc123",
"name": "abc123",
"contactEmail": "abc123",
"salesChannel": "DIRECT",
"canRenewTariffs": true,
"defaultAccountType": "BUSINESS",
"allowAlternativePaymentMethods": true,
"canRegisterBusinessMeterPoints": true,
"canRegisterPortfolioAccounts": true,
"canRegisterCustomersWithoutEmailAddress": true,
"canUseIvrSupportApi": true,
"skipMeterPointAddressValidation": true,
"salesChannelCode": "abc123",
"isFieldSalesOnlyProduct": true
}AffiliateSessionType
A tracked session for the affiliate link.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Affiliate Link. |
|
|
|
Example
{
"id": "abc123",
"ipAddress": "abc123",
"userAgent": "abc123",
"queryParams": {"key": "value"},
"link": AffiliateLinkType
}Fields
| Name | Description |
|---|---|
|
The price multiplier/coefficient used to calculate the unit rate. |
|
The peak offset for the unit rate. |
|
The maximum value/cap for the unit rate. |
Example
{
"priceCap": 1.0,
"peakOffset": 1.0,
"gspCoefficient": 1.0
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AgreementEdge,
"totalCount": 1,
"edgeCount": 1
}AgreementEdge
A Relay edge containing a Agreement and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": CommonAgreementType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The amount of the transaction that has been allocated to the billing document. A positive amount indicates money received from the customer (payments, credits). A negative amount indicates money paid to the customer (repayments). |
|
Reason for the allocation intention. |
|
The amount of the transaction. A positive amount indicates money received from the customer (payments, credits). A negative amount indicates money paid to the customer (repayments). |
|
ID of the allocated transaction. |
|
The type of the transaction. |
Example
{
"transactionId": 1,
"transactionType": "CREDIT",
"transactionAmount": 1,
"allocationAmount": 1,
"allocationReason": "abc123"
}AllocationType
Represents an allocation of a fulfilment to an obligation.
Fields
| Name | Description |
|---|---|
|
The amount of the allocation (in minor currency units), unsigned. |
|
The fulfilment that is allocated. |
Example
{
"amount": 1,
"fulfilment": FulfilmentType
}AllowRepaymentSubmission
Allow a repayment to be submitted.
The possible errors that can be raised are:
- KT-CT-3944: Account repayment does not exist.
- KT-CT-3945: Unable to allow a repayment to be submitted.
- KT-CT-3950: The provided reason text is too long.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The repayment ID. |
|
Resulting Repayment Intervention details. |
Example
{
"possibleErrors": [PossibleErrorType],
"repaymentId": "abc123",
"repaymentIntervention": RepaymentInterventionType
}AlreadyLinkedError
Returned when an account already has a LINE account linked to it.
Fields
| Name | Description |
|---|---|
|
The type of error that occurred. |
Example
{
"type": "NO_MATCHING_LINE_LINK"
}AmendPayment
The possible errors that can be raised are:
- KT-CT-3924: Unauthorized.
- KT-CT-4123: Unauthorized.
- KT-CT-3970: The account cannot amend payments.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": AccountPaymentType
}AmendUnbilledElectricityReading
Amend unbilled electricity reading.
Fields
| Name | Description |
|---|---|
|
Example
{
"readingAmended": true
}AnimationType
A media element containing an animation, such as a Lottie.
Fields
| Name | Description |
|---|---|
|
Whether the element is hidden from view. |
|
Accessible description of the element. |
|
The horizontal alignment of the media. |
|
Unique identifier of the object. |
|
The resource URL of the media. |
|
The name of the object's type. |
|
The measurement of the element. |
Example
{
"width": ItemSizeType,
"mediaUrl": "abc123",
"horizontalAlignment": "START",
"accessibilityHidden": true,
"accessibilityLabel": "abc123",
"id": "abc123",
"typename": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AnnualStatementConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AnnualStatementConnectionTypeEdge
A Relay edge containing a AnnualStatementConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AnnualStatementType,
"cursor": "abc123"
}AnnualStatementType
Annual statements that are sent to the account. They summarize important information about usage and tariffs.
Example
{
"periodStartsAt": "2020-01-01T00:00:00.000Z",
"periodEndsAt": "2020-01-01T00:00:00.000Z",
"id": "abc123",
"pdfUrl": "abc123"
}AnnulmentBillingDocumentType
An annulment is a billing document that annuls another billing document.
Fields
| Name | Description |
|---|---|
|
ID of the billing document annulled by this annulment. |
|
First time the annulment was issued. |
|
|
|
URL to the PDF of the annulment. |
Example
{
"id": 1,
"annulledBillingDocumentId": 1,
"firstIssued": "2020-01-01T00:00:00.000Z",
"pdfUrl": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": AppSessionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}AppSessionConnectionTypeEdge
A Relay edge containing a AppSessionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AppSessionType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Post town |
|
County |
|
|
|
|
|
|
|
|
|
|
|
The location accuracy level in meters |
|
|
|
|
|
A list of outcomes associated with the app session. |
|
|
|
|
|
|
|
|
|
|
|
Example
{
"startedAt": "2020-01-01T00:00:00.000Z",
"stoppedAt": "2020-01-01T00:00:00.000Z",
"addressLine1": "abc123",
"addressLine2": "abc123",
"addressLine3": "abc123",
"addressLine4": "abc123",
"addressLine5": "abc123",
"id": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"link": AffiliateLinkType,
"isArchived": true,
"postcode": "abc123",
"account": AccountType,
"locationAt": "2020-01-01T00:00:00.000Z",
"locationHorizontalAccuracy": 1,
"locationLatitude": "1.0",
"locationLongitude": "1.0",
"salesMode": "DOOR",
"type": AppSessionType,
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z",
"outcomes": [OutcomeType]
}Example
{
"value": "1.0",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z"
}ApplicableRateConnectionTypeConnection
Dovetailing rates applicable for an account / meter point combination over a given time period.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ApplicableRateConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ApplicableRateConnectionTypeEdge
A Relay edge containing a ApplicableRateConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ApplicableRate,
"cursor": "abc123"
}ApproveRepayment
The possible errors that can be raised are:
- KT-CT-3934: Repayment request already approved.
- KT-CT-3935: Repayment request cannot be paid.
- KT-CT-3959: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The approved repayment. |
Example
{
"possibleErrors": [PossibleErrorType],
"repayment": AccountRepaymentType
}AssessCollectionProcessRecordForPause
Assess the Collection Process for pause and pause or unpause it based on the assessment.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Details of collection process after running the pause assessment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessProcessed": AssessCollectionProcessRecordForPauseOutputType
}AssessCollectionProcessRecordForPauseOutputType
Output for assessing a Collection process for pause.
Fields
| Name | Description |
|---|---|
|
The pause status of the collection process. |
|
The number of the collection process record. |
Example
{
"number": "abc123",
"isPaused": true
}AssignDiscountCode
The possible errors that can be raised are:
- KT-GB-5911: We have assigned all electric blanket discount codes.
- KT-GB-5912: Account already has a discount code assigned.
- KT-GB-5913: An error occurred assigning a discount code.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The assigned discount code. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"discountCode": "abc123"
}Fields
| Name | Description |
|---|---|
|
The bucket that the conversation will be assigned to. |
|
|
|
The conversation that will be assigned to the bucket. |
Example
{
"conversation": InkConversation,
"bucket": InkBucket,
"clientMutationId": "abc123"
}Fields
| Name | Description |
|---|---|
|
The ID of the assigned user. |
|
The username of the assigned user. |
Example
{
"id": "abc123",
"username": "abc123"
}AssistanceAgreementType
A single Assistance Agreement.
Fields
| Name | Description |
|---|---|
|
The start datetime of the agreement. |
|
The end datetime of the agreement, if any. |
|
The type of assistance provided by the agreement. |
Example
{
"assistanceType": "abc123",
"activeFrom": "2020-01-01",
"activeTo": "2020-01-01"
}AssociateCallWithAccount
The possible errors that can be raised are:
- KT-CT-11802: Call not found.
- KT-CT-4178: No account found with given account number.
- KT-CT-11808: Unable to associate account to call.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The call. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"call": InboundCallType
}AssociateItemToCollectionProcess
Associate an item to collection process record
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-11205: Item already associated to collection process.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Item associated to the collection process. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessAssociatedItem": AssociateItemToCollectionProcessOutputType
}Fields
| Name | Description |
|---|---|
|
Associated item identifier. |
|
The number of the collection process record. |
Example
{
"number": "abc123",
"itemId": "abc123"
}AttachmentType
Represents a file to attach to a communication
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Temporary URL at which the attachment is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). |
Example
{
"id": "abc123",
"filename": "abc123",
"temporaryUrl": "abc123"
}Fields
| Name | Description |
|---|---|
|
The app session associated with this audio recording. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"appSession": AppSessionType,
"contentType": "abc123",
"duration": 1.0,
"fileSize": 1,
"startedAt": "2020-01-01T00:00:00.000Z",
"stoppedAt": "2020-01-01T00:00:00.000Z",
"s3Bucket": "abc123",
"s3Key": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z"
}AuthFlow
A step where the user must complete an auth flow.
Fields
| Name | Description |
|---|---|
|
The URL to redirect the user to for authorization. |
|
A unique identifier for this onboarding step. |
|
The URI where the auth flow is going to redirect back to at the end. |
Example
{
"id": "abc123",
"redirectUri": "abc123",
"authorizationUri": "abc123"
}AutoTopupConfigConnectionTypeConnection
GraphQL output type for querying nodes of auto top-up configs.
Using this class instead of AutoTopupConfigType directly allows for pagination.
Fields
| Name | Description |
|---|---|
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
Example
{
"pageInfo": PageInfo,
"edges": AutoTopupConfigConnectionTypeEdge
}AutoTopupConfigConnectionTypeEdge
A Relay edge containing a AutoTopupConfigConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AutoTopupConfigType,
"cursor": "abc123"
}AutoTopupConfigType
GraphQL output type for querying auto top-up configs.
Fields
| Name | Description |
|---|---|
|
The account number, e.g.: 'A-A1B2C3D4'. |
|
Alphanumber code identifying the device, e.g.: 'A1-BC-D2-00-01-23-EF-4G'. |
|
The date and time when the config became effective. |
|
The date and time when the config stopped being effective. |
|
|
|
Auto top-up amount in the lowest currency unit. i.e. USA cents / GBP pence / etc. |
Example
{
"id": "abc123",
"accountNumber": "abc123",
"deviceId": "abc123",
"topupAmount": 1,
"effectiveFrom": "2020-01-01T00:00:00.000Z",
"effectiveTo": "2020-01-01T00:00:00.000Z"
}AutoTopupTriggerConnectionTypeConnection
GraphQL output type for querying nodes of auto top-up trigger events.
Using this class instead of AutoTopupTriggerType directly allows for pagination.
Fields
| Name | Description |
|---|---|
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
Example
{
"pageInfo": PageInfo,
"edges": AutoTopupTriggerConnectionTypeEdge
}AutoTopupTriggerConnectionTypeEdge
A Relay edge containing a AutoTopupTriggerConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": AutoTopupTriggerType,
"cursor": "abc123"
}AutoTopupTriggerType
GraphQL output type for querying auto top-up trigger events.
Fields
| Name | Description |
|---|---|
|
Integer ID of the related AutoTopupConfig, e.g. '123'. |
|
DateTime when the trigger event was created, e.g. '2024-01-01T00:00:00+00:00'. |
|
Reason auto top-up trigger event failed, if any. |
|
|
|
Source of the auto top-up trigger event. |
|
Status of the auto top-up trigger event. |
|
DateTime when auto topup was triggered, e.g. '2024-01-01T00:00:00+00:00'. |
|
DateTime when the trigger event was last updated, e.g. '2024-01-01T00:00:00+00:00'. |
Example
{
"id": "abc123",
"autoTopupConfigId": "abc123",
"triggeredAt": "2020-01-01T00:00:00.000Z",
"status": "INITIATED",
"source": "LOW_CREDIT_BALANCE",
"failureReason": "NO_IMPORT_METER",
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Spin information for an electricity agreement. |
|
Spin information for a gas agreement. |
Example
{
"electricity": SupplyTypeSpecificSpinsType,
"gas": SupplyTypeSpecificSpinsType
}AwardLoyaltyPoints
Award Loyalty Points.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-9202: Loyalty Points adapter not configured.
- KT-CT-9204: Negative or zero points set.
- KT-CT-9208: Invalid posted at datetime.
- KT-CT-9210: Unhandled Loyalty Points exception.
- KT-CT-9212: Points exceed maximum limit.
- KT-CT-9221: Idempotency key already used on ledger entry.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The ledger entry for the awarded loyalty points |
|
The number of loyalty points that were awarded. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"pointsAwarded": 1,
"ledgerEntry": LoyaltyPointLedgerEntryType
}BackendScreenEvent
Returns an Action to perform, e.g. a screen to load.
BackendScreenEvents are specific types of Action which trigger a mutation in the Kraken backend. They return an action (any type), such as a ScreenActionType (which is then used to load the next screen). Any action registered in the registry should really be an "event" with some side-effect in the backend.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-8002: No event found.
- KT-CT-8003: Event has no execute function.
- KT-CT-8004: Error executing event in the backend.
- KT-CT-8007: Incorrect or missing parameters for backend screen event.
- KT-GB-9310: Account ineligible for joining Octoplus.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
An action to perform. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"action": ActionType
}BackendScreenEventActionType
An action which triggers some event in the Kraken backend.
Fields
| Name | Description |
|---|---|
|
The ID of the event to trigger. |
|
Unique identifier of the object. |
|
List of key-value pairs to pass as parameters to the event. |
|
The name of the action object's type. |
|
The name of the object's type. |
Example
{
"typeName": "abc123",
"id": "abc123",
"typename": "abc123",
"eventId": "abc123",
"params": BackendScreenParam
}BackendScreenParam
A key-value pair (both Strings) which is passed as a parameter to a screen.
Example
{
"key": "abc123",
"value": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the balance forecast is available for the given account. |
|
The reason why the balance forecast is unavailable for the given account. |
Example
{
"isAvailable": true,
"unavailabilityReason": "NO_BILL_ISSUED_IN_LAST_60_DAYS"
}Fields
| Name | Description |
|---|---|
|
The reason why the balance forecast is unavailable for the given account. |
|
Whether the balance forecast is available for the given account. Deprecated The 'isAvailable' field is deprecated. |
Example
{
"isAvailable": true,
"availability": BalanceForecastAvailabilityType
}Fields
| Name | Description |
|---|---|
|
The maximum state of charge (soc) %. |
|
The minimum state of charge (soc) %. |
Example
{
"minimumSocPercentage": 1,
"maximumSocPercentage": 1
}Fields
| Name | Description |
|---|---|
|
The charging preferences of the battery (e.g. min / max state of charge %). |
|
The current status of the battery (e.g. connected, state of charge, power). |
|
Batteries. |
|
ID of the device in KrakenFlex. |
|
Device specific parameters. |
|
Battery integration provider (make). |
Example
{
"krakenflexDeviceId": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"params": BatteryParamsType,
"deviceStatus": DeviceStatusType,
"chargingPreferences": BatteryChargingPreferencesType
}Fields
| Name | Description |
|---|---|
|
ID of the battery variant. |
Example
{
"variantId": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the battery is currently connected (online/offline). |
|
The current power being used to charge the battery, or discharging from the battery, in kW. A negative value indicates this power is being used to charge the battery; a positive value indicates power is being discharged from the battery. |
|
The current state of charge (SoC) of the battery (0-100). |
Example
{
"connectionStatus": "ONLINE",
"powerInKw": "1.0",
"stateOfCharge": "1.0"
}Fields
| Name | Description |
|---|---|
|
Usable capacity in kWh. |
|
Coupling type (AC/DC). |
|
Whether a variant is deprecated. |
|
Whether an integration/make is live, i.e. available. |
|
Max import/export power in kW. |
|
Model name of the battery. |
|
ID of the battery variant. |
Example
{
"variantId": "abc123",
"model": "abc123",
"couplingType": "AC",
"batteryCapacityInKwh": "1.0",
"maxPowerInKw": "1.0",
"isIntegrationLive": true,
"isDeprecated": true
}Fields
| Name | Description |
|---|---|
|
Make of the home battery. |
|
List of home battery models per make. |
Example
{
"make": "abc123",
"models": [BatteryVariantModelsType]
}BillCharge
A charge to the customer from the energy retailer.
Fields
| Name | Description |
|---|---|
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The date time when the transaction is created. |
|
The unique identifier for the transaction. |
|
Returns the note field value for the transaction, which contains additional info. |
|
The date the transaction was posted. |
|
Returns the reason. |
|
A user readable string that indicates what this transaction relates to. |
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"amounts": TransactionAmountType,
"title": "abc123",
"note": "abc123",
"reasonCode": "abc123"
}BillConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": BillConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}BillConnectionTypeEdge
A Relay edge containing a BillConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": BillInterface,
"cursor": "abc123"
}BillCredit
A credit to the customer from the energy retailer.
Fields
| Name | Description |
|---|---|
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The date time when the transaction is created. |
|
The unique identifier for the transaction. |
|
Returns the note field value for the transaction, which contains additional info. |
|
The date the transaction was posted. |
|
Returns the reason. |
|
A user readable string that indicates what this transaction relates to. |
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"amounts": TransactionAmountType,
"title": "abc123",
"note": "abc123",
"reasonCode": "abc123"
}BillPayment
A payment from the customer to the energy supplier.
Fields
| Name | Description |
|---|---|
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The date time when the transaction is created. |
|
The unique identifier for the transaction. |
|
Returns the note field value for the transaction, which contains additional info. |
|
The date the transaction was posted. |
|
Returns the reason. |
|
A user readable string that indicates what this transaction relates to. |
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"amounts": TransactionAmountType,
"title": "abc123",
"note": "abc123",
"reasonCode": "abc123"
}BillRefund
A refund to the customer from the energy supplier.
Fields
| Name | Description |
|---|---|
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The date time when the transaction is created. |
|
The unique identifier for the transaction. |
|
Returns the note field value for the transaction, which contains additional info. |
|
The date the transaction was posted. |
|
Returns the reason. |
|
A user readable string that indicates what this transaction relates to. |
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"amounts": TransactionAmountType,
"title": "abc123",
"note": "abc123",
"reasonCode": "abc123"
}BillToLatestSmartMeterSnapshot
Bill an account with a smart meter to the most recent midnight snapshot reading.
Fields
| Name | Description |
|---|---|
|
The date that has been billed up to. |
|
The balance after attempting to bill. |
Example
{
"billedToDate": "2020-01-01",
"currentBalance": "1.0"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": BillTransactionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}BillTransactionConnectionTypeEdge
A Relay edge containing a BillTransactionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": BillTransactionType,
"cursor": "abc123"
}BillingAttachmentConnectionTypeConnection
A connection that can provide links to the attachments of the bill.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": BillingAttachmentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}BillingAttachmentConnectionTypeEdge
A Relay edge containing a BillingAttachmentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": BillingAttachmentType,
"cursor": "abc123"
}BillingAttachmentType
Attachments are associated with a bill files and can be used to provide additional information to the customer.
Fields
| Name | Description |
|---|---|
|
The name of the file. |
|
The |
|
The expiry datetime field of the temporary URL. |
Example
{
"temporaryUrl": "abc123",
"temporaryUrlExpiresAt": "2020-01-01T00:00:00.000Z",
"filename": "abc123"
}BillingDocumentIssuanceFrequencyType
Represents billing document issuance frequency to be applied during a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true
}Fields
| Name | Description |
|---|---|
|
Allocation intentions for the billing document. |
|
Allocations for the billing document. |
|
The date when the payment is due for the billing document. |
|
The expected amount for the billing document (in minor currency units). |
|
The amount that remains to be paid for the billing document (in minor currency units). |
Example
{
"dueDate": "2020-01-01",
"expectedAmount": 1,
"remainingAmount": 1,
"allocationIntentions": AllocationIntentionType,
"allocations": AllocationType
}BillingOptionsType
Information about an account's billing schedule.
Fields
| Name | Description |
|---|---|
|
The date on which the current billing cycle will end. Null if the account is on flexible billing. |
|
The date on which the current billing cycle started. |
|
If true, this account is billed on specific day of a regular cycle. If false, the billing schedule is flexible, depending on when meter readings are submitted. |
|
The next date on which this account will next be billed. This is the same as the start date for their next bill cycle. Null if the account is on flexible billing. |
|
|
|
|
|
The day of the month on which the account's billing period should start. |
Example
{
"periodStartDay": 1,
"periodLength": "MONTHLY",
"periodLengthMultiplier": 1,
"isFixed": true,
"currentBillingPeriodStartDate": "2020-01-01",
"currentBillingPeriodEndDate": "2020-01-01",
"nextBillingDate": "2020-01-01"
}BlockRepaymentSubmission
Block a repayment from being submitted.
The possible errors that can be raised are:
- KT-CT-3944: Account repayment does not exist.
- KT-CT-3946: Unable to block a repayment from being submitted.
- KT-CT-3950: The provided reason text is too long.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The repayment ID. |
|
Resulting Repayment Intervention details. |
Example
{
"possibleErrors": [PossibleErrorType],
"repaymentId": "abc123",
"repaymentIntervention": RepaymentInterventionType
}BulkUpdateSensorDisplayName
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
A mapping of transaction ids for each sensor. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionIds": [SensorUpdateTransactionId]
}BulkUpdateZoneDisplayNames
The possible errors that can be raised are:
- KT-CT-4384: Error trying to update heat pump zone names.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The transaction ID for each zone based on the zone code. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionIds": ZoneDisplayNameUpdates
}Fields
| Name | Description |
|---|---|
|
The key of the business detail. |
|
The value of the business detail. |
Example
{
"key": "abc123",
"value": "abc123"
}Fields
| Name | Description |
|---|---|
|
The end date and time of the segment period |
|
The ID of the business segment period |
|
The segment associated with this period |
|
The start date and time of the segment period |
Example
{
"id": "abc123",
"segment": SegmentType,
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The billing address of the business. |
|
The company type of a business account. |
|
The details of the business. |
|
The business ID. |
|
The legal address of the business. |
|
Account number linked to this business. The possible errors that can be raised are:
Deprecated The 'linkedAccountNumber' field is deprecated. |
|
Account numbers linked to this business. |
|
The business' name |
|
The business' number |
|
List payment instructions owned by this business. |
|
The segment this business is assigned to |
Example
{
"id": "abc123",
"name": "abc123",
"number": "abc123",
"businessType": "SOLE_TRADER",
"details": [BusinessDetailType],
"billingAddress": RichAddressType,
"legalAddress": RichAddressType,
"linkedAccountNumber": "abc123",
"linkedAccountNumbers": "abc123",
"segmentName": "abc123",
"paymentMethods": PaymentInstructionConnectionTypeConnection
}CFCampaignEventConnectionTypeConnection
Paginator of Customer Flexibility Campaign Events
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": CFCampaignEventConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}CFCampaignEventConnectionTypeEdge
A Relay edge containing a CFCampaignEventConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": CFCampaignEventType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The unique code for the event. |
|
The end time of the campaign event. |
|
Indicates if the customer is participating in this specific event. |
|
The name of the event. |
|
The start time of the campaign event. |
Example
{
"name": "abc123",
"code": "abc123",
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"isEventParticipant": true
}CalculateDepositAmount
Calculates and records the security deposit amount. Returns the deposit amount and key.
The possible errors that can be raised are:
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Security deposit amount in pence. |
|
unique key of the record inserted in DepositAmount model. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"depositAmount": 1,
"key": "abc123"
}Fields
| Name | Description |
|---|---|
|
The key of the call metadata item. |
|
The value of the call metadata item. |
Example
{
"key": "abc123",
"value": "abc123"
}CallTagConnectionTypeConnection
Paginator of Call Tags
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": CallTagConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}CallTagConnectionTypeEdge
A Relay edge containing a CallTagConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": CallTagType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
ID of the call tag. |
|
Whether the tag can currently be used to tag calls. |
|
Name of the tag that will be used to identify it. |
Example
{
"id": "abc123",
"name": "abc123",
"isActive": true
}Example
{
"name": "abc123",
"slug": "abc123",
"expiryDate": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
Whether or not the account can amend payments. |
|
Whether or not the account can cancel payments. |
Example
{
"canAmendPayments": true,
"canCancelPayments": true
}CancelEnrolment
Mutation for an account to cancel enrolment to a supplier.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-GB-4136: Account cannot be withdrawn.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The number of the account whose enrolment was cancelled. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountNumber": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether or not the account's enrollment can be delayed. |
|
Whether or not the account's enrollment can be cancelled. |
|
Whether or not the account can skip the SSD payment. |
|
A best estimate of when the account should come on supply. |
|
The earliest possible Supply Start Date (SSD) for the account. |
|
The latest possible Supply Start Date (SSD) for the account. |
Example
{
"canBeDelayed": true,
"canBeWithdrawn": true,
"currentEstimatedSsd": "2020-01-01",
"earliestPossibleSsd": "2020-01-01",
"latestPossibleSsd": "2020-01-01",
"canSkipSsdPayment": true
}CancelPayment
The possible errors that can be raised are:
- KT-CT-3924: Unauthorized.
- KT-CT-3954: Payment cancellation failed.
- KT-CT-3955: Payment cannot be cancelled.
- KT-CT-3956: Temporary error occurred.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The cancelled payment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": AccountPaymentType
}CancelRepaymentRequest
Cancel a repayment or refund request.
The possible errors that can be raised are:
- KT-CT-4231: Unauthorized.
- KT-CT-3930: The repayment or refund request does not exist.
- KT-CT-3931: This repayment or refund request cannot be cancelled.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The cancelled repayment/refund request. |
Example
{
"possibleErrors": [PossibleErrorType],
"repaymentRequest": CancelRepaymentRequestOutputType
}CancelRepaymentRequestOutputType
Output from cancelling a repayment or refund request.
Fields
| Name | Description |
|---|---|
|
The ID of the cancelled request. |
|
The current status of the cancelled request. |
Example
{
"requestId": "abc123",
"status": "REQUESTED"
}CancelSiteworksAppointment
Allows account users and organisations to cancel siteworks appointment.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"siteworksAppointment": ActiveAppointmentType
}CancelSmartFlexOnboarding
Cancel onboarding of a device with SmartFlex.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}CardComponentType
A card containing a list of items
Fields
| Name | Description |
|---|---|
|
Whether the element is hidden from view. |
|
Accessible description of the element. |
|
Unique identifier of the object. |
|
The list of components. |
|
The name of the object's type. |
Example
{
"accessibilityHidden": true,
"accessibilityLabel": "abc123",
"id": "abc123",
"typename": "abc123",
"items": CardItemType
}Fields
| Name | Description |
|---|---|
|
The list of cards. |
|
Unique identifier of the object. |
|
The name of the object's type. |
Example
{
"id": "abc123",
"typename": "abc123",
"cards": CardComponentType
}Fields
| Name | Description |
|---|---|
|
The description for each kind of Constantine. |
|
The name describing which kind of Constantine this Constantine is. |
|
The first time this Constantine was caught. |
|
How many prize entries catching this Constantine is worth. |
|
How rare this kind of Constantine is expressed as en enum associated to a percentage value. |
|
The slug for this kind of Constantine. |
|
The amount of times this Constantine has been caught. |
Example
{
"displayName": "abc123",
"slug": "abc123",
"rarity": "Popular",
"description": "abc123",
"prizeEntries": 1,
"totalCaught": 1,
"firstCaught": "2020-01-01T00:00:00.000Z"
}CharacteristicOverrideConfigurationType
Represents a characteristic override configuration term in a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true
}Charge
A charge to the customer.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the account the transaction belongs to. |
|
Gross amount including tax (when payable). Refer to the Deprecated The 'amount' field is deprecated. |
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The customer's resulting balance after this transaction has been applied, in the smallest unit of currency. |
|
The unique identifier for the most recent billing document linked with the transaction.Note: a transaction may be linked with multiple documents, but this field will only return the identifier for the most recent billing document. |
|
If this charge is for consumption of a good or service, this field will contain details of how much was consumed. Omitted in cases where the charge is not for consumption, or where consumption information is not available (e.g. for some older records). |
|
The date time when the transaction is created. |
|
Returns True if the transaction is linked with a statement. |
|
|
|
Deprecated. Deprecated The 'isAccountCharge' field is deprecated. |
|
Deprecated. Deprecated The 'isAccountPayment' field is deprecated. |
|
Deprecated. Deprecated The 'isCredit' field is deprecated. |
|
Whether the charge is for export electricity. |
|
Whether the statement this transaction is on has been held. A held statement is not sent to a customer automatically, but is instead marked for manual attention by operations staff. Returns False if a statement is not linked with the transaction. |
|
Whether this transaction has been issued on any billing document.Note: Look for the most recently issued transaction instead of looking through all transactions as some accounts may have initial transactions that were not issued.This will return False if the transaction is not associated with any billing documents. |
|
|
|
Returns the note field value for the transaction, which contains additional info. |
|
|
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123",
"amount": 1,
"amounts": TransactionAmountType,
"balanceCarriedForward": 1,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "abc123",
"billingDocumentIdentifier": "abc123",
"statementId": "abc123",
"isReversed": true,
"hasStatement": true,
"note": "abc123",
"reasonCode": "abc123",
"consumption": Consumption,
"isExport": true
}Example
{
"id": "abc123",
"uid": "abc123",
"nameOnCard": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "abc123",
"models": [ChargePointModelsType]
}Example
{
"model": "abc123",
"powerInKw": ["abc123"]
}Fields
| Name | Description |
|---|---|
|
Supply amperage. Used in markets where customers are more familiar with amps than power output. |
|
Shows the availability status of an integration. |
|
|
|
|
|
|
|
Example
{
"variantId": 1,
"model": "abc123",
"powerInKw": "1.0",
"amperage": 1,
"isIntegrationLive": true,
"integrationStatus": "INTERNAL_TESTING"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "abc123",
"models": [ChargePointVariantModelType]
}Fields
| Name | Description |
|---|---|
|
The charge reason code. |
|
The charge reason display text. |
|
The group the charge reason belongs to (if applicable). |
|
Whether the charge reason is deprecated. |
|
Whether the charge reason is hidden. |
|
Whether the charge reason is sales tax exempt. |
Example
{
"code": "abc123",
"display": "abc123",
"isDeprecated": true,
"isTaxExempt": true,
"isHidden": true,
"group": "abc123"
}ChargesBreakdownConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ChargesBreakdownConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ChargesBreakdownConnectionTypeEdge
A Relay edge containing a ChargesBreakdownConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ChargesBreakdownType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Charge in minor currency. |
|
The end date of the period the charge is for (exclusive). |
|
The start date of the period the charge is for (inclusive). |
Example
{
"periodStart": "2020-01-01",
"periodEnd": "2020-01-01",
"charge": 1
}Fields
| Name | Description |
|---|---|
|
Example
{
"totalDonatedAmount": 1
}Fields
| Name | Description |
|---|---|
|
Is opted in to donate to charity. |
|
Amount to donate each month. |
Example
{
"monthlyAmount": "ONE",
"isOptedIn": true
}CheckBusinessCreditRisk
Returns a payment multiplier as a measure of risk. The payment multiplier is the number of advance payments we require from a business as security deposit. It is hardcoded except for Limited companies (=LTDs). For LTDs the payment multiplier depends on the credit score.
Fields
| Name | Description |
|---|---|
|
PaymentMultiplier to determine deposit amount. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentMultiplier": 1
}CheckDeviceConnection
Triggers an asynchronous request to check the connection of a device.
As this is an asynchronous operation, the mutation does not return the result of the request. Instead, the request reference is returned, which can be used to track the status of the request. If it's an organisation, the organisation will receive an update on the request via the agent services.
Fields
| Name | Description |
|---|---|
|
The reference of the request in Kraken. |
Example
{
"requestReference": "abc123"
}ClaimOctoplusReward
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
- KT-GB-9313: Not enough Octopoints.
- KT-GB-9314: Reward could not be processed.
- KT-GB-9315: Reward of this type unavailable.
- KT-GB-9316: Account is not Octoplus-enrolled.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The ID of the claimed reward. |
Example
{
"possibleErrors": [PossibleErrorType],
"rewardId": "abc123"
}ClaimShoptopusVoucher
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
- KT-GB-9313: Not enough Octopoints.
- KT-GB-9314: Reward could not be processed.
- KT-GB-9315: Reward of this type unavailable.
- KT-GB-9316: Account is not Octoplus-enrolled.
- KT-GB-9319: This feature is not currently available.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The Reward Voucher code. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"code": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The current temperature of the room in Celsius. |
|
The target temperature of the room in Celsius. |
Example
{
"climateControlEnabled": true,
"targetClimateControlTemperature": "1.0",
"currentClimateControlTemperature": "1.0"
}CloseActionType
Closes the screen.
Fields
| Name | Description |
|---|---|
|
Whether the element is hidden from view. |
|
Accessible description of the element. |
|
Unique identifier of the object. |
|
The name of the action object's type. |
|
The name of the object's type. |
Example
{
"typeName": "abc123",
"id": "abc123",
"typename": "abc123",
"accessibilityHidden": true,
"accessibilityLabel": "abc123"
}CloseDCAProceeding
The possible errors that can be raised are:
- KT-CT-4178: No account found with given account number.
- KT-CT-11602: Could not find DCA with that name.
- KT-CT-11603: Could not stop debt collection proceeding.
- KT-CT-11604: Active debt collection proceeding does not exist for account.
- KT-CT-11605: Multiple active Proceeding's found for same agency and campaign on account.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the closure could be applied. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"dcaProceedingClosureStatus": DCAProceedingClosureStatus
}Fields
| Name | Description |
|---|---|
|
|
|
The live chat. |
Example
{
"liveChat": InkLiveChat,
"clientMutationId": "abc123"
}CloseOpenPrintBatch
Close the Open Print Batch if any.
The possible errors that can be raised are:
- KT-CT-9010: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"printBatch": PrintBatchType
}CollectDeposit
Collect deposit for the given account.
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-CT-5711: No collection is required.
- KT-CT-5712: Deposit agreement does not exist or has not been accepted.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": CollectDepositOutput
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"status": "APPROVED",
"paymentDate": "2020-01-01"
}CollectPayment
The possible errors that can be raised are:
- KT-CT-3932: Invalid data.
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Details about the collected payment. Note that we might not be able to collect the payment (e.g. if there is no usable payment instruction), in which case the status of the returned payment might be failed or cancelled. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": AccountPaymentType
}CollectionProcessDetailsType
Collection process details type
Fields
| Name | Description |
|---|---|
|
Items associated to the collection process. |
|
The collection process record number. |
|
What kind of completion happened. |
|
The completion status of the collection process. |
|
The pause status of the collection process. |
|
Total number of days collection process were on pause. |
Example
{
"collectionProcessRecordNumber": "abc123",
"isPaused": true,
"isComplete": true,
"completionType": "abc123",
"associatedItems": [CollectionProcessRecordAssociatedItemType],
"pausedDays": 1
}CollectionProcessRecordAssociatedItemType
Item associated to collection process
Fields
| Name | Description |
|---|---|
|
Additional details of the item. |
|
Unique reference of item. |
|
Type of item. |
|
Datetime of when action that resulted in item happened. |
Example
{
"itemType": "abc123",
"itemReference": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z",
"extraDetails": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
|
|
The type of the bill. |
|
Constituents of the bill. |
|
The date of the bill is covered from. |
|
The ID of the bill. |
|
The date the bill was sent to the customer. |
|
Requesting this field generates a temporary URL at which bill is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). This field can raise an error with errorClass NOT_FOUND if the bill document has not been created/issued yet. This field is deprecated use 'attachments' field instead. Deprecated The 'temporaryUrl' field is deprecated. |
|
The date of the bill is covered to. |
Example
{
"id": "abc123",
"billType": "STATEMENT",
"fromDate": "2020-01-01",
"toDate": "2020-01-01",
"temporaryUrl": "abc123",
"issuedDate": "2020-01-01",
"attachments": BillingAttachmentConnectionTypeConnection,
"constituents": ConstituentConnection
}Fields
| Name | Description |
|---|---|
|
Information about the current state of the rate limiting for rate limited fields at the time of the request. |
|
Information about points-allowance rate limit for viewer. |
Example
{
"pointsAllowanceRateLimit": PointsAllowanceRateLimitInformation,
"fieldSpecificRateLimits": FieldSpecificRateLimitInformationConnectionTypeConnection
}CommenceDCAProceeding
The possible errors that can be raised are:
- KT-CT-11606: Debt Collection Agency cannot use campaign.
- KT-CT-11601: Cannot start collection proceeding, proceeding for this account already exists.
- KT-CT-11602: Could not find DCA with that name.
- KT-CT-11607: Invalid ledger number for debt collection proceeding.
- KT-CT-11608: Ledger does not belong to account.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the commencement could be applied. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"dcaProceedingCommencementStatus": DCAProceedingCommencementStatus
}CommissionMeter
The possible errors that can be raised are:
- KT-GB-4021: Invalid MPxN.
- KT-GB-4022: MPxN not recognised.
- KT-GB-4023: Error sending the request to commission the device.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The id of the SMETS Commission Request in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The datetime the agreement was entered. |
|
The datetime the agreement was terminated. |
|
|
|
Whether the agreement is currently active. |
|
Whether the agreement is revoked. |
|
The product associated with the agreement. |
|
The agreement's supply point |
|
|
|
|
|
Example
{
"id": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"agreedAt": "2020-01-01T00:00:00.000Z",
"terminatedAt": "2020-01-01T00:00:00.000Z",
"supplyPoint": SupplyPointType,
"product": SupplyProductType,
"isActive": true,
"agreedFrom": "2020-01-01T00:00:00.000Z",
"agreedTo": "2020-01-01T00:00:00.000Z",
"isRevoked": true
}ComplaintConnectionTypeConnection
Paginator of Complaint type.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ComplaintConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ComplaintConnectionTypeEdge
A Relay edge containing a ComplaintConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ComplaintType,
"cursor": "abc123"
}ComplaintContactConnectionTypeConnection
Paginator of Complaint contact type.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ComplaintContactConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ComplaintContactConnectionTypeEdge
A Relay edge containing a ComplaintContactConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ComplaintContactType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Description of action taken. |
|
Created at for contact. |
|
Complaint email. |
|
Complaint landline. |
|
Complaint phone. |
|
Complainant name. |
|
Complaint preferred method. |
|
Status of complaint. |
|
Complaint summary. |
Example
{
"name": "abc123",
"actionTaken": "abc123",
"status": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"mobile": "abc123",
"email": "abc123",
"landline": "abc123",
"preferredCommunicationMethod": "abc123",
"summary": "abc123"
}Fields
| Name | Description |
|---|---|
|
Complaint Assignee. |
|
Complaint contacts. |
|
Complaint creation date. |
|
|
|
Complaint resolution date. |
|
Complaint subtype. |
|
Complaint type. |
Example
{
"id": "abc123",
"contacts": ComplaintContactConnectionTypeConnection,
"type": "abc123",
"subtype": "abc123",
"creationDate": "2020-01-01",
"resolutionDate": "2020-01-01",
"assigneeId": "abc123"
}CompleteAuthFlowForSmartFlexOnboarding
Complete the auth flow step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}CompleteTeslaSetupVirtualKeyForSmartFlexOnboarding
Complete the Tesla setup virtual key onboarding step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}CompleteUserActionRequiredForSmartFlexOnboarding
Complete the UserActionRequired step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}ComponentListType
A list of components which comprise a screen.
This is a legacy type; GenericBackendScreen should be preferred. This is because API clients
should not need to explicitly query for screen attributes like items - these fields are
embedded in the screenData field.
Fields
| Name | Description |
|---|---|
|
Whether the element is hidden from view. |
|
Accessible description of the element. |
|
Unique identifier of the object. |
|
The list of components. Deprecated The 'items' field is deprecated. |
|
The name of the screen. |
|
The refresh / polling frequency in milliseconds. |
|
Serialized JSON representation of the screen. |
|
The name of the object's type. |
Example
{
"accessibilityHidden": true,
"accessibilityLabel": "abc123",
"id": "abc123",
"typename": "abc123",
"name": "abc123",
"refreshFrequency": 1,
"screenData": "abc123",
"items": ItemType
}ConfirmDoubleOptIn
Confirm a requested consent.
This mutation will update the value of the consent associated with the provided token to ACCEPTED.
The possible errors that can be raised are:
- KT-CT-9016: Consent management not enabled.
- KT-CT-9020: Invalid consent expiring token.
- KT-CT-9021: Consent expiring token not found.
- KT-CT-9022: Consent for given token already accepted.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The consent that was created or updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"consent": ConsentType
}ConfirmSiteworksAppointmentSlot
The possible errors that can be raised are:
- KT-GB-4219: Property does not exist.
- KT-GB-4220: No account currently active at property.
- KT-GB-4221: Could not confirm duplicate property.
- KT-GB-4228: Cannot currently book appointments for legacy prepay meters.
- KT-GB-4229: A smart meter exchange appointment for this date already exists.
- KT-GB-4210: Bookings not supported for agent appointed at property.
- KT-GB-4211: Timeslot no longer available.
- KT-GB-4212: Missing or invalid data for account or property.
- KT-GB-4234: Booking service currently unavailable.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"siteworksAppointment": ActiveAppointmentType
}ConsentType
A consent given by a signing identity for a consent type.
Fields
| Name | Description |
|---|---|
|
Unique code given to this consent type. |
|
id of the consent. |
|
The type of the consent. |
|
Value of the consent. |
Example
{
"id": 1,
"code": "abc123",
"value": "ACCEPTED",
"type": ConsentTypeType
}ConsentTypeType
A type of consent that a signing identity can accept or reject to.
Fields
| Name | Description |
|---|---|
|
Unique code given to this consent type. |
|
Default value of the consent type. |
|
Description of the consent type. |
|
Name of the consent type. |
Example
{
"code": "abc123",
"description": "abc123",
"name": "abc123",
"defaultValue": "ACCEPTED"
}Fields
| Name | Description |
|---|---|
|
The description for each kind of Constantine. |
|
The name describing which kind of Constantine this Constantine is. |
|
If the user has caught this Constantine in the cache period. |
|
How many prize entries catching this Constantine is worth. |
|
How rare this kind of Constantine is expressed as en enum associated to a percentage value. |
|
The slug for this kind of Constantine. |
|
Unique Identifier for the Constantine. |
Example
{
"displayName": "abc123",
"slug": "abc123",
"rarity": "Popular",
"description": "abc123",
"prizeEntries": 1,
"spawnId": "abc123",
"isCaught": true
}Fields
| Name | Description |
|---|---|
|
The datetime of when the list of Constantines will expire. |
|
A List of Constantines. |
Example
{
"constantines": [ConstantineSpawn],
"cacheExpiry": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The description for each kind of Constantine. |
|
The name describing which kind of Constantine this Constantine is. |
|
How many prize entries catching this Constantine is worth. |
|
How rare this kind of Constantine is expressed as en enum associated to a percentage value. |
|
The slug for this kind of Constantine. |
Example
{
"displayName": "abc123",
"slug": "abc123",
"rarity": "Popular",
"description": "abc123",
"prizeEntries": 1
}ConstituentConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ConstituentEdge,
"totalCount": 1,
"edgeCount": 1
}ConstituentEdge
A Relay edge containing a Constituent and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ConstituentInterface,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"startDate": "2020-01-01",
"endDate": "2020-01-01",
"quantity": "1.0",
"unit": "kWh",
"usageCost": 1,
"supplyCharge": 1
}Fields
| Name | Description |
|---|---|
|
Unique identifier of the source of the usage. |
|
Human readable name of what the usage is for. |
|
Monthly usage in pence. First month is January. |
Example
{
"sourceName": "abc123",
"sourceId": "abc123",
"usage": [1]
}ConsumptionBreakdownConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ConsumptionBreakdownConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ConsumptionBreakdownConnectionTypeEdge
A Relay edge containing a ConsumptionBreakdownConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ConsumptionBreakdownType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Charges grouped per displayed period. |
|
Name of the market the charges are for. |
Example
{
"marketName": "abc123",
"charges": ChargesBreakdownConnectionTypeConnection
}ConsumptionConnection
Pagination for energy consumption readings.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ConsumptionEdge,
"totalCount": 1,
"edgeCount": 1
}Example
{
"day": "1.0",
"night": "1.0"
}ConsumptionEdge
A Relay edge containing a Consumption and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ConsumptionType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"elecAnnualConsumptionStandard": 1,
"elecAnnualConsumptionDay": 1,
"elecAnnualConsumptionNight": 1,
"gasAnnualConsumption": 1
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"low": ConsumptionEstimate,
"medium": ConsumptionEstimate,
"high": ConsumptionEstimate
}ConsumptionType
Energy consumption between two points in time.
Example
{
"value": "1.0",
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Email. |
|
First name. |
|
Last name. |
|
Phone. |
Example
{
"firstName": "abc123",
"lastName": "abc123",
"email": "abc123",
"phone": "abc123"
}Contract
A legally binding relationship agreed with a subject (e.g. an account).
Fields
| Name | Description |
|---|---|
|
Date when the contract was cancelled, null if not cancelled. |
|
Unique identifier for the contract. |
|
The current version information for this contract. |
|
The party (Account or Business) that entered into this contract |
|
Date when the contract was signed. |
|
The status of the contract. |
|
The accounts impacted by this contract |
|
The terms of the contract. |
|
Title of the contract. |
|
Date from which the contract is valid. |
|
Date until which the contract is valid, null if the contract is rolling. |
Example
{
"identifier": NonEmptyString,
"title": "abc123",
"party": ContractParty,
"subject": [AccountType],
"status": "REVOKED",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"signedAt": "2020-01-01T00:00:00.000Z",
"cancelledAt": "2020-01-01T00:00:00.000Z",
"lifecycle": ContractVersion,
"terms": TermInterface
}ContractMetaDataType
Represents additional metadata for a contract term.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The additional metadata of the contract. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true,
"metadata": {"key": "value"}
}ContractTerminationInstigated
Contract termination was successfully instigated.
Fields
| Name | Description |
|---|---|
|
The message to display to the user on termination instigation. |
Example
{
"message": "abc123"
}ContractVersion
Represents a version of a contract with its effective date.
Fields
| Name | Description |
|---|---|
|
The date from which this version of the contract becomes effective. |
|
The reference number for this contract version. |
Example
{
"versionReference": 1,
"effectiveFrom": "2020-01-01T00:00:00.000Z"
}ContributionAgreementType
A single Contribution Agreement.
Fields
| Name | Description |
|---|---|
|
The start datetime of the agreement. |
|
The end datetime of the agreement, if any. |
|
The amount contributed per interval. Note, this is in the smallest domination that the currecy support. e.g. Pence, Cents, Yen, etc. |
|
The scheme to which the agreement contributes. |
|
|
|
The frequency of contributions. |
|
The periods over which contributions have been made. |
Example
{
"id": "abc123",
"contributionScheme": ContributionSchemeType,
"interval": "MONTHLY",
"activeFrom": "2020-01-01T00:00:00.000Z",
"activeTo": "2020-01-01T00:00:00.000Z",
"amount": 1,
"periods": ContributionPeriodConnection
}ContributionPeriodConnection
Pagination for contribution periods.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ContributionPeriodEdge,
"totalCount": 1,
"edgeCount": 1
}ContributionPeriodEdge
A Relay edge containing a ContributionPeriod and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ContributionPeriodType,
"cursor": "abc123"
}ContributionPeriodType
A single Contribution Period.
Fields
| Name | Description |
|---|---|
|
|
|
When the contribution was fulfilled |
|
|
|
The datetime the marks the beginning of the period. |
|
The datetime the marks the end of the period. |
Example
{
"id": "abc123",
"agreement": ContributionAgreementType,
"fulfilledAt": "2020-01-01T00:00:00.000Z",
"periodFrom": "2020-01-01T00:00:00.000Z",
"periodTo": "2020-01-01T00:00:00.000Z"
}ContributionSchemeType
A single Contribution Scheme.
Fields
| Name | Description |
|---|---|
|
Is this scheme currently accepting contributions? |
|
|
|
|
|
|
|
Are contributions to this scheme taxable? |
Example
{
"id": "abc123",
"code": "abc123",
"displayName": "abc123",
"taxable": true,
"acceptingContributions": true
}Fields
| Name | Description |
|---|---|
|
The EUID of the controller. |
Example
{
"euid": "abc123"
}Fields
| Name | Description |
|---|---|
|
Controller configuration. |
|
Controller configuration. |
|
List of zones with their configuration and schedules. |
Example
{
"controller": ControllerConfiguration,
"zones": [ZoneInformation],
"heatPump": HeatPumpConfiguration
}Fields
| Name | Description |
|---|---|
|
The controller attached to the account. |
|
The model of the heat pump. |
|
The location at which the device exists. |
|
When the controller was provisioned (at this location for this account). |
Example
{
"controller": Controller,
"heatPumpModel": "abc123",
"location": Location,
"provisionedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
8 character password used to access the access point mode webpage. |
|
Whether or not the controller is currently connected. |
|
Controller firmware options for ESP and EFR chips. |
|
Timezone the controller is in. |
|
When the controller was last reset. |
|
Current state of the controller. |
Example
{
"firmwareConfiguration": FirmwareConfiguration,
"state": "NORMAL_MODE",
"accessPointPassword": "abc123",
"heatPumpTimezone": "abc123",
"connected": true,
"lastReset": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The status and telemetry information of a sensor. |
|
The status and telemetry information of a zone. |
Example
{
"sensors": [SensorStatus],
"zones": [ZoneStatus]
}Example
{
"latitude": 1.0,
"longitude": 1.0
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": CoreSiteworksRequestConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}CoreSiteworksRequestConnectionTypeEdge
A Relay edge containing a CoreSiteworksRequestConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": CoreSiteworksRequestType,
"cursor": "abc123"
}CoreSiteworksRequestType
A Siteworks Request
Fields
| Name | Description |
|---|---|
|
List of appointments linked to this request. |
|
|
|
|
|
|
|
List of supply points on request. |
|
|
|
Example
{
"id": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"status": "abc123",
"reason": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"lastStatusUpdateAt": "2020-01-01T00:00:00.000Z",
"appointments": [OnSiteJobsAppointmentType],
"marketSupplyPoints": SupplyPointConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Consumption in kWh. |
|
Cost in pence (excl. tax). |
|
Cost in pence (incl. tax). |
Example
{
"costOfChargeId": "abc123",
"krakenflexDeviceId": "abc123",
"reportDate": "2020-01-01",
"isSmartCharge": true,
"totalConsumption": 1.0,
"totalCostExclTax": 1.0,
"totalCostInclTax": 1.0
}CostOfUsageConnectionTypeConnection
Dovetailing usage and cost for an account / meter combination over a given time period.
Fields
| Name | Description |
|---|---|
|
Overall cost of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Overall usage of nodes in the edge. |
Example
{
"pageInfo": PageInfo,
"edges": CostOfUsageConnectionTypeEdge,
"cost": 1,
"usageKwh": "1.0"
}CostOfUsageConnectionTypeEdge
A Relay edge containing a CostOfUsageConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": IntervalCostOfUsageType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether cost of usage can be displayed for a user. |
|
Cost of usage for given period. |
|
Energy product direction, e.g. IMPORT or EXPORT. |
Example
{
"costEnabled": true,
"direction": "abc123",
"details": CostOfUsageConnectionTypeConnection
}CreateAPICall
The possible errors that can be raised are:
- KT-CT-7803: Received an invalid apiExceptionId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created APICall. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"apiCall": APICallType
}CreateAPIException
The possible errors that can be raised are:
- KT-CT-7801: Received an invalid operationsTeamId.
- KT-CT-7802: The external identifier already exists.
- KT-CT-7805: Too many tags associated with this API Exception.
- KT-CT-7806: Cannot create duplicate tags for the same API exception.
- KT-CT-7811: Received an invalid assignedUserId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created APIException. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"apiException": APIExceptionType
}CreateAPIExceptionEvent
The possible errors that can be raised are:
- KT-CT-7803: Received an invalid apiExceptionId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created APIExceptionEvent. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"apiExceptionEvent": APIExceptionEventType
}CreateAPIExceptionNote
The possible errors that can be raised are:
- KT-CT-7803: Received an invalid apiExceptionId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created APIExceptionNote. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"apiException": APIExceptionType
}CreateAccountCharge
Add charges to an account.
The possible errors that can be raised are:
- KT-CT-5211: The charge reason with the requested code is deprecated.
- KT-CT-5212: The charge reason with the requested code does not exist.
- KT-CT-5213: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountCharge": AccountChargeType
}CreateAccountCredit
Add credits to an account.
The possible errors that can be raised are:
- KT-CT-5315: Invalid data.
- KT-CT-5314: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountCredit": AccountCreditType
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"postRequest": UploadPostRequest,
"clientMutationId": "abc123"
}CreateAccountNote
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-4180: Account note must be a valid string.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account, which has the added note. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}CreateAccountPaymentSchedule
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-3815: No active payment schedule found for this account.
- KT-CT-3822: Unauthorized.
- KT-CT-3923: Unauthorized.
- KT-CT-3941: Invalid data.
- KT-CT-3942: An unexpected error occurred.
- KT-CT-3947: An unexpected error occurred.
- KT-CT-3960: Invalid value for payment day.
- KT-CT-3961: Cannot update plan-associated payment schedule.
- KT-CT-3962: No new value provided to update payment schedule.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
New payment schedule. |
Example
{
"possibleErrors": [PossibleErrorType],
"schedule": PaymentScheduleType
}CreateAccountReference
Create an account reference.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-8310: Invalid data.
- KT-CT-8311: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountReference": AccountReferenceType
}CreateAccountReminder
The possible errors that can be raised are:
- KT-CT-1401: Invalid data.
- KT-CT-1402: Unable to create account reminder.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account reminder. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountReminder": AccountReminder
}CreateAcquisitionQuoteRequestForProducts
The possible errors that can be raised are:
- KT-GB-4625: Unable to create quote request.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Returns a quote request for the requested product codes. Does not persist the quote. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": QuoteRequestBase
}CreateAffiliateLink
Create an affiliate link for a new sales agent.
The possible errors that can be raised are:
- KT-CT-7711: Invalid data.
- KT-CT-7713: Invalid data.
- KT-CT-7714: Invalid data.
- KT-CT-7715: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created affiliate link. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"affiliateLink": AffiliateLinkType
}CreateAffiliateOrganisation
Create an affiliate organisation.
The possible errors that can be raised are:
- KT-CT-7716: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created affiliate organisation. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"affiliateOrganisation": AffiliateOrganisationType
}CreateAffiliateSession
Create a session for an affiliate link.
Fields
| Name | Description |
|---|---|
|
The created affiliate session |
Example
{
"affiliateSession": AffiliateSessionType
}CreateAudioRecording
The possible errors that can be raised are:
- KT-CT-7720: Invalid S3 key format.
- KT-CT-7721: Link not found.
- KT-CT-7722: Invalid input for audio recording upload.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created audio recording. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"audioRecording": AudioRecordingType
}CreateAutoTopupConfig
Create a new auto topup config for SPAYG meter.
Fields
| Name | Description |
|---|---|
|
The created auto top-up config. |
Example
{
"autoTopupConfig": AutoTopupConfigType
}CreateBusiness
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11108: Invalid data.
- KT-CT-11109: Invalid data.
- KT-CT-11110: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created business. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"business": BusinessType
}CreateCallMetadata
The possible errors that can be raised are:
- KT-CT-11802: Call not found.
- KT-CT-11806: Call metadata item key cannot be an empty string.
- KT-CT-11807: A call metadata item with this key already exists for this call.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The call metadata was attached to. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"call": CallInterface
}CreateCampaignItems
The possible errors that can be raised are:
- KT-CT-11501: Voice campaign not found.
- KT-CT-4178: No account found with given account number.
- KT-CT-11503: One or more campaign items are invalid and cannot be created.
- KT-CT-11504: The batch of campaign items is too large.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The identifier for this batch of items to assist in tracking and logging. |
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"campaignItems": [VoiceCampaignItemType],
"batchIdentifier": "abc123"
}CreateContributionAgreement
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-9601: Invalid data.
- KT-CT-9602: Unable to create contribution agreement.
- KT-CT-9605: Contribution amount cannot be 0 or negative.
- KT-CT-9606: Scheme is not accepting contributions at this time.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created contribution agreement. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"contributionAgreement": ContributionAgreementType
}CreateCreditTransferPermission
Mutation to create a credit transfer permission.
The possible errors that can be raised are:
- KT-CT-3822: Unauthorized.
- KT-CT-3827: The ledger is not valid.
- KT-CT-3828: At least one of the provided ledgers must be a credit storage ledger.
- KT-CT-3829: The credit transfer permission already exists.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Datetime when the credit transfer permission is valid. |
Example
{
"possibleErrors": [PossibleErrorType],
"validFrom": "2020-01-01T00:00:00.000Z"
}CreateCustomerFeedback
The possible errors that can be raised are:
- KT-CT-5516: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created customer feedback object. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"customerFeedback": CustomerFeedbackType
}CreateDepositAgreement
Create a new deposit agreement for the account if it needs one.
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"depositAgreement": CreateDepositAgreementOutput
}Example
{
"depositRequired": true,
"depositAmount": 1
}CreateDirectDebitInstruction
The possible errors that can be raised are:
- KT-CT-3940: Invalid data.
- KT-CT-3923: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"directDebitInstruction": DirectDebitInstructionType
}CreateElectricJuiceAgreement
Create an Electric Juice agreement for an account.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"agreement": Agreement
}CreateElectricJuiceCharge
Create an Electric Juice charge and associated line items.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"accountCharge": AccountChargeType
}CreateElectricJuiceChargeCard
Create a new Electric Juice charge card for an account.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"chargeCard": ChargeCardType
}CreateElectricJuiceCredit
Add a credit to an Electric Juice Network ledger.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"accountCredit": AccountCreditType
}CreateEvPublicChargingAgreement
Create an EV Public Charging agreement.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-5811: Active agreement already exists.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"agreement": Agreement
}CreateExternalAccountEvent
Create an external account event.
The possible errors that can be raised are:
- KT-CT-7123: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The new event data. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"event": ExternalAccountEvent
}CreateExternalAccountUserEvent
Create an external account user event.
The possible errors that can be raised are:
- KT-CT-7123: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The new event data. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"event": ExternalAccountUserEvent
}CreateGoodsPurchase
The possible errors that can be raised are:
- KT-CT-8206: Invalid data.
- KT-CT-1131: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Goods purchase created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"goodsPurchase": GoodsPurchase
}CreateGoodsQuote
The possible errors that can be raised are:
- KT-CT-8202: Invalid data.
- KT-CT-8205: Unable to create quote.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Goods quote created for the customer. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"goodsQuote": GoodsQuote
}CreateGoodsQuoteWithoutAccount
The possible errors that can be raised are:
- KT-CT-8202: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Goods quote created for the customer. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"goodsQuote": GoodsQuote
}CreateHeatPumpGoodsQuote
Create a Goods quote for heat pumps.
This augments the standard goods quote with additional heat pump information.
Fields
| Name | Description |
|---|---|
|
Generated heat pump quote. |
Example
{
"quote": HeatPumpGoodsQuote
}CreateInboundCall
The possible errors that can be raised are:
- KT-CT-11805: Invalid input for creating an inbound call.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The call that was created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"call": InboundCallType
}CreateInkInboundMessagePayload
Register an Ink inbound message.
Fields
| Name | Description |
|---|---|
|
|
|
The Ink message that was created. |
Example
{
"message": InkMessage,
"clientMutationId": "abc123"
}CreateMetadata
Create metadata on an object.
The possible errors that can be raised are:
- KT-CT-8412: Invalid data.
- KT-CT-8414: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"metadata": Metadata
}Fields
| Name | Description |
|---|---|
|
Deprecated The 'id' field is deprecated. |
|
Example
{
"readingErrors": [SerializerFieldErrorsType],
"id": "abc123"
}CreateOctoplusRewardContactLink
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
- KT-GB-9319: This feature is not currently available.
- KT-GB-9323: Could not create contact link.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The URL of the customer contact form link. |
Example
{
"possibleErrors": [PossibleErrorType],
"url": "abc123"
}CreateOfferGroupForQuoting
Create a quoting offer group.
The possible errors that can be raised are:
- KT-CT-12401: Unable to create offer group.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Quoting offer group. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"offerGroup": OfferGroupType
}CreateOpportunity
The possible errors that can be raised are:
- KT-CT-8912: Funnel not found.
- KT-CT-8919: Funnel initial stage not set.
- KT-CT-8920: Extra details contains invalid key.
- KT-CT-8911: Unable to create opportunity.
- KT-CT-8907: Lead not found.
- KT-CT-8901: Unable to create lead.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The date the opportunity was created. |
|
The code of the funnel. |
|
The unique number of the opportunity. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The stage of the opportunity. |
Example
{
"possibleErrors": [PossibleErrorType],
"opportunityNumber": "abc123",
"dateOfCreation": "2020-01-01T00:00:00.000Z",
"stage": "abc123",
"funnelCode": "abc123"
}CreateOrUpdateLoyaltyCardMutation
Create a Loyalty Card for the given account user.
The possible errors that can be raised are:
- KT-CT-5412: No account user exists with the given id.
- KT-CT-8610: Invalid data.
- KT-CT-8611: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Created or updated loyalty card. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"loyaltyCard": LoyaltyCardType
}CreateOrUpdateSiteworksAppointment
Create a new job or update the status of an existing one.
The possible errors that can be raised are:
- KT-CT-1112: 'Authorization' header not provided.
- KT-CT-4231: Unauthorized.
- KT-GB-4230: Invalid data.
- KT-GB-4224: Error processing siteworks appointment.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"result": CreateOrUpdateSiteworksAppointmentOutput
}Example
{
"appointmentCreated": true,
"appointmentUpdated": true
}CreatePaymentSchedule
Mutation for creating an Payment Schedule instance using the authenticated user.
The possible errors that can be raised are:
- KT-GB-3917: Unable to create payment schedule.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentSchedule": PaymentScheduleType
}CreatePortfolio
Create a new portfolio.
The possible errors that can be raised are:
- KT-CT-9402: Received an invalid brandCode.
- KT-CT-9401: Received an invalid operationsTeamId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created portfolio. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"portfolio": PortfolioType
}CreatePortfolioUserRole
The possible errors that can be raised are:
- KT-CT-9403: Received an invalid portfolioId.
- KT-CT-9404: Received an invalid accountUserId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created role for a user in association with a portfolio. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"portfolioUserRole": PortfolioUserRoleType
}CreatePostEvents
Create post delivery events from external vendors.
The possible errors that can be raised are:
- KT-CT-9907: Post events batch size exceeded.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Number of events successfully created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"createdEventsCount": 1
}CreateProductOutput
Output type for creating a product.
Fields
| Name | Description |
|---|---|
|
The created product. |
Example
{
"product": SupplyProductType
}CreateProductRates
Create one or more product rates for a product.
The possible errors that can be raised are:
- KT-GB-9514: No available product found.
- KT-GB-9518: Invalid input data for product rate(s).
- KT-GB-9519: Unable to create product rate(s).
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Successfully created rate(s) for the specified product. |
Example
{
"possibleErrors": [PossibleErrorType],
"productRates": [ProductRateType]
}CreateProvisioningClaim
Create an AWS provisioning claim certificate.
Fields
| Name | Description |
|---|---|
|
The temporary provisioning certification. |
Example
{
"tempProvisioningClaimCert": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType
}CreateQuoteForAccount
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
- KT-CT-4616: Unable to create a quote.
- KT-CT-4631: Unable to quote for the chosen market.
- KT-CT-4645: No supply point found belonging to the account for the provided identifier.
- KT-CT-4924: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Returns a quote request. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": MarketSupplyQuoteRequestType
}Fields
| Name | Description |
|---|---|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"errors": [SerializerFieldErrorsType],
"quote": QuoteType
}CreateQuoteRequestForProducts
The possible errors that can be raised are:
- KT-GB-4624: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Returns a quote request for the requested product codes. Does not persist the quote. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": QuoteRequestBase
}CreateReferral
Use a referral code to create a referral and trigger a referral reward. This is for customers to refer other customers so it only works with friend referrals and not partner referrals. This will try to find a user with given referral code as their personal referral code. If found, it will create an AccountReferral instance for the given account number.
The possible errors that can be raised are:
- KT-CT-6723: Unauthorized.
- KT-CT-6710: Unable to create referral.
- KT-CT-6711: Accounts may not self-refer.
- KT-CT-6713: Referring and referred account brands do not match.
- KT-CT-6712: Invalid reference.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The reward amount to be issued to the referred account, in smallest currency subunits. |
Example
{
"possibleErrors": [PossibleErrorType],
"referredAccountRewardAmount": 1
}CreateRefundRequest
Mutation for creating an refund request for an account.
The possible errors that can be raised are:
- KT-GB-4127: Unable to send refund request confirmation email.
- KT-GB-4121: Unable to process refund request.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"refundRequest": RefundRequestType
}CreateReminder
The possible errors that can be raised are:
- KT-CT-1401: Invalid data.
- KT-CT-1402: Unable to create account reminder.
- KT-CT-1403: Missing user or team assignee.
- KT-CT-1404: This reminder type is deprecated.
- KT-CT-1405: Both user and team assignee provided.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Account reminder. |
Example
{
"possibleErrors": [PossibleErrorType],
"reminder": Reminder
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"quoteRequest": QuoteRequest
}CreateScheduledTransactions
Mutation to create scheduled transactions.
The possible errors that can be raised are:
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-3830: Invalid action.
- KT-CT-3831: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"scheduledTransactions": [ScheduledTransactionType]
}CreateShellAccountPayload
Create a shell account (a billable account with no property/energy supply).
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"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",
"password": "abc123",
"passwordUpdateToken": "abc123",
"urn": "abc123",
"errors": [ErrorType],
"account": AccountInterface,
"clientMutationId": "abc123"
}Fields
| Name | Description |
|---|---|
|
Example
{
"eventCreated": true
}CreateSiteworksEventExternal
Makes it possible to create Sitework events by external third parties.
This mutation uses the external JWT authorization method.
The possible errors that can be raised are:
- KT-GB-4222: The provided 'siteworksRequestId' is not a valid UUID.
- KT-GB-4223: Siteworks request not found. Check the provided 'siteworksRequestId' is correct.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"eventCreated": true
}CreateSnap
The possible errors that can be raised are:
- KT-GB-9316: Account is not Octoplus-enrolled.
- KT-GB-9325: Invalid constantine slug.
- KT-GB-9326: Invalid spawn ID.
- KT-GB-9319: This feature is not currently available.
- KT-GB-9327: Snap failed to create.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Returns true if snap was successfully created. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}CreateSupplyPointMetadata
The possible errors that can be raised are:
- KT-CT-8412: Invalid data.
- KT-CT-8414: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created metadata. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"metadata": Metadata
}Credit
A credit to the customer from the energy retailer.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the account the transaction belongs to. |
|
Gross amount including tax (when payable). Refer to the Deprecated The 'amount' field is deprecated. |
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The customer's resulting balance after this transaction has been applied, in the smallest unit of currency. |
|
The unique identifier for the most recent billing document linked with the transaction.Note: a transaction may be linked with multiple documents, but this field will only return the identifier for the most recent billing document. |
|
The date time when the transaction is created. |
|
Returns True if the transaction is linked with a statement. |
|
|
|
Deprecated. Deprecated The 'isAccountCharge' field is deprecated. |
|
Deprecated. Deprecated The 'isAccountPayment' field is deprecated. |
|
Deprecated. Deprecated The 'isCredit' field is deprecated. |
|
Whether the statement this transaction is on has been held. A held statement is not sent to a customer automatically, but is instead marked for manual attention by operations staff. Returns False if a statement is not linked with the transaction. |
|
Whether this transaction has been issued on any billing document.Note: Look for the most recently issued transaction instead of looking through all transactions as some accounts may have initial transactions that were not issued.This will return False if the transaction is not associated with any billing documents. |
|
|
|
Returns the note field value for the transaction, which contains additional info. |
|
|
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123",
"amount": 1,
"amounts": TransactionAmountType,
"balanceCarriedForward": 1,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "abc123",
"billingDocumentIdentifier": "abc123",
"statementId": "abc123",
"isReversed": true,
"hasStatement": true,
"note": "abc123",
"reasonCode": "abc123"
}Fields
| Name | Description |
|---|---|
|
The credit reason code. |
|
The credit reason display text. |
|
The group the credit reason belongs to (if applicable). |
|
Whether the credit reason is deprecated. |
|
Whether the credit reason is hidden. |
|
Whether the credit reason is sales tax exempt. |
Example
{
"code": "abc123",
"display": "abc123",
"isDeprecated": true,
"isTaxExempt": true,
"isHidden": true,
"group": "abc123"
}Fields
| Name | Description |
|---|---|
|
The number of the account linked to this permission. |
|
The number of the ledger linked to this permission. |
|
The datetime from which the permission is valid. |
|
The datetime to which the permission is valid. |
Example
{
"ledgerNumber": "abc123",
"accountNumber": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The number of the account linked to this permission. |
|
The number of the ledger linked to this permission. |
|
The datetime from which the permission is valid. |
|
The datetime to which the permission is valid. |
Example
{
"ledgerNumber": "abc123",
"accountNumber": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Permissions for credit transfers when the ledger is the target. |
|
Permissions for credit transfers when the ledger is the source. |
Example
{
"fromSourceLedgers": [CreditTransferPermissionFromSourceLedgerType],
"toTargetLedgers": [CreditTransferPermissionToTargetLedgerType]
}CustomerFeedbackFormConnectionTypeConnection
Paginator of Customer Feedback Form.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": CustomerFeedbackFormConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}CustomerFeedbackFormConnectionTypeEdge
A Relay edge containing a CustomerFeedbackFormConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": CustomerFeedbackFormType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The unique identifier for the customer feedback form. |
|
The name of the customer feedback form. |
Example
{
"id": "abc123",
"name": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The value attached to the source |
|
The datetime the feedback was submitted |
Example
{
"id": "abc123",
"rawScore": 1,
"submittedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The account number. |
|
The ledger identifier. |
Example
{
"accountNumber": "abc123",
"ledgerNumber": "abc123"
}Fields
| Name | Description |
|---|---|
|
The account number. |
|
The agency. |
|
The campaign. |
|
Whether the commencement could be applied. |
|
The ledger identifier. |
Example
{
"commencementStatus": true,
"accountNumber": "abc123",
"ledgerNumber": "abc123",
"agency": "abc123",
"campaign": "abc123"
}Fields
| Name | Description |
|---|---|
|
The account number. |
|
Whether the update has been applied. |
Example
{
"commencementStatus": true,
"accountNumber": "abc123"
}Dashboard
A list of components which comprise a dashboard screen.
Fields
| Name | Description |
|---|---|
|
The list of sections for a dashboard. |
|
Unique identifier of the object. |
|
The serialised dashboard items. |
|
The name of the object's type. |
Example
{
"id": "abc123",
"typename": "abc123",
"dashboardItems": SectionType,
"serialisedDashboardItems": "abc123"
}Fields
| Name | Description |
|---|---|
|
The cursor of the last item. |
|
Whether there are more items when paginating forwards. |
|
Whether there are previous items when paginating backwards. |
|
The cursor of the first item. |
Example
{
"startCursor": "2020-01-01T00:00:00.000Z",
"endCursor": "2020-01-01T00:00:00.000Z",
"hasPreviousPage": true,
"hasNextPage": true
}Fields
| Name | Description |
|---|---|
|
|
|
Is EPG applied to the unit rate. |
|
|
|
|
|
|
|
|
|
Whether the tariff is for exporting energy. |
|
|
|
Is EPG applied to the unit rate. |
|
|
|
|
|
|
|
|
|
|
|
Describes a particular tariff by combining the product code, number of rates, available from date and GSP code. |
Example
{
"id": "abc123",
"displayName": "abc123",
"fullName": "abc123",
"description": "abc123",
"productCode": "abc123",
"standingCharge": 1.0,
"preVatStandingCharge": 1.0,
"tariffCode": "abc123",
"isExport": true,
"dayRate": 1.0,
"dayRateEpgApplied": true,
"nightRate": 1.0,
"nightRateEpgApplied": true,
"preVatDayRate": 1.0,
"preVatNightRate": 1.0
}DeauthenticateDevice
De-authenticate a registered device.
The possible errors that can be raised are:
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4350: Unable to de-authenticate device.
- KT-CT-4352: This device cannot currently be de-authenticated.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": DeviceDetailsType
}DeauthenticateFlexDevice
De-authenticate a registered device by device id.
The possible errors that can be raised are:
- KT-CT-4350: Unable to de-authenticate device.
- KT-CT-4352: This device cannot currently be de-authenticated.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": DeviceDetailsType
}Example
{
"name": "abc123",
"code": "abc123",
"isActive": true
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"code": "abc123",
"displayName": "abc123",
"deprecatedAt": "2020-01-01T00:00:00.000Z",
"requiresFieldVisit": true
}Fields
| Name | Description |
|---|---|
|
The agency responsible for the collection proceedings. |
|
|
|
The campaign type of the collection proceedings. Deprecated The 'campaign' field is deprecated. |
|
The campaign type of the collection proceedings. |
|
|
|
|
|
Example
{
"agency": DebtCollectionAgencyType,
"campaign": "VULNERABLE_CUSTOMER",
"amount": 1,
"startedAt": "2020-01-01T00:00:00.000Z",
"stoppedAt": "2020-01-01T00:00:00.000Z",
"stopReason": "BANKRUPT",
"collectionCampaign": DebtCollectionCampaignType
}DecommissionSmartDevice
The possible errors that can be raised are:
- KT-GB-4024: The provided device ID does not match any devices known by Kraken.
- KT-GB-4025: Error sending the request to decommission the device.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The reference of the Decommission Request in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}DeductLoyaltyPoints
Deduct a set amount of loyalty points from an account.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-5420: Unauthorized.
- KT-CT-9211: Invalid reason for loyalty points award.
- KT-CT-9219: Loyalty points user not found.
- KT-CT-9204: Negative or zero points set.
- KT-CT-9205: Insufficient Loyalty Points.
- KT-CT-9208: Invalid posted at datetime.
- KT-CT-9221: Idempotency key already used on ledger entry.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The ledger entry for the deducted loyalty points |
|
The number of loyalty points that were deducted. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"pointsDeducted": 1,
"ledgerEntry": LoyaltyPointLedgerEntryType
}DeeplinkActionType
An action which navigates to the URL of another backend screen.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the object. |
|
The name of the action object's type. |
|
The name of the object's type. |
|
The URL to navigate to. |
Example
{
"typeName": "abc123",
"id": "abc123",
"typename": "abc123",
"url": "abc123"
}DefaultElectricJuicePaymentInstructionType
Payment Instructions
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"instructionType": "abc123",
"cardPaymentNetwork": "abc123",
"cardExpiryMonth": 1,
"cardExpiryYear": 1,
"validFrom": "2020-01-01T00:00:00.000Z",
"vendor": "abc123",
"cardNumber": "abc123",
"cardType": "abc123"
}DelayerDaysType
Represents delayer days for active payment in a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true
}DeleteAccountReference
Delete a reference for a particular account and namespace.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-8310: Invalid data.
- KT-CT-8312: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountReference": DeleteAccountReferenceType
}Fields
| Name | Description |
|---|---|
|
The namespace associated with the removed AccountReference. |
Example
{
"namespace": "abc123"
}DeleteBoostCharge
The possible errors that can be raised are:
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4354: Unable to cancel boost charge.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}DeletePushNotificationBinding
The possible errors that can be raised are:
- KT-CT-5411: Invalid token or no push notification binding found for the given account user.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"status": "SUCCESSFUL"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"depositKey": "abc123",
"depositAmount": 1,
"acceptedAt": "2020-01-01T00:00:00.000Z",
"fulfilledAt": "2020-01-01T00:00:00.000Z"
}DeprovisionHeatingController
De-provision a heating controller device.
The possible errors that can be raised are:
- KT-CT-4307: Error deprovisioning an Octopus heat pump.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The message to display to the user upon successful device de-provisioning. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": "abc123"
}DeviceChargingSessionConnection
Paginator for device charging session.
Fields
| Name | Description |
|---|---|
|
Contains the nodes in this connection. |
|
Information to aid in DateTime pagination. |
Example
{
"pageInfo": DateTimePageInfo,
"edges": DeviceChargingSessionEdge
}DeviceChargingSessionEdge
A Relay edge containing a DeviceChargingSession and its cursor.
Fields
| Name | Description |
|---|---|
|
The cursor of the item. |
|
The item at the end of the edge |
Example
{
"node": DeviceChargingSession,
"cursor": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The type of device. |
|
|
|
The third party that provides control over this device. |
Example
{
"krakenflexDeviceId": "abc123",
"provider": "BYD",
"deviceType": "BATTERIES"
}DeviceRegistration
Register a device for smart controlling.
Where device refers to batteries, electric vehicles, heat pumps or thermostats.
The possible errors that can be raised are:
- KT-CT-4324: Device already registered error.
- KT-CT-4321: Serializer validation error.
- KT-CT-4312: Unable to register device.
- KT-CT-4363: No capable devices found.
- KT-CT-4364: Multiple devices found.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Device ID(s) of the registered device(s). |
Example
{
"possibleErrors": [PossibleErrorType],
"registeredDeviceIds": ["abc123"]
}Fields
| Name | Description |
|---|---|
|
Timestamp of the reading. |
|
Value of the reading. |
Example
{
"value": 1.0,
"timestamp": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Device charging power in kilowatts (kW) - negative for import, positive for export. |
|
Energy stored in the device in kilowatt-hours (kWh). |
|
State of charge of the battery in % (may not be a whole number). |
Example
{
"activePowerInKw": DeviceStatusReadingType,
"energyInKwh": DeviceStatusReadingType,
"socPercentage": DeviceStatusReadingType
}Fields
| Name | Description |
|---|---|
|
The maximum export power of the device in kilowatts. |
|
The maximum import power of the device in kilowatts. |
|
Whether device is connected. |
|
Device status telemetry readings. |
|
The lifecycle status of the device. Deprecated The 'status' field is deprecated. |
|
Whether control of the device has been temporarily suspended. |
Example
{
"status": "ONBOARDING",
"suspended": true,
"maxImportInKw": 1.0,
"maxExportInKw": 1.0,
"pluggedIn": true,
"readings": DeviceStatusReadingsType
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": DirectDebitInstructionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}DirectDebitInstructionConnectionTypeEdge
A Relay edge containing a DirectDebitInstructionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": DirectDebitInstructionType,
"cursor": "abc123"
}DirectDebitInstructionType
Direct Debit Instructions
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The last four digits of the account number. Deprecated The 'lastFourDigitsOfAccountNumber' field is deprecated. |
|
A masked reference to a recurring payment method. |
|
A masked version of the IBAN. |
|
The owners of the financial account this instruction represents. |
|
|
|
Example
{
"id": "abc123",
"status": "abc123",
"sortCode": "abc123",
"iban": "abc123",
"accountHolder": "abc123",
"instructionType": "abc123",
"cardPaymentNetwork": "abc123",
"cardExpiryMonth": 1,
"cardExpiryYear": 1,
"lastFourDigitsOfAccountNumber": "abc123",
"maskedAccountIdentifier": "abc123",
"maskedIban": "abc123",
"owners": [PaymentInstructionOwnerType]
}Fields
| Name | Description |
|---|---|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"paymentSchedule": PaymentScheduleType,
"errors": [ErrorType]
}DisableAutoTopup
Disable auto topup for SPAYG meter.
Fields
| Name | Description |
|---|---|
|
Boolean indicating if the auto top-up was successfully disabled. |
Example
{
"success": true
}Fields
| Name | Description |
|---|---|
|
The discount as a decimal between 0 and 1. |
|
This type will return additional market specific information. For example, some markets support wind direction, fan speed, wind speed, etc. while others do not. |
|
Timestamp for the discount. |
Example
{
"startAt": "2020-01-01T00:00:00.000Z",
"discount": "1.0",
"metaData": FanClubMetadataOutput
}Fields
| Name | Description |
|---|---|
|
The start time that the ensemble forecast simulation. |
|
Discount forecast data-points. |
Example
{
"baseTime": "2020-01-01T00:00:00.000Z",
"data": ForecastData
}Fields
| Name | Description |
|---|---|
|
Example
{
"earliestPossibleDirectDebitPaymentDate": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
Connection type. |
|
Connection type effective from date. |
|
Connection type end date. |
|
Consumer Type. |
|
Current supplier as supplied via CSS messages. |
|
Current supply start date via CSS messages. |
|
Data Aggregator appointment effective from date. |
|
Data Aggregator MPID. |
|
Data Collector appointment effective from date. |
|
Data Collector MPID. |
|
Data Communications Company Service Flag. |
|
Data Communications Company Service Flag effective from date. |
|
Distributor MPID. |
|
Domestic Consumer Indicator supplied via CSS messages. |
|
Energisation status. |
|
Energisation status effective from date. |
|
Energy direction. |
|
Energy direction effective from date. |
|
Energy direction end date. |
|
Indicates if a Green Deal is currently active for this MPAN. |
|
Grid Supply Point Group effective from date. |
|
Grid Supply Point Group Id. |
|
In Home Display Install status. |
|
In Home Display Install status effective from date. |
|
Line Loss Factor Class. |
|
Line Loss Factor Class effective from date. |
|
Measurement Class. |
|
Measurement Class effective from date. |
|
Meter Operator appointment effective from date. |
|
Meter Operator MPID. |
|
Meter Time-switch Class. |
|
Meter Time-switch Class effective from date. |
|
Metered Indicator. |
|
Metered Indicator effective from date. |
|
Metered Indicator end date. |
|
List of meter details. |
|
MPAN. |
|
Profile Class. |
|
Profile Class effective from date. |
|
Relationship Status Indicator. |
|
RMP State. |
|
RMP State effective from date. |
|
Smart Metering Equipment Technical Specification version. |
|
Smart Metering System Operator effective from date. |
|
Smart Metering System Operator MPID. |
|
Standard Settlement Configuration. |
|
Standard Settlement Configuration effective from date. |
|
Effective from date of the current supplier. |
|
Supplier MPID. |
|
MPAN trading status. |
|
MPAN trading status effective from date. |
Example
{
"mpan": "abc123",
"distributorMpid": "abc123",
"tradingStatus": "abc123",
"tradingStatusEfd": "2020-01-01",
"gspGroupId": "abc123",
"gspGroupEfd": "2020-01-01",
"lineLossFactor": "abc123",
"lineLossFactorEfd": "2020-01-01",
"dccServiceFlag": "abc123",
"dccServiceFlagEfd": "2020-01-01",
"greenDealInEffect": "abc123",
"supplierMpid": "abc123",
"supplierEfd": "2020-01-01",
"energisationStatus": "abc123",
"energisationStatusEfd": "2020-01-01",
"profileClass": 1,
"profileClassEfd": "2020-01-01",
"standardSettlementConfiguration": "abc123",
"standardSettlementConfigurationEfd": "2020-01-01",
"meterTimeswitchClass": 1,
"meterTimeswitchClassEfd": "2020-01-01",
"measurementClass": "abc123",
"measurementClassEfd": "2020-01-01",
"dataAggregatorMpid": "abc123",
"dataAggregatorEfd": "2020-01-01",
"dataCollectorMpid": "abc123",
"dataCollectorEfd": "2020-01-01",
"meterOperatorMpid": "abc123",
"meterOperatorEfd": "2020-01-01",
"smsoMpid": "abc123",
"smsoEfd": "2020-01-01",
"ihdStatus": "abc123",
"ihdStatusEfd": "2020-01-01",
"smetsVersion": "abc123",
"meteredIndicator": true,
"meteredIndicatorEfd": "2020-01-01",
"meteredIndicatorEtd": "2020-01-01",
"consumerType": "abc123",
"domesticConsumerIndicator": true,
"relationshipStatusIndicator": "abc123",
"rmpState": "abc123",
"rmpStateEfd": "2020-01-01",
"cssSupplierMpid": "abc123",
"cssSupplyStartDate": "2020-01-01",
"energyDirection": "abc123",
"energyDirectionEfd": "2020-01-01",
"energyDirectionEtd": "2020-01-01",
"connectionType": "abc123",
"connectionTypeEfd": "2020-01-01",
"connectionTypeEtd": "2020-01-01",
"meters": [ElectricMeterTechnicalSubDetails]
}Fields
| Name | Description |
|---|---|
|
ESME ID. |
|
Installing Supplier DIP ID, 10 characters. |
|
Installing Supplier MPID. |
|
Meter Asset Provider DIP ID, 10 characters. |
|
Meter Asset Provider MPID. |
|
Meter Install Date. |
|
Meter location. |
|
Meter manufacturer. |
|
Meter Serial Number. |
|
Meter Type. |
|
Number of register digits. |
Example
{
"installingSupplierMpid": "abc123",
"meterSerialNumber": "abc123",
"meterType": "abc123",
"meterInstallDate": "2020-01-01",
"mapMpid": "abc123",
"esmeId": "abc123",
"meterLocation": "abc123",
"registerDigits": 1,
"installingSupplierDipId": "abc123",
"mapDipId": "abc123",
"meterManufacturer": "abc123"
}Fields
| Name | Description |
|---|---|
|
This field is replacing |
|
|
|
|
|
Shows the availability status of an integration. |
|
|
|
|
|
|
|
|
|
Example
{
"vehicleId": 1,
"model": "abc123",
"year": 1,
"availableFrom": 1,
"availableTo": 1,
"batterySize": "1.0",
"supportedProviders": ["abc123"],
"isIntegrationLive": true,
"integrationStatus": "INTERNAL_TESTING"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "abc123",
"models": [ElectricVehicleModelType]
}ElectricityAgentContractType
An organization who manages a given meterpoint.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"contractType": "MOP",
"effectiveFrom": "2020-01-01",
"agentId": "abc123",
"contractStatus": "ACCEPTED"
}Fields
| Name | Description |
|---|---|
|
|
|
The datetime the agreement was entered. |
|
The datetime the agreement was terminated. |
|
Bespoke rates that apply to this agreement. |
|
Bespoke standing charges that apply to this agreement. |
|
The ID of the agreement. |
|
Whether the agreement is revoked. |
|
A collection of charges and associated consumption data. |
|
|
|
List of contracted standing charge uplifts applicable during this agreement's duration. This is only applicable to business accounts where we may pay commission to a third-party intermediary. |
|
|
|
List of contracted unit rate uplifts applicable during this agreement's duration. This is only applicable to business accounts where we may pay commission to a third-party intermediary. |
|
The start datetime of the agreement. |
|
The end datetime of the agreement. |
Example
{
"id": 1,
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"agreedFrom": "2020-01-01T00:00:00.000Z",
"agreedTo": "2020-01-01T00:00:00.000Z",
"account": AccountType,
"meterPoint": ElectricityMeterPointType,
"tariff": ElectricityTariffType,
"isRevoked": true,
"lineItems": LineItemConnection,
"unitRateUplifts": [ElectricityContractUnitRateUplift],
"standingChargeUplifts": [ElectricityContractStandingChargeUplift],
"bespokeRates": [ElectricityBespokeRate],
"bespokeStandingCharges": [ElectricityBespokeStandingCharge]
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"value": "1.0",
"paymentMethod": "DIRECT_DEBIT",
"rateType": "STANDARD"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"value": "1.0",
"paymentMethod": "DIRECT_DEBIT"
}Example
{
"day": 1,
"night": 1,
"isEstimate": true
}Example
{
"consumption": 1,
"isEstimate": true
}Example
{
"day": 1,
"night": 1,
"offPeak": 1,
"isEstimate": true
}Fields
| Name | Description |
|---|---|
|
The estimated Electricity Annual Consumption measured in kWh. |
|
The date from which the EAC is calculated. |
|
A flag stating if the meterpoint has ever had an erroneous transfer of supplier. |
|
The date the meterpoint switched to the current supplier. |
|
The current supplier for the meterpoint. |
Example
{
"eac": 1.0,
"eacEffectiveFromDate": "2020-01-01",
"supplierName": "abc123",
"supplierEffectiveFromDate": "2020-01-01",
"hasErroneousTransfer": true
}Fields
| Name | Description |
|---|---|
|
The amount to add to the standing charge when billing, in pence per day. |
|
When this contract is valid from. |
|
When this contract is valid until. |
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"standingChargeUplift": "1.0"
}Fields
| Name | Description |
|---|---|
|
The amount to add to the unit rate when billing, in pence/kWh. |
|
When this contract is valid from. |
|
When this contract is valid until. |
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"unitRateUplift": "1.0"
}Fields
| Name | Description |
|---|---|
|
The identifier of the 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. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The identifier of the register associated to this reading. |
Example
{
"readingDirection": "CONSUMPTION",
"registerId": "abc123",
"readingQuality": "ACTUAL",
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "abc123",
"deviceId": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
Line 1 of the address returned from the search. |
|
Line 2 of the address returned from the search. |
|
List of meterpoints associated with the address. Only returned if addresshasmorethanoneelectricitymeter_point is True. |
|
The postcode of the address returned from the search. |
Example
{
"addressHasMoreThanOneElectricityMeterPoint": true,
"electricityMeterPoints": ["abc123"],
"addressLine1": "abc123",
"addressLine2": "abc123",
"postcode": "abc123"
}ElectricityMeterPointType
An electricity meterpoint is a collection of meters. Meters can be changed over time, so it is convenient to keep an invariant reference. Sometimes there are multiple active meters on a meterpoint at a time (eg ECO10), but expect that to be an edge case.
Fields
| Name | Description |
|---|---|
|
A list of agents responsible for management of the meterpoint. |
|
A list of electricity agreements belonging to an account that is linked to the viewer. Filters out expired agreements by default. |
|
Whether it is possible to renew the meter point's tariff. |
|
The current MPID for this meter point. |
|
|
|
|
|
Indicates whether the electricity meter point is an import or an export meter point. |
|
|
|
Details of an ongoing enrolment process. |
|
The distribution network the grid supply point falls under. |
|
|
|
|
|
|
|
|
|
|
|
Whether the meter point is due to renew their tariff. |
|
The ID of the meter point in Junifer. Deprecated The 'juniferMeterPointId' field is deprecated. |
|
|
|
Line loss factor class |
|
|
|
|
|
|
|
Meter timeswitch code |
|
|
|
|
|
The profile class of the electricity meter point. |
|
|
|
|
|
|
|
|
|
Smart Metering System Operator |
|
|
|
Standard settlement configuration |
|
|
|
|
|
|
|
|
|
A list of unbilled electricity readings for the meterpoint. |
Example
{
"id": "abc123",
"supplyEndDate": "2020-01-01",
"mpan": "abc123",
"ssc": "abc123",
"energisationStatus": "abc123",
"dccServiceFlag": "abc123",
"statusUpdatedAt": "2020-01-01T00:00:00.000Z",
"oldSupplierId": "abc123",
"newSupplierId": "abc123",
"smartStartDate": "2020-01-01",
"requiresEnrolment": true,
"targetSsd": "2020-01-01",
"requiresWithdrawal": true,
"hasOpenOpeningReadDispute": true,
"hasOpenClosingReadDispute": true,
"profileClass": 1,
"llf": "abc123",
"mtc": 1,
"measurementClass": "abc123",
"lastValidatedReadingDate": "2020-01-01",
"smsOperator": "abc123",
"smsOperatorEffectiveFrom": "2020-01-01",
"ihdStatus": "abc123",
"ihdEffectiveFrom": "2020-01-01",
"dccEffectiveFrom": "2020-01-01",
"meters": [ElectricityMeterType],
"status": "abc123",
"enrolment": EnrolmentType,
"gspGroupId": "abc123",
"agentContracts": [ElectricityAgentContractType],
"juniferMeterPointId": 1,
"agreements": [ElectricityAgreementType],
"smartTariffOnboarding": SmartTariffOnboardingType,
"unbilledReadings": [ElectricityMeterReadingType],
"currentSupplierMpid": "abc123",
"direction": "IMPORT",
"isDueTariffRenewal": true,
"canRenewTariff": true
}ElectricityMeterReadingConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ElectricityMeterReadingConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ElectricityMeterReadingConnectionTypeEdge
A Relay edge containing a ElectricityMeterReadingConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ElectricityMeterReadingType,
"cursor": "abc123"
}ElectricityMeterReadingType
A electricity meter reading. A reading can in fact contain multiple values for each register (for example for ECO7). They are collected under a common read_at datetime and have a common fuel type.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
What 'kind' of reading this is based on how it was taken. |
|
|
|
Example
{
"id": "abc123",
"readAt": "2020-01-01T00:00:00.000Z",
"readingSource": "abc123",
"registers": [RegisterReading],
"source": "abc123",
"readingType": "abc123"
}ElectricityMeterRegisterType
Electricity registers measure consumption.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"identifier": "abc123",
"digits": 1,
"decimalPlaces": 1,
"name": "abc123",
"expectedReadingRanges": [1],
"timePatternRegime": "abc123",
"unitRateType": "abc123",
"eac": "1.0",
"multiplier": 1.0
}ElectricityMeterType
An electricity meter is a collection of registers which store readings. Eco7 meters are an example of a meter with multiple registers (for day and night).
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Energy consumption recorded by the meter. |
|
The units of consumption for a smart meter. |
|
|
|
|
|
|
|
The type of fuel this meter uses. |
|
Returns if the meter has and allows half hourly readings. |
|
|
|
|
|
|
|
|
|
Returns if the meter is ready for top up. |
|
Returns if the meter is an RTS meter. |
|
Returns if the meter is a traditional prepay meter. |
|
|
|
|
|
|
|
|
|
|
|
This lets us get around the fact that we already use the field id as a primary key. We will migrate the id field over to be this id eventually. |
|
|
|
|
|
|
|
Whether this meter requires a final change of tenancy (COT) reading. |
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"serialNumber": "abc123",
"requiresAccess": true,
"isDigital": true,
"installationDate": "2020-01-01",
"lastInspectionDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z",
"activeFrom": "2020-01-01",
"activeTo": "2020-01-01",
"meterPoint": ElectricityMeterPointType,
"location": "abc123",
"currentRating": 1,
"makeAndType": "abc123",
"meterType": "CHECK",
"certificationDate": "2020-01-01",
"certifiedUntil": "2020-01-01",
"retrievalMethod": "abc123",
"importMeter": ElectricityMeterType,
"exportMeters": ElectricityMeterTypeConnection,
"prepayLedgers": PrepayLedgersType,
"smartImportElectricityMeter": SmartMeterDeviceType,
"smartExportElectricityMeter": SmartMeterDeviceType,
"consumptionUnits": "abc123",
"requiresCotFinalReading": true,
"fuelType": "abc123",
"consumption": ConsumptionConnection,
"nodeId": "abc123",
"readings": ElectricityMeterReadingConnectionTypeConnection,
"registers": [ElectricityMeterRegisterType],
"hasAndAllowsHhReadings": true,
"smartDevices": [SmartMeterDeviceType],
"isTradPrepay": true,
"isReadyForTopup": true,
"isRts": true
}Fields
| Name | Description |
|---|---|
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
Example
{
"pageInfo": PageInfo,
"edges": ElectricityMeterTypeEdge
}ElectricityMeterTypeEdge
A Relay edge containing a ElectricityMeterType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ElectricityMeterType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Estimated cost in pence of the product over a year based on the quoted usage. |
|
Electricity tariff information label (TIL) provides standardised information between suppliers about a tariff. The type of ElectricityProductTariffInformationLabel depends on the rateType of the ElectricitySupplyPoint. |
|
The ID of the quoted product. |
|
|
|
Estimated cost in pence of the product per month based on the quoted usage. |
|
Energy product quoted. |
Example
{
"id": 1,
"label": "abc123",
"product": EnergyProductType,
"annualAmount": 1,
"monthlyAmount": 1,
"electricityTariffInformationLabel": ElectricityProductTariffInformationLabel
}Fields
| Name | Description |
|---|---|
|
Current active agreement on this supply point. |
|
Annual consumption of the supply point. The type of ElectricityConsumption depends on the rateType. |
|
CO2 saving based on annual consumption for a given supplier. |
|
The Mpan of the suply point. |
|
A list of quoted products and the corresponding tariff information. |
|
Rate type. |
|
Trees saved given the CO2 saving. |
Example
{
"mpan": "abc123",
"agreement": ElectricityAgreementType,
"annualConsumption": ElectricityConsumption,
"quotedProducts": ElectricityQuotedProduct,
"rateType": "STANDARD",
"co2SavingInKgFromConsumption": 1,
"treesSavedFromConsumption": 1
}Fields
| Name | Description |
|---|---|
|
The formatted supply address including postcode. The possible errors that can be raised are:
|
|
The grid supply point. |
|
The valid Saving Sessions MPAN. |
Example
{
"address": "abc123",
"mpan": "abc123",
"gspGroupId": "abc123"
}EmailAttachmentType
Represents a file to attach to a email message.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Temporary URL at which the attachment is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). |
Example
{
"id": "abc123",
"filename": "abc123",
"temporaryUrl": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The ID of the object |
|
Email message of the email event. Returns null for message's sent/received by other user's on the account. |
|
Example
{
"id": "abc123",
"eventType": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z",
"message": EmailType
}EmailType
Represents an email communication
Fields
| Name | Description |
|---|---|
|
Attachments of the email message. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Email recipient. |
|
Email sender. |
|
|
|
Subject line of the email message. |
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"channel": "EMAIL",
"toAddress": "abc123",
"fromEmail": "abc123",
"toNumber": "abc123",
"fromNumber": "abc123",
"templateCode": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"sentAt": "2020-01-01T00:00:00.000Z",
"attachments": [EmailAttachmentType],
"subject": "abc123",
"textBody": "abc123",
"htmlBody": "abc123",
"sender": "abc123",
"recipient": "abc123"
}Fields
| Name | Description |
|---|---|
|
The email address to be checked. |
|
The status of verification for associated email. |
Example
{
"email": "abc123",
"status": "NOT_SENT"
}Fields
| Name | Description |
|---|---|
|
The identifier of the 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. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The identifier of the register associated to this reading. |
Example
{
"readingDirection": "CONSUMPTION",
"registerId": "abc123",
"readingQuality": "ACTUAL",
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "abc123",
"deviceId": "abc123"
}EmbeddedNetworkType
Represents an embedded network that holds multiple embedded properties.
Fields
| Name | Description |
|---|---|
|
Get details about properties in an embedded network. |
|
|
|
A unique name/code for the network |
Example
{
"id": "abc123",
"name": "abc123",
"embeddedProperties": [EmbeddedPropertyType]
}EmbeddedPropertyType
Represents an embedded property in an embedded network.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
The id of the physical property related to this embedded property type. |
Example
{
"id": "abc123",
"embeddedNetwork": EmbeddedNetworkType,
"propertyId": "abc123"
}EndContributionAgreement
The possible errors that can be raised are:
- KT-CT-9603: Unable to find contribution agreement.
- KT-CT-4123: Unauthorized.
- KT-CT-9604: Unable to end contribution agreement.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created contribution agreement. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"contributionAgreement": ContributionAgreementType
}Energy
Describes the energy (not power) consumed (e.g. as electricity) or returned (e.g. as heat) by a system over a given span of time.
Differs from Power in that it describes the total amount of energy transferred during a
given time frame (not a single point in time).
Fields
| Name | Description |
|---|---|
|
The units in which the energy is being measured. |
|
The amount of energy (not power) transmitted. |
Example
{
"value": "1.0",
"unit": "KILOWATT_HOUR"
}Fields
| Name | Description |
|---|---|
|
Do we have the calculations needed for estimating heatpump for this account? |
|
Do we have the calculations needed for estimating solar panels for this account? |
|
The current bill of the account in pounds. |
|
The assumed electricity rate for an electric vehicle. |
|
The energy IQ score. |
|
Does the calculation for the account include an electric vehicle? |
|
Does the calculation for the account include a heatpump? |
|
Does the calculation for the account include solar panels? |
|
Is this estimation for the account what they actually have (heatpump, ev, solar). |
|
The new estimated bill for the account in pounds. |
Example
{
"enqScore": 1,
"currentBill": 1.0,
"newBill": 1.0,
"hasEv": true,
"hasSolar": true,
"hasHeatpump": true,
"elecCarRate": 1.0,
"isCurrentRecord": true,
"canAddSolar": true,
"canAddHeatpump": true
}EnergyMixDataType
Energy mix data can include the latest carbon intensity index in a region.
Fields
| Name | Description |
|---|---|
|
Current carbon intensity index. |
Example
{
"carbonIntensityIndex": "abc123"
}EnergyProductConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": EnergyProductConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}EnergyProductConnectionTypeEdge
A Relay edge containing a EnergyProductConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": EnergyProductType,
"cursor": "abc123"
}EnergyProductType
An EnergyProduct models a group of tariffs for both electricity and gas.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
This will be shown to customers during sign-up |
|
Whether the product is an import or export product. |
|
This name will be shown to customers during sign-up |
|
The exit fee applied per fuel if the agreement is ended early. Total value is determined by exit fee type, i.e. this value is either a flat cost or cost per year/month remaining on the agreement. |
|
Determines how the exit fee is calculated. |
|
|
|
|
|
Does the product have EPG applied on the unit rates. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Whether to hide this product from the direct registration journey |
|
|
|
|
|
|
|
|
|
These are internal notes to explain why this product exists |
|
Tags associated with the product. |
|
A list of tariffs per product for a given postcode. |
|
Duration of agreements using this product in months |
Example
{
"id": "abc123",
"fullName": "abc123",
"displayName": "abc123",
"description": "abc123",
"availableFrom": "2020-01-01T00:00:00.000Z",
"availableTo": "2020-01-01T00:00:00.000Z",
"isHidden": true,
"code": "abc123",
"direction": "IMPORT",
"notes": "abc123",
"isVariable": true,
"isGreen": true,
"isBusiness": true,
"isChargedHalfHourly": true,
"isPrepay": true,
"isDefault": true,
"isOccupier": true,
"term": 1,
"tariffs": EnergyTariffConnectionTypeConnection,
"isAvailable": true,
"isUnavailable": true,
"isFixed": true,
"isDomestic": true,
"includesEpgReduction": true,
"exitFees": 1,
"exitFeesType": "abc123",
"tags": ["abc123"]
}EnergyTariffConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": EnergyTariffConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}EnergyTariffConnectionTypeEdge
A Relay edge containing a EnergyTariffConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": EnergyTariffType,
"cursor": "abc123"
}Example
{
"linkState": "abc123",
"linkUrl": "abc123"
}EnqueueInboundCall
The possible errors that can be raised are:
- KT-CT-11802: Call not found.
- KT-CT-11803: Unable to enqueue the call.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The call that was enqueued. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"call": InboundCallType
}EnrollAccountInLoyaltyProgram
Enroll an account into the loyalty program.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-9213: ineligible loyalty points enrollment.
- KT-CT-9210: Unhandled Loyalty Points exception.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Outcome of the loyalty points campaign enrollment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"outcome": EnrollAccountInLoyaltyProgramOutcome
}Fields
| Name | Description |
|---|---|
|
Whether or not this account has been enrolled in the loyalty points campaign. |
Example
{
"hasEnrolled": true
}EnrollFanClubAccount
Try to enroll an account onto Fan Club.
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-CT-8104: Account already enrolled.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Result of the Fan Club enrollment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"enrollmentOutput": EnrollFanClubAccountOutputType
}Fields
| Name | Description |
|---|---|
|
Example
{
"status": "ELIGIBLE"
}EnrollmentCancelled
Enrollment was successfully cancelled.
Fields
| Name | Description |
|---|---|
|
The Enrollment process that was cancelled. |
|
The message to display to the user on Enrollment initiation. |
Example
{
"message": "abc123",
"enrollmentProcess": EnrollmentProcess
}EnrollmentInitiated
Enrollment was successfully initiated.
Fields
| Name | Description |
|---|---|
|
The Enrollment processes that were initiated. |
|
The message to display to the user on Enrollment initiation. |
Example
{
"enrollmentProcesses": EnrollmentProcess,
"message": "abc123"
}Fields
| Name | Description |
|---|---|
|
The outcome of the Octoplus enrolment. |
Example
{
"octoplus": OctoplusEnrolmentOutcome
}EnrolmentType
Details of an ongoing enrolment process.
Fields
| Name | Description |
|---|---|
|
The last company to supply this meter point. |
|
The enrolment status on a meter point. |
|
Target date for supply to start. |
|
Date the switch started. |
Example
{
"switchStartDate": "2020-01-01",
"supplyStartDate": "2020-01-01",
"previousSupplier": "abc123",
"status": "OBJECTION_RECEIVED"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"field": "abc123",
"messages": "abc123"
}Fields
| Name | Description |
|---|---|
|
Monetary currency of the statistic in ISO-4217 format. |
|
|
|
Net price per unit of the statistic if applicable. |
Example
{
"estimatedAmount": "1.0",
"costCurrency": "abc123",
"pricePerUnit": PricePerUnit
}ExpireEvPublicChargingToken
Expire an EV Public Charging token.
The possible errors that can be raised are:
- KT-CT-5817: External Account not found.
- KT-CT-5818: Invalid data.
- KT-CT-5819: Token not found.
- KT-CT-5820: Multiple tokens found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"token": Token
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"eventType": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z",
"category": "abc123",
"subcategory": "abc123",
"description": "abc123",
"content": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"eventType": "abc123",
"category": "abc123",
"subcategory": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z",
"description": "abc123",
"content": {"key": "value"}
}FanClubDiscountNotification
Send a push notification of there being a high likelihood of getting a Fan Club discount.
The possible errors that can be raised are:
- KT-CT-8106: No catchments provided.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Boolean indicating if Fan Club notifications were triggered. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}Fields
| Name | Description |
|---|---|
|
The instantaneous turbine output power in kW. |
|
The turbine's rotor speed in revolutions per minute. |
|
The total amount of electricity grid-wide from all sources in megawatts. |
|
A decimal in degrees representing the direction from which the wind is blowing. 360.0 degrees indicates the wind blows from the north. Read more here: https://confluence.ecmwf.int/pages/viewpage.action?pageId=133262398 |
|
The total amount of electricity grid-wide from wind in megawatts. |
|
The proportion of electricity on the grid coming from wind. Ranges from 0.0 - 1.0. |
|
The wind speed in m/s. |
Example
{
"power": "1.0",
"windSpeed": "1.0",
"windDirection": "1.0",
"rotorSpeed": "1.0",
"windPowerOnGrid": "1.0",
"totalPowerOnGrid": "1.0",
"windPowerProportion": "1.0"
}FanClubNonOctopusCustomerComms
The possible errors that can be raised are:
- KT-CT-8107: Invalid eligibility status.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Flag for whether Fan Club comms for non-Octopus customer were sent. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}Fields
| Name | Description |
|---|---|
|
The list of account numbers for the source and account user. |
|
The list of catchments that this discount source applies to. |
|
The current or 'live' status of discounts for this source. |
|
The source for the discount, e.g. 'Fan 1' for a wind turbine in UK, or an ERCOT Load Zone for US. |
|
The forecasted discount probabilities for this source. |
|
The historic discounts for this source. |
|
The location of the discount source. |
|
The name of the discount source. |
|
The list of property IDs for the source and account user. |
|
The details of Fan Club thresholds for the discount source. |
|
The wind farm that the discount source is part of. |
Example
{
"discountSource": "abc123",
"name": "abc123",
"location": "abc123",
"windFarm": "abc123",
"accountNumbers": "abc123",
"propertyIds": 1,
"catchments": "abc123",
"thresholds": Threshold,
"current": DiscountData,
"historic": DiscountData,
"forecast": DiscountForecast
}FetchGeneratePaymentFingerprint
The possible errors that can be raised are:
- KT-CT-12101: Payment instruction not found.
- KT-CT-12102: Payment vendor not supported.
- KT-CT-12103: Missing payment metadata from vendor.
- KT-CT-12104: Unable to fetch or generate payment fingerprint.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Fetched or generated fingerprint from vendor. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Vendor name. |
Example
{
"possibleErrors": [PossibleErrorType],
"fingerprint": "abc123",
"vendor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": FieldSalesVisitConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}FieldSalesVisitConnectionTypeEdge
A Relay edge containing a FieldSalesVisitConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": FieldSalesVisitType,
"cursor": "abc123"
}FieldSalesVisitOutcomeType
The specific outcome of a field sales visit at an address.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"type": "SALE",
"category": "SUCCESS",
"reason": "abc123"
}FieldSalesVisitType
A field sales visit at an address.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Post town |
|
County |
|
Affiliate Link. |
|
|
|
Field Sales Outcomes. |
|
|
|
Example
{
"startedAt": "2020-01-01T00:00:00.000Z",
"stoppedAt": "2020-01-01T00:00:00.000Z",
"addressLine1": "abc123",
"addressLine2": "abc123",
"addressLine3": "abc123",
"addressLine4": "abc123",
"addressLine5": "abc123",
"outcome": "SWITCHED",
"affiliateLink": AffiliateLinkType,
"outcomes": [FieldSalesVisitOutcomeType]
}Fields
| Name | Description |
|---|---|
|
The name of the GraphQL field for which the rate is limited. |
|
Whether the viewer is currently blocked from making requests to this field due to exceeding the allowed request rate. |
|
Indicates the rate limit allowed for this field (e.g. 10/m). |
|
Time to live: The time remaining before the user is unblocked from making requests to this field. |
Example
{
"field": "abc123",
"rate": "abc123",
"ttl": 1,
"isBlocked": true
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": FieldSpecificRateLimitInformationConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}FieldSpecificRateLimitInformationConnectionTypeEdge
A Relay edge containing a FieldSpecificRateLimitInformationConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": FieldSpecificRateLimitInformation,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The ID type. Currently only 'meter_point' is supported. |
|
The ID to be checked. |
|
Returns True if the risk identifier is in the risk list. |
|
Returns the level of risk for the supplied object between |
Example
{
"identifierValue": "abc123",
"identifierType": "abc123",
"riskLevel": "1.0",
"isInRiskList": true
}Fields
| Name | Description |
|---|---|
|
EFR32 firmware version (Emergency Firmware Recovery). |
|
ESP32 firmware version (EFI System Partition). |
|
The EUI of the controller being queried. |
Example
{
"esp32": "abc123",
"efr32": "abc123",
"eui": "abc123"
}FitAcceptSchedule
FiT customers need to be able to accept their FiT schedules. There are a number of conditions that need to be met for a schedule: - It must have been sent - It must not have been accepted - It must not be in the future
The possible errors that can be raised are:
- KT-GB-6813: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The accepted schedule. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"fitSchedule": FitScheduleType
}Fields
| Name | Description |
|---|---|
|
The FiT installation associated with the provided FiT id. |
Example
{
"installation": InstallationType
}FitCreateMeterReadings
The possible errors that can be raised are:
- KT-GB-6812: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"readingsSubmitted": true
}Fields
| Name | Description |
|---|---|
|
ID of the meter. |
|
Any installation capacities linked to the meter. |
|
The maximum read volume expected for the current datetime, including any extra tolerance allowed. |
|
MPAN of the meter point linked to the meter. |
|
|
|
Serial number of the meter. |
|
The type of meter. |
Example
{
"serialNumber": "abc123",
"id": "abc123",
"type": "abc123",
"readings": FitReadingConnectionTypeConnection,
"installationCapacities": [InstallationCapacityType],
"maxExpectedRead": "1.0",
"mpan": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": FitReadingConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}FitReadingConnectionTypeEdge
A Relay edge containing a FitReadingConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": FitReadingType,
"cursor": "abc123"
}Example
{
"value": "1.0",
"readAt": "2020-01-01T00:00:00.000Z",
"isBiennial": true
}Fields
| Name | Description |
|---|---|
|
Datetime the schedule was accepted. |
|
Unique Identifier of the schedule. |
|
Datetime the schedule was sent. |
|
URLs for any schedule PDFs. URLs are temporary and will expire in approximately one hour. They are intended for redirection purposes only; they are not persistent in any form (eg. in emails or a web page body). |
Example
{
"scheduleId": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"sentAt": "2020-01-01T00:00:00.000Z",
"acceptedAt": "2020-01-01T00:00:00.000Z",
"temporaryDownloadUrls": ["abc123"]
}Fields
| Name | Description |
|---|---|
|
The unique id of the device preference schedule setting. |
|
The maximum value a preference can be set to (inclusive). |
|
The minimum value a preference can be set to (inclusive). |
|
The step size preference can be set to. |
|
The minimum time a preference can be set to (inclusive). |
|
The step amount (in minutes) a preference schedule time can be set. |
|
The maximum time a preference can be set to (inclusive). |
Example
{
"id": 1,
"timeFrom": "00:00:00.000Z",
"timeTo": "00:00:00.000Z",
"timeStep": 1,
"min": "1.0",
"max": "1.0",
"step": "1.0"
}Fields
| Name | Description |
|---|---|
|
The device type of the setting. |
|
The unique id of the device preference setting. |
|
The mode of the setting. |
|
Scheduled preference settings. |
|
The unit of the min and max values in the preferences setting. |
Example
{
"id": 1,
"deviceType": "abc123",
"mode": "CHARGE",
"unit": "CELSIUS",
"scheduleSettings": FlexDevicePreferenceScheduleSettingInterface
}Fields
| Name | Description |
|---|---|
|
The minimum and maximum temperatures which may be selected, dictated by the device. |
|
The flow temperature currently selected by the user. |
Example
{
"allowableRange": TemperatureRange,
"currentTemperature": Temperature
}Fields
| Name | Description |
|---|---|
|
The type of account. |
|
|
|
|
|
|
|
The payment method for the product. |
|
Example
{
"activeFrom": "2020-01-01T00:00:00.000Z",
"activeTo": "2020-01-01T00:00:00.000Z",
"accountType": "BUSINESS",
"paymentMethod": "DIRECT_DEBIT",
"renewalProducts": [RenewalProductType],
"createdAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The time at which forced reauthentication is effective. Kraken and refresh tokens issued before this time will be invalid. |
|
Reports whether the mutation applied successfully. Should always be 'true'. |
Example
{
"tokensInvalidated": true,
"effectiveAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Lower confidence interval bound for forecasted power (kW). |
|
The best guess for forecasted power (kW). |
|
Upper confidence interval bound for forecasted power (kW). |
|
Projected discount based on ensemble forecast data. |
|
Timestamp for the data-point. |
Example
{
"validTime": "2020-01-01T00:00:00.000Z",
"projectedDiscount": "1.0",
"powerMedian": "1.0",
"powerLowerBound": "1.0",
"powerUpperBound": "1.0"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"id": 1,
"content": {"key": "value"},
"errors": [SerializerFieldErrorsType]
}FractionSizeType
A fractional measurement.
Fields
| Name | Description |
|---|---|
|
The fractional value. |
|
Unique identifier of the object. |
|
The name of the object's type. |
Example
{
"id": "abc123",
"typename": "abc123",
"fraction": "1.0"
}Fields
| Name | Description |
|---|---|
|
Returns True if the meter point ID is in the list of suspicious meter point IDs. |
|
The meter point ID. |
Example
{
"meterPointId": "abc123",
"isInSuspiciousList": true
}FulfilmentType
Represents an amount of money that can be used to fulfil an obligation.
Fields
| Name | Description |
|---|---|
|
The amount of the fulfilment (in minor currency units), unsigned. |
|
The database ID of the fulfilment source, e.g. the database ID of the payment. |
|
The type of the fulfilment source, e.g. PAYMENT. |
Example
{
"sourceType": "UNKNOWN",
"sourceIdentifier": "abc123",
"amount": 1
}Fields
| Name | Description |
|---|---|
|
The time the data was reported. |
|
The latest reported mode of the heat pump. |
Example
{
"value": "HEATING",
"timestamp": "2020-01-01T00:00:00.000Z"
}FundingSourceAmountConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": FundingSourceAmountConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}FundingSourceAmountConnectionTypeEdge
A Relay edge containing a FundingSourceAmountConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": FundingSourceAmountType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Amount used from a funding source in minor currency. |
|
Reason why the funding source was used. |
Example
{
"reason": "abc123",
"amount": 1
}GasAgentContractType
An organization who manages a given meterpoint.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"contractType": "MAM",
"agentId": "abc123",
"contractStatus": "ACCEPTED",
"effectiveFrom": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
|
|
The datetime the agreement was entered. |
|
The datetime the agreement was terminated. |
|
Bespoke rates that apply to this agreement. |
|
Bespoke standing charges that apply to this agreement. |
|
The ID of the agreement. |
|
Whether the agreement is revoked. |
|
A collection of charges and associated consumption data. |
|
|
|
List of contracted standing charge uplifts applicable during this agreement's duration. This is only applicable to business accounts where we may pay commission to a third-party intermediary. |
|
|
|
List of contracted unit rate uplifts applicable during this agreement's duration. This is only applicable to business accounts where we may pay commission to a third-party intermediary. |
|
The start datetime of the agreement. |
|
The end datetime of the agreement. |
Example
{
"id": 1,
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"agreedFrom": "2020-01-01T00:00:00.000Z",
"agreedTo": "2020-01-01T00:00:00.000Z",
"account": AccountType,
"meterPoint": GasMeterPointType,
"tariff": GasTariffType,
"isRevoked": true,
"lineItems": LineItemConnection,
"unitRateUplifts": [GasContractUnitRateUplift],
"standingChargeUplifts": [GasContractStandingChargeUplift],
"bespokeRates": [GasBespokeRate],
"bespokeStandingCharges": [GasBespokeStandingCharge]
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"value": "1.0",
"paymentMethod": "DIRECT_DEBIT"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"value": "1.0",
"paymentMethod": "DIRECT_DEBIT"
}Example
{
"consumption": 1,
"isEstimate": true
}Fields
| Name | Description |
|---|---|
|
The estimated Annual Quantity measured in kWh. |
|
The date from which the AQ is calculated. |
|
The date the meterpoint switched to the current supplier. |
|
The current supplier for the meterpoint. |
Example
{
"aq": 1,
"supplierName": "abc123",
"supplierEffectiveFromDate": "2020-01-01",
"aqEffectiveFromDate": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
The amount to add to the standing charge when billing, in pence per day. |
|
When this contract is valid from. |
|
When this contract is valid until. |
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"standingChargeUplift": "1.0"
}Fields
| Name | Description |
|---|---|
|
The amount to add to the unit rate when billing, in pence/kWh. |
|
When this contract is valid from. |
|
When this contract is valid until. |
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"unitRateUplift": "1.0"
}GasFiltersOutput
Filter measurements by gas parameters.
Fields
| Name | Description |
|---|---|
|
The identifier of the device associated to this reading. |
|
The identifier of the market supply point associated to this reading. |
|
The frequency of the reading. |
|
The identifier of the register associated to this reading. |
Example
{
"registerId": "abc123",
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "abc123",
"deviceId": "abc123"
}GasMeterPointType
A gas meterpoint is a collection of meters. Meters are changed over time, so it is convenient to keep an invariant reference. We would not expect there to be multiple active meters at a time on a gas meterpoint.
Fields
| Name | Description |
|---|---|
|
A list of agents responsible for management of the meterpoint. |
|
A list of gas agreements belonging to an account that is linked to the viewer. Filters out expired agreements by default. |
|
Whether it is possible to renew the meter point's tariff. |
|
|
|
Rolling SOQ |
|
Rolling SOQ |
|
The current MPID for this meter point. |
|
|
|
Details of an ongoing enrolment process. |
|
|
|
|
|
|
|
AQ fixed for year |
|
SOQ fixed for year |
|
|
|
|
|
|
|
|
|
|
|
Whether the meter point is due to renew their tariff. |
|
Local distribution zone - Distribution charges are based upon this |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A list of unbilled gas readings for the meterpoint. |
|
Industry status code |
Example
{
"id": "abc123",
"supplyEndDate": "2020-01-01",
"mprn": "abc123",
"statusUpdatedAt": "2020-01-01T00:00:00.000Z",
"oldSupplierId": "abc123",
"newSupplierId": "abc123",
"smartStartDate": "2020-01-01",
"requiresEnrolment": true,
"targetSsd": "2020-01-01",
"requiresWithdrawal": true,
"hasOpenOpeningReadDispute": true,
"hasOpenClosingReadDispute": true,
"marketSectorCode": "D",
"marketCategory": "SSP",
"meterOwnershipType": "T",
"confirmationReference": 1,
"nominationType": "abc123",
"supplyClass": 1,
"nominationShipperReference": "abc123",
"xoserveStatus": "abc123",
"exitCapacityChargeRate": "1.0",
"ldzCapacityChargeRate": "1.0",
"ldzCommodityChargeRate": "1.0",
"ldzCustomerChargeRate": "1.0",
"ntsExitCommodityChargeRate": "1.0",
"mrfType": "abc123",
"meterReadBatchFrequency": "abc123",
"formulaYearSmpSoq": 1,
"formulaYearSmpAq": 1,
"currentDmSoq": 1,
"currentNdmSoq": 1,
"exitZone": "abc123",
"ldz": "abc123",
"supplyPointCategory": "abc123",
"endUserCategory": 1,
"eucIdentifier": "abc123",
"igtIdentifier": "abc123",
"igtCheckedAt": "2020-01-01T00:00:00.000Z",
"meters": [GasMeterType],
"status": "abc123",
"enrolment": EnrolmentType,
"agentContracts": [GasAgentContractType],
"agreements": [GasAgreementType],
"unbilledReadings": [GasMeterReadingType],
"currentSupplierMpid": "abc123",
"isDueTariffRenewal": true,
"canRenewTariff": true
}GasMeterReadingConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": GasMeterReadingConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}GasMeterReadingConnectionTypeEdge
A Relay edge containing a GasMeterReadingConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": GasMeterReadingType,
"cursor": "abc123"
}GasMeterReadingType
A gas meter reading. The reading value is under the register collection to be consistent with electricity readings. We expect a single register and reading value for gas.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
What 'kind' of reading this is based on how it was taken. |
|
|
|
Example
{
"id": "abc123",
"readAt": "2020-01-01T00:00:00.000Z",
"readingSource": "abc123",
"registers": [RegisterReading],
"source": "abc123",
"readingType": "abc123"
}GasMeterRegisterType
Gas registers measure consumption.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"identifier": "abc123",
"digits": 1,
"decimalPlaces": 1,
"name": "abc123",
"expectedReadingRanges": [1],
"unitRateType": "abc123"
}Fields
| Name | Description |
|---|---|
|
A unique three-character code used to identify the current supplier. |
|
A datetime indicating the date on which the Supplier became the supplier of the RMP. |
|
Daily Metered current annual offtake quantity (AQ) of a Supply Meter Point. Value in kWh. |
|
Unique Identifier for the Gas Transporter Organisation, can also be used to identify the geographical area. |
|
Unique reference code for the Local Distribution Zone (LDZ). |
|
A code that specifies if the site is used for domestic or industrial/commercial purposes. D = Domestic, I = Industrial and Commercial. |
|
The amount of gas that can be passed through the meter in a given time period. This is the manufacturer's maximum value. |
|
The coded value of the description of the Meter Mechanism, an identifier for the type of equipment fitted, e.g. credit or prepayment meter. |
|
The number of dials on the meter installed at the Supply Meter Point. |
|
The manufacturer's meter serial number as held on the physical meter currently installed on the supply point. |
|
The current annual offtake quantity (AQ) of a Supply Meter Point. Value in kWh. |
|
Meter Point Reference Number (MPRN). A unique identifier for the point at which a meter is, has been or will be connected to the Gas Network. |
|
Non-Daily Metered current annual offtake quantity (AQ) of a Supply Meter Point. Value in kWh. |
|
A datetime indicating the date on which a subsequent Supplier will become the supplier of the RMP. |
|
Specification ID of the smart meter. |
Example
{
"mprn": "abc123",
"currentSupplierId": "abc123",
"currentSupplierRegEffectiveDate": "abc123",
"pendingSupplierRegEffectiveDate": "abc123",
"dmq": "1.0",
"gasTransportId": "abc123",
"ldzId": "abc123",
"meterCapacity": "abc123",
"meterMechanismCode": "abc123",
"meterNumberOfDials": "abc123",
"meterSerialNumber": "abc123",
"mpaq": "1.0",
"marketSectorCode": "abc123",
"ndmq": "1.0",
"smartEquipmentTechnicalCode": "abc123"
}GasMeterType
A gas meter has a register which holds readings. We would expect this to be a one-to-one relationship between meter and register.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Energy consumption recorded by the meter. |
|
The units of consumption for a smart meter. |
|
|
|
|
|
|
|
The type of fuel this meter uses. |
|
Returns if the meter has and allows half hourly readings. |
|
|
|
|
|
|
|
|
|
|
|
Returns if the meter is ready for top up. |
|
Returns if the meter is a traditional prepay meter. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This lets us get around the fact that we already use the field id as a primary key. We will migrate the id field over to be this id eventually. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Whether this meter requires a final change of tenancy (COT) reading. |
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"serialNumber": "abc123",
"requiresAccess": true,
"isDigital": true,
"installationDate": "2020-01-01",
"lastInspectionDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z",
"activeFrom": "2020-01-01",
"activeTo": "2020-01-01",
"meterPoint": GasMeterPointType,
"manufacturerCode": "abc123",
"modelName": "abc123",
"manufacturedYear": 1,
"meterType": "abc123",
"imperial": true,
"units": 1,
"location": "abc123",
"mechanism": "CR",
"correction": 1.0,
"locationDescription": "abc123",
"readingFactor": "1.0",
"instructions": "abc123",
"pulseValue": "1.0",
"linkCode": "abc123",
"collarFitted": "abc123",
"bypassFitted": "abc123",
"measuringCapacity": "1.0",
"status": "LI",
"operationalStatusDate": "2020-01-01",
"owner": "abc123",
"currentMeterAssetManager": "abc123",
"prepayLedgers": PrepayLedgersType,
"smartGasMeter": SmartMeterDeviceType,
"consumptionUnits": "abc123",
"requiresCotFinalReading": true,
"fuelType": "abc123",
"consumption": ConsumptionConnection,
"nodeId": "abc123",
"readings": GasMeterReadingConnectionTypeConnection,
"registers": [GasMeterRegisterType],
"hasAndAllowsHhReadings": true,
"smartDevices": [SmartMeterDeviceType],
"isTradPrepay": true,
"isReadyForTopup": true
}Fields
| Name | Description |
|---|---|
|
Estimated cost in pence of the product over a year based on the quoted usage. |
|
Gas tariff information label (TIL) provides standardised information between suppliers about a tariff. |
|
The ID of the quoted product. |
|
|
|
Estimated cost in pence of the product per month based on the quoted usage. |
|
Energy product quoted. |
Example
{
"id": 1,
"label": "abc123",
"product": EnergyProductType,
"annualAmount": 1,
"monthlyAmount": 1,
"gasTariffInformationLabel": ProductTariffInformationLabelStandard
}Fields
| Name | Description |
|---|---|
|
Current active agreement on this supply point. |
|
Annual consumption of the supply point. |
|
The Mprn of the suply point. |
|
A list of quoted products and the corresponding tariff information. |
|
Gas has only STANDARD rate type. |
Example
{
"mprn": "abc123",
"agreement": GasAgreementType,
"annualConsumption": GasConsumption,
"quotedProducts": GasQuotedProduct,
"rateType": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Whether the tariff is for exporting energy. |
|
|
|
|
|
|
|
|
|
Describes a particular tariff by combining the product code, number of rates, available from date and GSP code. |
|
|
|
Is EPG applied to the unit rate. |
Example
{
"id": "abc123",
"displayName": "abc123",
"fullName": "abc123",
"description": "abc123",
"productCode": "abc123",
"standingCharge": 1.0,
"preVatStandingCharge": 1.0,
"tariffCode": "abc123",
"isExport": true,
"unitRate": 1.0,
"unitRateEpgApplied": true,
"preVatUnitRate": 1.0
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
The html of the terms and conditions document rendered as a JSON string. |
|
The markdown text of the terms and conditions. |
|
|
|
|
|
Example
{
"name": "abc123",
"pdfUrl": "abc123",
"brandCode": "abc123",
"markdown": "abc123",
"html": "abc123",
"version": "abc123",
"effectiveFrom": "2020-01-01T00:00:00.000Z"
}GenerateAffiliatesAudioRecordingPreSignedUrl
Generate a pre-signed URL for uploading a audio file for use with affiliates.
Fields
| Name | Description |
|---|---|
|
Input fields required to generate a presigned S3 post for affiliates audio recording. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"affiliatesAudioRecordingPreSignedUrl": AffiliateAudioRecordingPresignedPostType
}GenerateInkPresignedUrl
The possible errors that can be raised are:
- KT-CT-7620: Channel not supported.
- KT-CT-7618: Unable to process message.
- KT-CT-7624: Error when generating the presigned URL.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Presigned post fields required to upload the file. |
|
The key for the item. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
A presigned URL for the user to upload to the quarantine bucket. |
Example
{
"possibleErrors": [PossibleErrorType],
"uploadUrl": "abc123",
"key": "abc123",
"fields": {"key": "value"}
}GeneratePaymentAllocationNumber
Generate a PAN (Payment Allocation Number) for a smart meter. This can be used to add credit to the meter in a shop, if the meter is in prepayment mode.
The possible errors that can be raised are:
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The Payment Allocation Number routes payments made via a PSP (Payment Service Provider) to this device. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"pan": "abc123"
}GeneratePreSignedToken
Mutation to generate a pre-signed token.
The pre-signed, expiring and opaque tokens will be swapped for a limited scope JWT (Kraken Token).
The possible errors that can be raised are:
- KT-CT-1128: Unauthorized.
- KT-CT-1120: The Kraken Token has expired.
- KT-CT-1131: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
|
|
|
|
Example
{
"possibleErrors": [PossibleErrorType],
"token": "abc123",
"tokenExpiryDatetime": "2020-01-01T00:00:00.000Z",
"scope": "SUBMIT_METER_READINGS"
}GenericBackendScreen
A generic backend screen that can be used to define any type of screen.
Fields
| Name | Description |
|---|---|
|
The name of the screen. |
|
The refresh / polling frequency in milliseconds. |
|
Serialized JSON representation of the screen. |
Example
{
"name": "abc123",
"refreshFrequency": 1,
"screenData": "abc123"
}GetEmbeddedSecretForNewPaymentInstruction
Get the client secret needed to create a new payment instruction using an embedded form.
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"secretKey": "abc123"
}GetEmbeddedSecretForNewPaymentInstructionWithoutAccount
Get the client secret needed to create a new stored payment instruction using an embedded form.
This mutation is specifically for saving payment methods for future use, without immediately creating a payment instruction tied to a specific ledger or account.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The client secret needed to create a new stored payment instruction. |
Example
{
"possibleErrors": [PossibleErrorType],
"secretKey": "abc123"
}GetHostedUrlForNewPaymentInstruction
Get external URL where the user can set up a payment instruction.
The possible errors that can be raised are:
- KT-CT-1128: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
URL at which payment instruction can be set up. |
Example
{
"possibleErrors": [PossibleErrorType],
"url": "abc123"
}GetOrCreateShellAccountForOpportunity
The possible errors that can be raised are:
- KT-CT-8903: Unable to update opportunity.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The account number of the newly created or existing account. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountNumber": "abc123"
}Fields
| Name | Description |
|---|---|
|
All available sets of constantine. |
|
Total amount of prize entries. |
Example
{
"sets": [SnapSetType],
"totalPrizeEntries": 1
}Fields
| Name | Description |
|---|---|
|
Currency. |
|
Gross amount. |
|
Net amount. |
|
Grant type. |
Example
{
"type": "abc123",
"netAmount": 1.0,
"grossAmount": 1.0,
"currency": "abc123"
}Fields
| Name | Description |
|---|---|
|
Product available from. |
|
Product available to. |
|
Product code. |
|
Currency. |
|
Product customer name. |
|
Product description. |
|
Gross price per unit. |
|
Product ID. |
|
Product internal name. |
|
Market of the product. |
|
Product notes. |
|
Price per unit. |
|
Type of the product. |
Example
{
"id": 1,
"marketName": "abc123",
"productType": GoodsProductType,
"code": "abc123",
"internalName": "abc123",
"customerName": "abc123",
"notes": "abc123",
"description": "abc123",
"availableFrom": "2020-01-01",
"availableTo": "2020-01-01",
"pricePerUnit": 1.0,
"grossPricePerUnit": 1.0,
"currency": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": GoodsProductConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}GoodsProductConnectionTypeEdge
A Relay edge containing a GoodsProductConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": GoodsProduct,
"cursor": "abc123"
}Example
{
"code": "abc123",
"internalName": "abc123"
}Fields
| Name | Description |
|---|---|
|
Client parameters of the purchase. |
|
Purchase code. |
|
Grants that apply in this purchase. |
|
Sale items in this purchase. |
|
Ledger ID associated to the purchase. Deprecated The 'ledgerId' field is deprecated. |
|
The ledger number associated to the purchase. |
|
Market name of the purchase. |
|
Market parameters of the purchase. |
Example
{
"code": "abc123",
"ledgerId": "abc123",
"ledgerNumber": "abc123",
"goodsSaleItems": [GoodsSaleItem],
"goodsGrants": [GoodsGrant],
"marketName": "abc123",
"marketParams": {"key": "value"},
"clientParams": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
Code of the quote. |
|
Products of this quote. |
|
Indicates whether or not the quote is expired. |
|
ID of the quote. |
|
Date and time when the quote was created. |
|
Total net amount of the quote in cents. |
Example
{
"id": "abc123",
"code": "abc123",
"totalNetAmount": 1,
"quotedAt": "2020-01-01T00:00:00.000Z",
"goodsQuotedProducts": [GoodsQuotedProduct],
"hasQuoteExpired": true
}Fields
| Name | Description |
|---|---|
|
The ID of the quote share. |
Example
{
"id": "abc123"
}Fields
| Name | Description |
|---|---|
|
Currency. |
|
Net amount. |
|
Number of units. |
|
Price per unit. |
|
Product code. |
Example
{
"product": "abc123",
"numberOfUnits": 1,
"pricePerUnit": 1,
"netAmount": 1,
"currency": "abc123"
}Fields
| Name | Description |
|---|---|
|
Currency. |
|
Gross amount. |
|
Net amount. |
|
Number of units. |
|
Price per unit. |
|
Product code. |
Example
{
"product": "abc123",
"numberOfUnits": 1,
"pricePerUnit": 1.0,
"netAmount": 1.0,
"grossAmount": 1.0,
"currency": "abc123"
}Example
{
"savedTrees": 1,
"savedCo2InKgs": 1
}GreennessForecastPeriod
A greenness forecast entry for a single period of time.
Fields
| Name | Description |
|---|---|
|
The greenness index LOW/MEDIUM/HIGH (higher is greener) to map to a localised value. |
|
The greenness score 0-100 (higher is greener). |
|
Indicates that this is one of the best periods in the forecast (there may be more than one). This may not consider the entire forecast and can be ignored or calculated client-side from the score. |
|
The start of the forecast period (inclusive). |
|
The end of the forecast period (exclusive). |
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"greennessScore": 1,
"greennessIndex": "LOW",
"highlightFlag": true
}Fields
| Name | Description |
|---|---|
|
The current power being imported from or exported to the grid in kW. A negative value indicates power is being imported from the grid; a positive value indicates power is being exported to the grid. |
Example
{
"powerInKw": "1.0"
}GuaranteeOfOriginConfigurationType
Configuration for Guarantee of Origin term, defining percentage of energy from renewable sources.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The percentage of the guarantee of origin. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true,
"guaranteeOfOriginPercentage": "ZERO"
}Fields
| Name | Description |
|---|---|
|
Information on how agile unit rates have been calculated. The possible errors that can be raised are:
|
|
|
|
|
|
|
|
|
|
Whether the tariff is for exporting energy. |
|
|
|
|
|
|
|
Describes a particular tariff by combining the product code, number of rates, available from date and GSP code. |
|
Example
{
"id": "abc123",
"displayName": "abc123",
"fullName": "abc123",
"description": "abc123",
"productCode": "abc123",
"standingCharge": 1.0,
"preVatStandingCharge": 1.0,
"tariffCode": "abc123",
"isExport": true,
"unitRates": [UnitRate],
"agileCalculationInfo": AgileCalculationInfo
}HardshipAgreementType
Represents a Hardship Agreement for a particular Account.
Fields
| Name | Description |
|---|---|
|
These are internal notes detailing the hardship. |
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"hardshipType": "DEATH_IN_FAMILY",
"hardshipDetails": "abc123",
"hardshipEntryReason": "SELF_IDENTIFIED",
"paymentPlanDetails": "abc123",
"startDate": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
Any fault codes present on the device. |
|
The hardware version. |
|
Whether the system has a hot water cylinder (tank) which is compatible with heat pumps. |
|
The flow temperature set for heating. |
|
The last time the heat pump metrics were reset to zero. |
|
Whether the system has a manifold set up. |
|
The maximum temperature which the hot water can be set to. |
|
The minimum temperature which the hot water can be set to. |
|
The heat pump model (eg. COSY). |
|
The serial number of the heat pump. |
|
The current weather compensation settings. |
Example
{
"serialNumber": "abc123",
"model": "abc123",
"hardwareVersion": "abc123",
"faultCodes": ["abc123"],
"weatherCompensation": WeatherCompensationConfiguration,
"heatingFlowTemperature": FlowTemperatureConfiguration,
"manifoldEnabled": true,
"hasHeatPumpCompatibleCylinder": true,
"maxWaterSetpoint": 1.0,
"minWaterSetpoint": 1.0,
"latestCounterReset": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Always HEAT_PUMPS. Deprecated The 'deviceType' field is deprecated. |
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
|
The third party that provides control of this heat pump. |
Example
{
"krakenflexDeviceId": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"params": HeatPumpParamsType
}Fields
| Name | Description |
|---|---|
|
Account associated to quote. |
|
Property details stored in hubspot. |
|
Quote code. |
|
Contact details stored in hubspot. |
|
ID of the quote. |
|
Quoted product details. |
Example
{
"accountNumber": "abc123",
"code": "abc123",
"quoteId": 1,
"quotedProduct": GoodsQuotedProduct,
"contactDetails": ContactDetails,
"addressDetails": AddressDetails
}Fields
| Name | Description |
|---|---|
|
The end datetime of the node. |
|
The field to show energy input. |
|
The field to show energy output. |
|
The field to show outdoor temperature. |
|
The start datetime of the node. |
Example
{
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"energyInput": Energy,
"energyOutput": Energy,
"outdoorTemperature": Temperature
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Whether the heat pump is currently connected to the provider. |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"isConnected": true,
"climateControlStatus": ClimateControlDetailsType,
"waterTemperatureStatus": WaterTemperatureDetailsType
}Fields
| Name | Description |
|---|---|
|
The coefficient of performance (COP) of the heat pump. |
|
The field to show energy input. |
|
The field to show energy output. |
Example
{
"heatPumpId": "abc123",
"model": "abc123",
"powerInKw": "1.0",
"isDeprecated": true
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "abc123",
"models": [HeatPumpVariantModelsType]
}Fields
| Name | Description |
|---|---|
|
Whether a statement is currently held. |
|
Reason for statement being held. |
Example
{
"isHeld": true,
"reason": "abc123"
}ImageType
A media element containing an image.
Fields
| Name | Description |
|---|---|
|
Whether the element is hidden from view. |
|
Accessible description of the element. |
|
The horizontal alignment of the media. |
|
Unique identifier of the object. |
|
The resource URL of the media. |
|
The name of the object's type. |
|
The measurement of the element. |
Example
{
"width": ItemSizeType,
"mediaUrl": "abc123",
"horizontalAlignment": "START",
"accessibilityHidden": true,
"accessibilityLabel": "abc123",
"id": "abc123",
"typename": "abc123"
}Fields
| Name | Description |
|---|---|
|
The average number of seconds passed before an inbound call is answered. This value represents the calls received in the last 30 minutes. |
|
The average number of seconds passed before an inbound call is answered. This value represents the calls received on the previous day. |
Example
{
"yesterday": 1,
"recent": 1
}Fields
| Name | Description |
|---|---|
|
If known, this is the account that a call is about. For inbound calls, we attempt to identify the account based on the phone number of the incoming call. For outbound calls, the account will be automatically set if the call was initiated from an account page. For all call types, the account can be updated, for example to correct a misidentification of an incoming call. |
|
The ID of the call. |
|
When an inbound call is received, we identify all entities linked to the phone number of the caller. |
|
Metadata related to the call, for example metrics or data passed via an interactive voice response (IVR). |
Example
{
"id": "abc123",
"account": AccountType,
"metadata": CallMetadataItemType,
"initialCallerIdentification": PhoneNumberIdentificationType
}Fields
| Name | Description |
|---|---|
|
The escalation start date for the product rate override configuration. |
|
The index code for the product rate override configuration. |
Example
{
"indexCode": "abc123",
"escalationStartAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The account number of the newly created account or the existing account to be re-used. |
|
Was a new account created. |
Example
{
"isNewAccount": true,
"accountNumber": "abc123"
}Fields
| Name | Description |
|---|---|
|
Was a new user created. |
|
The user number of the newly created user or the existing user to be re-used. |
Example
{
"isNewUser": true,
"userNumber": "abc123"
}InitiateHostedStandalonePayment
Initiate a standalone payment and return the url where the customer can complete it.
The possible errors that can be raised are:
- KT-CT-1128: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-3943: Invalid ledger.
- KT-CT-3957: No collection method provided.
- KT-CT-3958: Provide either ledger ID or ledger number.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The details required to refer to and complete a hosted payment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": InitiateHostedStandalonePaymentOutput
}InitiateHostedStandalonePaymentOutput
Tokens required to collect and retrieve a standalone payment.
Fields
| Name | Description |
|---|---|
|
The retrieval token for this standalone payment. |
|
The url for the customer to complete the payment. |
Example
{
"retrievalToken": "abc123",
"url": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The newly initiated live chat. If an open live chat already exists for the given account, that is returned instead. |
Example
{
"liveChat": InkLiveChat,
"clientMutationId": "abc123"
}InitiateProductSwitch
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4619: Quote with given code not found.
- KT-CT-4624: Unable to accept the given product code.
- KT-CT-4924: Unauthorized.
- KT-CT-4626: No product selected for the given quote code.
- KT-CT-4719: No supply point found for identifier provided.
- KT-CT-1509: Unable to create agreement.
- KT-CT-1507: Agreement product switch date is not within the acceptable range.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The selected product for a specific product switch. |
|
The date at which the product switch becomes effective. |
Example
{
"possibleErrors": [PossibleErrorType],
"productCode": "abc123",
"switchDate": "2020-01-01"
}InitiateStandalonePayment
Initiate a standalone payment and return the client secret required to complete it.
The possible errors that can be raised are:
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-4177: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-3943: Invalid ledger.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": InitiateStandalonePaymentOutput
}InitiateStandalonePaymentOutput
Tokens required to collect and retrieve a standalone payment.
Fields
| Name | Description |
|---|---|
|
The retrieval token for this standalone payment. |
|
The secret used to collect the payment. |
Example
{
"retrievalToken": "abc123",
"secretToken": "abc123"
}InitiateUnauthenticatedStandalonePayment
Initiate an unauthenticated standalone payment and return the client secret required to complete it.
Fields
| Name | Description |
|---|---|
|
The payment's retrieval and secret tokens. |
Example
{
"payment": InitiateUnauthenticatedStandalonePaymentOutput
}Fields
| Name | Description |
|---|---|
|
The retrieval token for this standalone payment. |
|
The secret used to collect the payment. |
Example
{
"retrievalToken": "abc123",
"secretToken": "abc123"
}Fields
| Name | Description |
|---|---|
|
The icon code point. |
|
The ID of the object |
|
The ink bucket name. |
Example
{
"id": "abc123",
"name": "abc123",
"icon": "abc123"
}Fields
| Name | Description |
|---|---|
|
All contacts for this conversation. |
|
|
The default contact for this conversation. |
Example
{
"default": InkContactChannelIdentity,
"all": InkContactChannelIdentity
}Fields
| Name | Description |
|---|---|
|
The channel of the contact. |
|
The name to display to the user. |
|
The handle. |
Example
{
"channel": "EMAIL",
"handle": "abc123",
"displayName": "abc123"
}Fields
| Name | Description |
|---|---|
|
The account users on the conversation. |
|
The buckets the conversation is currently in. |
|
The contact channel identities associated with this conversation. |
|
Conversation events. |
|
|
|
The status of the conversation. |
Example
{
"id": "abc123",
"status": "OPEN",
"contactChannelIdentities": InkContactChannelIdentities,
"accountUsers": [AccountUserType],
"events": InkConversationEventsConnection,
"buckets": [InkBucket]
}Fields
| Name | Description |
|---|---|
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
Example
{
"pageInfo": PageInfo,
"edges": InkConversationEventsEdge
}InkConversationEventsEdge
A Relay edge containing a InkConversationEvents and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": InkConversationEvent,
"cursor": "abc123"
}InkEmail
This type wraps around the Message type for emails.
Fields
| Name | Description |
|---|---|
|
Attachments on the message. |
|
CC recipients on the message. |
|
The contact channel identity. |
|
The delivery status of the message. |
|
The direction of the email. |
|
The content of the message. |
|
From email address. |
|
Is this an message an email. |
|
The time the message was sent/received. |
|
The email subject. |
|
All Tags associated with a message. |
|
The addresses that the message was sent to. |
Example
{
"direction": "INBOUND",
"toHandles": ["abc123"],
"fromHandle": "abc123",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2020-01-01T00:00:00.000Z",
"subject": "abc123",
"displayContent": "abc123",
"attachments": InkMessageAttachment,
"cc": "abc123",
"isChannelEmail": true,
"tags": InkTag
}InkGenericMessage
This message type is used for messages that belong to contact channels without a more granular message type.
Fields
| Name | Description |
|---|---|
|
The contact channel identity. |
|
The delivery status. |
|
The direction of the message. |
|
The content of the message. |
|
The identity the message was sent from. |
|
The ID of the object |
|
The time the message was sent/received at. |
|
The identity the message was sent to. |
Example
{
"id": "abc123",
"direction": "INBOUND",
"fromHandle": "abc123",
"toHandle": "abc123",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2020-01-01T00:00:00.000Z",
"displayContent": "abc123"
}InkLine
This type wraps around the Message type for LINE message.
Fields
| Name | Description |
|---|---|
|
Attachments on the LINE message. |
|
The contact channel identity. |
|
The delivery status of the message. |
|
The direction of the message. |
|
From LINE id. |
|
Is this a LINE message. |
|
The line message content. |
|
The time the message was sent/received. |
|
All Tags associated with a message. |
|
To LINE id. |
Example
{
"direction": "INBOUND",
"fromHandle": "abc123",
"toHandle": "abc123",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2020-01-01T00:00:00.000Z",
"lineMessage": LineMessage,
"isChannelLine": true,
"attachments": InkMessageAttachment,
"tags": InkTag
}InkLiveChat
Ink live chat
Fields
| Name | Description |
|---|---|
|
The relay ID of the live chat. |
Example
{
"relayId": "abc123"
}Fields
| Name | Description |
|---|---|
|
The url for fetching the attachment. |
|
The filename. |
|
The size in bytes. |
Example
{
"filename": "abc123",
"fetchUrl": "abc123",
"sizeInBytes": 1
}Fields
| Name | Description |
|---|---|
|
Message delivery status. |
Example
{
"status": "PENDING"
}InkNewMessage
This types is used for both the message-received and message-sent conversation events.
Fields
| Name | Description |
|---|---|
|
The message. |
|
The time the conversation event occurred. |
Example
{
"occurredAt": "2020-01-01T00:00:00.000Z",
"message": InkMessage
}Fields
| Name | Description |
|---|---|
|
The content of the ink note. |
|
The ID of the object |
|
The note is pinned, so that it's always visible in the conversation. |
|
The datetime at which the conversation note occurred. |
Example
{
"id": "abc123",
"content": "abc123",
"isPinned": true,
"occurredAt": "2020-01-01T00:00:00.000Z"
}InkPost
This type wraps around the Message type for Post.
Fields
| Name | Description |
|---|---|
|
The contact channel identity. |
|
The notes left when a message was uploaded. |
|
The from property id. |
|
Determine if the message is a post message. |
|
The content of the message. |
|
The to property id. |
Example
{
"fromHandle": "abc123",
"toHandle": "abc123",
"displayContent": "abc123",
"rawPlainTextContent": "abc123",
"isChannelPost": true,
"contactChannelIdentity": InkContactChannelIdentity
}InkSMS
This type wraps around the Message type for SMS.
Fields
| Name | Description |
|---|---|
|
The contact channel identity. |
|
The delivery status. |
|
The direction of the message. |
|
The content of the message. |
|
The phone number the message was sent from. |
|
Is this an SMS message. |
|
The time the message was sent/received at. |
|
All Tags associated with a message. |
|
The phone number the message was sent to. |
Example
{
"direction": "INBOUND",
"fromHandle": "abc123",
"toHandle": "abc123",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2020-01-01T00:00:00.000Z",
"displayContent": "abc123",
"isChannelSms": true,
"tags": InkTag
}Example
{
"id": "abc123",
"name": "abc123"
}InkTwilioWhatsApp
This type wraps around the Message type for a Twilio WhatsApp message.
Fields
| Name | Description |
|---|---|
|
Twilio WhatsApp message contact channel identity. |
|
Message delivery status. |
|
The direction of the message. |
|
From WhatsApp number. |
|
Date when the conversation event was created. |
|
All Tags associated with a message. |
|
To WhatsApp number. |
|
The vendor id. |
|
Whatsapp message content. |
Example
{
"direction": "INBOUND",
"fromHandle": "abc123",
"toHandle": "abc123",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2020-01-01T00:00:00.000Z",
"vendorId": "abc123",
"whatsappContent": WhatsAppTextMessage,
"tags": InkTag
}InkWhatsApp
This type wraps around the Message type for WhatsApp message.
Fields
| Name | Description |
|---|---|
|
Whatsapp message contact channel identity. |
|
Whatsapp message delivery status. |
|
The direction of the message. |
|
From WhatsApp phone number. |
|
Whether or not the message is a whatsapp message. |
|
Date when the conversation event was created. |
|
All Tags associated with a message. |
|
Whatsapp contact phone number. |
|
The vendor id. |
|
Whatsapp message content. |
Example
{
"direction": "INBOUND",
"fromHandle": "abc123",
"toHandle": "abc123",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2020-01-01T00:00:00.000Z",
"vendorId": "abc123",
"whatsappContent": WhatsAppTextMessage,
"isChannelWhatsapp": true,
"tags": InkTag
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"declaredNetCapacity": "1.0",
"extensionReference": "abc123",
"installedCapacity": "1.0"
}Fields
| Name | Description |
|---|---|
|
FIT ID of the installation. |
|
Date fit terms were agreed to. |
|
Meter inspection date. |
|
Details of any meters attached to the installation. |
|
Address of the property linked to the installation. |
Example
{
"fitId": "abc123",
"fitTermsAgreedAt": "2020-01-01T00:00:00.000Z",
"inspectionAt": "2020-01-01T00:00:00.000Z",
"meters": [FitMeterType],
"propertyAddress": PropertyAddressType
}IntervalCostOfUsageType
Usage and cost between two points in time.
Fields
| Name | Description |
|---|---|
|
Cost per time interval. |
|
Interval end datetime. |
|
Interval start datetime. |
|
Usage per time interval. |
Example
{
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"cost": 1,
"usageKwh": "1.0"
}Fields
| Name | Description |
|---|---|
|
Deprecated The 'accumulation' field is deprecated. |
|
The duration of the measurement. |
|
The end datetime of the measurement. |
|
This type will return more granular data about the measurement. |
|
The datetime the measurement was taken. |
|
The data source of the measurement. |
|
The start datetime of the measurement. |
|
The unit of the measurement. |
|
The value of the measurement. |
Example
{
"source": "abc123",
"metaData": MeasurementsMetadataOutput,
"value": "1.0",
"unit": "abc123",
"readAt": "2020-01-01T00:00:00.000Z",
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"durationInSeconds": 1,
"accumulation": "1.0"
}InvalidatePaymentInstruction
Invalidates a payment instruction.
The possible errors that can be raised are:
- KT-CT-3926: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"instruction": InvalidatePaymentInstructionOutput
}InvalidatePaymentInstructionOutput
Output for invalidating an arbitrary payment instruction.
Fields
| Name | Description |
|---|---|
|
Example
{
"id": 1
}InvalidatePreSignedToken
Invalidate a previously issued expiring/pre-signed token.
This mutation can be used to invalidate the token itself.
To invalidate tokens issued to a particular user, use InvalidatePreSignedTokensForUser mutation.
The possible errors that can be raised are:
- KT-CT-1129: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"token": PreSignedToken
}InvalidatePreSignedTokensForUser
Invalidate pre-signed tokens previously issued to a particular user.
This mutation can invalidate all pre-signed tokens issued to a customer, or only tokens of a given scope.
The possible errors that can be raised are:
- KT-CT-1129: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"tokens": [PreSignedToken]
}InvalidateRefreshToken
Invalidate a previously issued refresh token.
This mutation can be used to invalidate the token itself. To invalidate tokens issued to a particular user, use InvalidateRefreshTokensForUser.
The possible errors that can be raised are:
- KT-CT-1130: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"token": RefreshToken
}InvalidateRefreshTokensForUser
Invalidate refresh tokens previously issued to a particular user.
This mutation will invalidate all refresh tokens issued to a customer.
The possible errors that can be raised are:
- KT-CT-1128: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"tokens": [RefreshToken]
}Fields
| Name | Description |
|---|---|
|
Whether the inverter is currently connected (online/offline). |
|
The current power flowing through the inverter in kW. A negative value indicates that power is being drawn in to charge the battery; a positive value indicates power is being exported to the property (and, possibly, the grid) from the battery and/or solar panels. |
Example
{
"connectionStatus": "ONLINE",
"powerInKw": "1.0"
}Fields
| Name | Description |
|---|---|
|
The make (manufacturer) of the device. |
Example
{
"make": "abc123"
}InvoiceBillingDocumentConnectionTypeConnection
An invoice is a bill that contains individual transactions (i.e. charges, credits, payments, and repayments). These may come from any period of time.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": InvoiceBillingDocumentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}InvoiceBillingDocumentConnectionTypeEdge
A Relay edge containing a InvoiceBillingDocumentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": InvoiceBillingDocumentType,
"cursor": "abc123"
}InvoiceBillingDocumentType
An invoice is a bill that contains individual transactions (i.e. charges, credits, payments, and repayments). These may come from any period of time.
Fields
| Name | Description |
|---|---|
|
Billing document that annuls this invoice. |
|
Position of the billing document in the delinquent debt tracking system. |
|
First time the invoice was issued. |
|
|
|
The invoiced amount of the billing document. |
|
The unique billing document's reference that can be used for identifying it externally. |
|
URL to the PDF of the Invoice. |
|
The total amounts for all charges on the invoice. |
|
The total amounts for all credits on the invoice. |
|
Transactions on the invoice |
Example
{
"id": 1,
"firstIssued": "2020-01-01T00:00:00.000Z",
"pdfUrl": "abc123",
"annulledBy": AnnulmentBillingDocumentType,
"number": "abc123",
"invoicedAmount": 1,
"totalCharges": InvoiceTotalType,
"totalCredits": InvoiceTotalType,
"transactions": BillTransactionConnectionTypeConnection,
"documentDebtPosition": BillingDocumentPositionType
}Fields
| Name | Description |
|---|---|
|
The gross total amount for the statement (in minor currency units). |
|
The net total amount for the statement (in minor currency units). |
|
The total amount of tax on the statement (in minor currency units). |
Example
{
"netTotal": 1,
"taxTotal": 1,
"grossTotal": 1
}Fields
| Name | Description |
|---|---|
|
|
|
The type of the bill. |
|
The date of the bill is covered from. |
|
This field returns the total gross amount of the bill in pence. |
|
The ID of the bill. |
|
The unique identifier of a bill. It will usually be present on the billing document itself. Note: a bill that hasn't been issued yet will not have an identifier; and not all issued bills will have an identifier assigned to them, in which case this will be null. |
|
Whether the billing document has been annulled. |
|
The date the bill was sent to the customer. |
|
Requesting this field generates a temporary URL at which bill is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). This field can raise an error with errorClass NOT_FOUND if the bill document has not been created/issued yet. This field is deprecated use 'attachments' field instead. Deprecated The 'temporaryUrl' field is deprecated. |
|
The date of the bill is covered to. |
|
The total amounts for all charges on the invoice. |
|
The total amounts for all credits on the invoice. |
|
The sum of all previous payments made that are included towards this invoice. |
|
Transactions on the given ledger. |
Example
{
"id": "abc123",
"billType": "STATEMENT",
"fromDate": "2020-01-01",
"toDate": "2020-01-01",
"temporaryUrl": "abc123",
"issuedDate": "2020-01-01",
"attachments": BillingAttachmentConnectionTypeConnection,
"identifier": "abc123",
"grossAmount": 1,
"isAnnulled": true,
"totalCharges": InvoiceTotalType,
"totalCredits": InvoiceTotalType,
"totalPayments": 1,
"transactions": BillTransactionConnectionTypeConnection
}JoinConsumerDevice
The possible errors that can be raised are:
- KT-GB-4053: Fuel type should not be specified for Alt HAN device.
- KT-GB-4031: Error sending the request to join the device to the CHF.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The reference of the join PPMID, IHD, CAD or Alt HAN request in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}JoinDeviceToNetwork
Send a request to the DCC to join a smart device to a HAN (Home Area Network).
The possible errors that can be raised are:
- KT-GB-4019: This device type is not currently supported.
- KT-GB-4020: Error sending the request to join the device to the Home Area Network.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}JoinOctoplusCampaign
Sign an account up to Octoplus.
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-GB-9310: Account ineligible for joining Octoplus.
- KT-GB-9311: Error joining campaign.
- KT-GB-9312: Account already signed up to Octoplus.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Outcome of the Octoplus enrollment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Returns mutation success. Deprecated, in favour of the outcome field. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true,
"outcome": EnrolmentOutcome
}JoinSavingSessionsCampaign
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-GB-5110: Campaign not found.
- KT-GB-5111: Meter point not found.
- KT-GB-5112: Error joining campaign.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": SavingSessionsAccountReturnType
}JoinSavingSessionsEvent
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-GB-5114: Saving Sessions event not found.
- KT-GB-5116: Account is not part of a Saving Sessions campaign.
- KT-GB-5117: Account ineligible to join Saving Sessions event.
- KT-GB-5115: Error joining event.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The event codes that the account has joined. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"joinedEventCodes": ["abc123"]
}JoinSupplierAcceptTermsAndConditions
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4501: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Indicator that the mutation has completed successfully. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": JoinSupplierProcessConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}JoinSupplierProcessConnectionTypeEdge
A Relay edge containing a JoinSupplierProcessConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": JoinSupplierProcessType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Affiliate link for the join supplier journey. |
|
The note associated with this join supplier process data. |
|
When the journey was requested. |
|
Sales channel. |
|
Sales subchannel. |
|
The supply point context data. |
Example
{
"requestedAt": "2020-01-01T00:00:00.000Z",
"salesChannel": "abc123",
"salesSubchannel": "abc123",
"affiliateLink": AffiliateLinkType,
"supplyPointContexts": SupplyPointContextDataInterface,
"note": "abc123"
}JoinSupplierProcessType
Represents a Join Supplier process.
Fields
| Name | Description |
|---|---|
|
The current process data associated with the Join Supplier process. |
|
The ID or the primary key of the lifecycle process. |
|
The unique identifier of the process. |
|
The status of the process. |
|
The supply points associated with the process. |
Example
{
"id": "abc123",
"status": "PENDING",
"supplyPoints": SupplyPointConnectionTypeConnection,
"number": "abc123",
"currentProcessData": JoinSupplierProcessDataType
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
The third party that provides control over this device. |
|
Maximum state of charge (SoC) limit telemetry. |
|
|
|
|
|
The reason for the most recent failed test dispatch (if any). |
|
|
|
|
|
Example
{
"krakenflexDeviceId": "abc123",
"provider": "BYD",
"vehicleMake": "abc123",
"vehicleModel": "abc123",
"vehicleBatterySizeInKwh": "1.0",
"chargePointMake": "abc123",
"chargePointModel": "abc123",
"chargePointPowerInKw": "1.0",
"status": "abc123",
"suspended": true,
"hasToken": true,
"createdAt": "2020-01-01T00:00:00.000Z",
"stateOfChargeLimit": StateOfChargeLimit,
"testDispatchFailureReason": "NONE"
}KrakenVersionType
Information about what version of Kraken is being executed by this service.
Fields
| Name | Description |
|---|---|
|
The git commit SHA that is being executed. |
|
The version number that is being executed. |
Example
{
"number": "abc123",
"SHA": "abc123"
}LatePaymentFeesType
Represents later payment fees to be applied in a contract.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The flat fee amount for late payment. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The percentage fee for late payment. |
|
The interval in days for the percentage fee (1=daily, 7=weekly, 30=monthly, 365=yearly). |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true,
"flatFeeAmount": "1.0",
"percentageFee": "1.0",
"percentageIntervalDays": "1.0"
}Fields
| Name | Description |
|---|---|
|
List of block list hits found. |
|
Indicates if the block list validation passed. |
Example
{
"valid": true,
"blockListHits": ["abc123"]
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": LeavePropertyProcessConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}LeavePropertyProcessConnectionTypeEdge
A Relay edge containing a LeavePropertyProcessConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": LeavePropertyProcessType,
"cursor": "abc123"
}LeavePropertyProcessType
Represents a Leave Property process.
Fields
| Name | Description |
|---|---|
|
The ID or the primary key of the lifecycle process. |
|
The status of the process. |
|
The supply points associated with the process. |
Example
{
"id": "abc123",
"status": "PENDING",
"supplyPoints": SupplyPointConnectionTypeConnection
}LeaveSupplierCancelled
Output of a LeaveSupplier journey cancellation.
Fields
| Name | Description |
|---|---|
|
The message to display to the user on cancellation. |
Example
{
"message": "abc123"
}LeaveSupplierInstigated
Termination was successfully initiated.
Fields
| Name | Description |
|---|---|
|
The ID of the newly created or existing leave supplier process. Deprecated The 'leaveSupplierProcessId' field is deprecated. |
|
The message to display to the user on termination initiation. |
|
The number of the newly created or existing leave supplier process. |
Example
{
"number": "abc123",
"leaveSupplierProcessId": "abc123",
"message": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": LeaveSupplierProcessConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}LeaveSupplierProcessConnectionTypeEdge
A Relay edge containing a LeaveSupplierProcessConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": LeaveSupplierProcessType,
"cursor": "abc123"
}LeaveSupplierProcessType
Represents a Leave Supplier process. Conceptually, it contains information related to supply points that are associated with a Leave Supplier journey.
Fields
| Name | Description |
|---|---|
|
The ID or the primary key of the lifecycle process. |
|
The unique identifier of the process. |
|
The status of the process. |
|
The supply points associated with the process. |
Example
{
"id": "abc123",
"status": "PENDING",
"number": "abc123",
"supplyPoints": SupplyPointConnectionTypeConnection
}LeaveSupplierUpdated
Leave supplier was successfully updated.
Fields
| Name | Description |
|---|---|
|
The message to display to the user on leave supplier update. |
Example
{
"message": "abc123"
}LedgerType
Ledgers provide the foundation of Kraken’s bookkeeping functionality. Similar to a bank account, they allow us to keep track of financial activity on a particular Kraken account.
Fields
| Name | Description |
|---|---|
|
Whether payments can be posted onto this ledger. |
|
Whether this ledger's balance contributes to the account's balance. |
|
The charged supply agreements of the ledger. |
|
The amount owed from the customer perspective. A positive value implies the customer owes the business, while a negative amount implies the customer is in credit. |
|
The current balance on the ledger in minor units of currency. |
|
Permissions data for credit transfers involving the given ledger. |
|
True if the current direct debit instruction has been invalidated by vendor. False otherwise. |
|
The debt ledger assigned to this ledger. |
|
Deprecated The 'ledgerId' field is deprecated. |
|
An invoice is a bill that contains individual transactions (i.e. charges, credits, payments, and repayments). These may come from any period of time. |
|
|
The ledger type code. |
|
The display name of the ledger. |
|
The canonical name of the ledger. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The customer's preferred payment methods. |
|
Refund requests for a given ledger. |
|
Repayment requests for a given ledger. |
|
A statement is a billing document that contains all entries on a ledger during a period of time. A customer can understand how their ledger's balance has changed by looking at each statement in series. |
|
Is it possible for this ledger to contain invoices. |
|
Is it possible for this ledger to contain statements. |
|
Transactions on the given ledger. |
Example
{
"id": "abc123",
"name": "abc123",
"number": "abc123",
"ledgerType": "abc123",
"balance": 1,
"amountOwedByCustomer": 1,
"affectsAccountBalance": true,
"statements": StatementBillingDocumentConnectionTypeConnection,
"invoices": InvoiceBillingDocumentConnectionTypeConnection,
"transactions": TransactionConnectionTypeConnection,
"repaymentRequests": RepaymentRequestConnectionTypeConnection,
"refundRequests": RefundRequestConnectionTypeConnection,
"acceptsPayments": true,
"paymentAdequacy": PaymentAdequacyDetailsType,
"creditTransferPermissionsData": CreditTransferPermissionsDataType,
"paymentPreferences": PaymentPreferenceConnectionTypeConnection,
"debtLedger": LedgerType,
"agreements": AgreementConnection,
"supportsStatements": true,
"supportsInvoices": true,
"currentDirectDebitInstructionInvalidatedWithVendor": true
}Fields
| Name | Description |
|---|---|
|
List of JoinSupplierProcess for an account. |
|
List of LeavePropertyProcess for an account. |
|
List of LeaveSupplierProcess for an account. |
|
List of OccupyPropertyProcess for an account. |
Example
{
"leaveSupplierProcesses": LeaveSupplierProcessConnectionTypeConnection,
"joinSupplierProcesses": JoinSupplierProcessConnectionTypeConnection,
"occupyPropertyProcesses": OccupyPropertyProcessConnectionTypeConnection,
"leavePropertyProcesses": LeavePropertyProcessConnectionTypeConnection
}LifetimeTelemetry
A container for some basic metrics to show how the heating system has performed over its lifetime.
Note that "its lifetime" may not be the actual life of the heat pump, but may have been reset when it was last provisioned.
Fields
| Name | Description |
|---|---|
|
The electrical energy drawn by the heat pump over its lifetime. |
|
The heat energy emitted by the heat pump over its lifetime. |
|
When these measurements were taken. |
|
The average lifetime coefficient of performance up to the time of measurement. |
LineCommonError
A base error type. Should be used for general application or lower level errors.
Fields
| Name | Description |
|---|---|
|
The field that for which this error should be associated. |
|
The error message to display to the user. |
Example
{
"message": "abc123",
"field": "abc123"
}LineEmoji
A LINE specific emoji object. refs: https://developers.line.biz/en/reference/messaging-api/#text-message
Fields
| Name | Description |
|---|---|
|
The emoji id. |
|
The location of the emoji in the message. |
|
The length of the emoji string placeholder. |
|
The product id. |
Example
{
"index": 1,
"length": 1,
"productId": "abc123",
"emojiId": "abc123"
}LineItemConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
Example
{
"pageInfo": PageInfo,
"edges": LineItemEdge
}LineItemEdge
A Relay edge containing a LineItem and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": LineItemType,
"cursor": "abc123"
}LineItemType
A record of spend on consumption between two points in time.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"netAmount": "1.0",
"numberOfUnits": "1.0",
"itemType": "abc123",
"settlementUnit": "abc123"
}LineLinkRedirectResponse
Link Successful. Complete link process with LINE.
Fields
| Name | Description |
|---|---|
|
Example
{
"redirectUrl": "abc123"
}Fields
| Name | Description |
|---|---|
|
Keywords describing the sticker. |
|
Sticker package id. |
|
Sticker resource type. |
|
Sticker id. |
|
Text used to customize some stickers. |
Example
{
"packageId": "abc123",
"stickerId": "abc123",
"resourceType": "abc123",
"keywords": "abc123",
"text": "abc123"
}Fields
| Name | Description |
|---|---|
|
The display content. |
|
The emojis in the message. |
Example
{
"displayContent": "abc123",
"emojis": [LineEmoji]
}LinkAccountToBusiness
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11104: Business role already allocated.
- KT-CT-11105: Business role already allocated.
- KT-CT-11106: Unauthorized.
- KT-CT-11107: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The business the account was linked to. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"business": BusinessType
}LinkActionType
An action which navigates to any URL.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the object. |
|
The name of the action object's type. |
|
The name of the object's type. |
|
The URL to navigate to. |
Example
{
"typeName": "abc123",
"id": "abc123",
"typename": "abc123",
"url": "abc123"
}LinkTokenNotFound
Returned when no LineAccountLink record matching the parameters exists.
Fields
| Name | Description |
|---|---|
|
The type of error that occurred. |
Example
{
"type": "NO_MATCHING_LINE_LINK"
}Fields
| Name | Description |
|---|---|
|
The combined average montly cost for all markets based on usage. |
|
Suggested temporary adjustment to ongoing usage amount to cover debt or overpayment. |
|
Breakdown of customer's estimated or real usage per market and per month. |
|
The balance the ledger has at the time of review. |
|
The amount the customer is paying monthly at the time of the review. |
|
The date that we used to calculate the review of the ledger. |
|
The suggested monthly payment amount in minor currency following the payment adequacy review. |
|
The balance we expect the ledger to have at the end period of the review. |
Example
{
"suggestedNewMonthlyAmount": 1,
"consumption": ConsumptionBreakdownConnectionTypeConnection,
"averageMonthlyCharge": 1,
"existingMonthlyAmount": 1,
"balanceAdjustment": 1,
"currentBalance": 1,
"targetBalance": 1,
"reviewedOn": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
How much balance we expect the account to have at this time of year. |
|
Breakdown of customer's usage per source and per month. |
|
The suggested monthly payment amount in pence following the payment adequacy review. |
|
The date that we used to calculate the review of the account. |
|
How much balance we expect the account to have at this time of year. |
Example
{
"recommendedPayment": PaymentBreakdown,
"currentBalance": 1,
"targetBalance": 1,
"estimatedConsumption": [ConsumptionBreakdown],
"reviewedOn": "2020-01-01"
}LiveTelemetry
A container for some basic metrics relevant to the current state of the heating system.
Fields
| Name | Description |
|---|---|
|
The coefficient of performance at the time of measurement. |
|
The rate of heat flow from the heat pump at a given time. |
|
The temperature outdoors. |
|
The power being drawn by the heat pump at a given time. |
|
When these measurements were taken. |
Example
{
"readAt": "2020-01-01T00:00:00.000Z",
"coefficientOfPerformance": "1.0",
"powerInput": Power,
"heatOutput": Power,
"outdoorTemperature": Temperature
}Fields
| Name | Description |
|---|---|
|
The property ID of the location. |
Example
{
"propertyId": "abc123"
}LoyaltyCardType
A loyalty card.
Fields
| Name | Description |
|---|---|
|
|
|
The number of the loyalty card. |
|
The scheme of the loyalty card. |
|
The status of the loyalty card. |
Example
{
"id": "abc123",
"scheme": "abc123",
"number": "abc123",
"status": "abc123"
}LoyaltyPointLedgerEntryType
A Loyalty Point ledger entry.
Fields
| Name | Description |
|---|---|
|
The account number associated with the entry. |
|
Equal to the |
|
Equal to the |
|
|
|
A unique idempotency key for the operation. |
|
The |
|
The date the points were added to the ledger. |
|
The reason the entry was being added. |
|
The value of the charge or credit. |
Example
{
"id": "abc123",
"ledgerType": "abc123",
"value": "abc123",
"balanceBroughtForward": "abc123",
"balanceCarriedForward": "abc123",
"reasonCode": "abc123",
"idempotencyKey": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"postedAt": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the account is eligible to join the loyalty points program. |
|
The primary reason for ineligibility, if any. |
Example
{
"isEligible": true,
"primaryIneligibilityReason": "abc123"
}Fields
| Name | Description |
|---|---|
|
Identifier for meter point. |
|
List of available products for the meter point. |
Example
{
"mpxn": "abc123",
"products": [EnergyProductType]
}MarkPrintBatchAsProcessed
Mark a closed print batch as Processed
The possible errors that can be raised are:
- KT-CT-9011: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"printBatch": PrintBatchType
}MarketSupplyQuoteRequestType
A quote request.
Fields
| Name | Description |
|---|---|
|
|
|
The code of the created quote. |
|
List of quoted supply points. |
|
|
|
List of terms and conditions applicable to the quote. |
Example
{
"acceptedAt": "2020-01-01T00:00:00.000Z",
"requestedAt": "2020-01-01T00:00:00.000Z",
"code": "abc123",
"quotedSupplyPoints": MarketSupplyQuotedSupplyPointConnectionTypeConnection,
"termsAndConditions": TermsAndConditionsConnectionTypeConnection
}MarketSupplyQuotedProductConnectionTypeConnection
Pagination for quoted products.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": MarketSupplyQuotedProductConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}MarketSupplyQuotedProductConnectionTypeEdge
A Relay edge containing a MarketSupplyQuotedProductConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": MarketSupplyQuotedProductType,
"cursor": "abc123"
}MarketSupplyQuotedProductType
A product quoted for a supply point.
Fields
| Name | Description |
|---|---|
|
A JSON object containing client parameters on the quoted product. |
|
|
|
The product associated with the quoted product. |
|
Example
{
"id": "abc123",
"wasSelected": true,
"product": SupplyProductType,
"clientParams": {"key": "value"}
}MarketSupplyQuotedSupplyPointConnectionTypeConnection
Pagination for quoted supply points.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": MarketSupplyQuotedSupplyPointConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}MarketSupplyQuotedSupplyPointConnectionTypeEdge
A Relay edge containing a MarketSupplyQuotedSupplyPointConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": MarketSupplyQuotedSupplyPointType,
"cursor": "abc123"
}MarketSupplyQuotedSupplyPointType
A supply point quoted as part of a quote request.
Fields
| Name | Description |
|---|---|
|
A JSON object containing client parameters on the quoted product. |
|
The ID of the quoted supply point. |
|
The identifier of the quoted supply point, if one exists. |
|
The market this supply point belongs to. |
|
Details of all products quoted for this supply point. |
|
The supply point being quoted. |
Example
{
"marketName": "abc123",
"id": "abc123",
"identifier": "abc123",
"quotedProducts": MarketSupplyQuotedProductConnectionTypeConnection,
"supplyPoint": SupplyPointType,
"clientParams": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
A list of any errors that occurred while running this mutation. |
|
A Kraken Token that can be used to authenticate to the API, masquerading as the desired user. |
Example
{
"token": "abc123",
"errors": [ErrorType]
}Fields
| Name | Description |
|---|---|
|
The maximum amount available to be requested as a refund. |
|
The reason why a specific amount is the maximum available to be requested as a refund. |
|
The recommended minimum balance an account should have when asking for a refund. |
Example
{
"amount": 1,
"reasonToRecommendAmount": "MAX_AVAILABLE_AMOUNT",
"recommendedBalance": 1
}MeasurementConnection
Pagination for measurements.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": MeasurementEdge,
"totalCount": 1,
"edgeCount": 1
}MeasurementEdge
A Relay edge containing a Measurement and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": MeasurementInterface,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
This type will return more granular data about the measurement. |
|
The datetime the measurement was taken. |
|
The data source of the measurement. |
|
The unit of the measurement. |
|
The value of the measurement. |
Example
{
"source": "abc123",
"metaData": MeasurementsMetadataOutput,
"value": "1.0",
"unit": "abc123",
"readAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Statistics relating to the parent measurement node. |
|
The source information relating to the parent measurement node. |
Example
{
"utilityFilters": UtilityFiltersOutput,
"statistics": [StatisticOutput]
}Fields
| Name | Description |
|---|---|
|
The channel that the message was sent through. |
|
The date/time that Kraken dispatched the message to the vendor. |
|
The date/time that the message was confirmed as having failed to send. |
Example
{
"channel": "EMAIL",
"dispatchedAt": "2020-01-01T00:00:00.000Z",
"failedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": MessageEdge,
"totalCount": 1,
"edgeCount": 1
}MessageEdge
A Relay edge containing a Message and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Message,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The key for the metadata. |
|
The metadata value. |
Example
{
"key": "abc123",
"value": {"key": "value"}
}MinimumContractLengthType
Represents the minimum term of a contract.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The minimum length of the contract. |
|
The type of the term. |
|
The unit of time for the contract length. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true,
"length": 1,
"unitOfTime": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The ISO-4217 code for the currency. |
Example
{
"amount": "1.0",
"currency": "abc123"
}NotifiableApplicationType
Represents an application that can receive push notifications.
Fields
| Name | Description |
|---|---|
|
Bundle ID or package name of the app. |
|
|
|
Project ID used in push notification delivery service. (Currently: AWS Pinpoint) |
|
|
|
|
|
Human readable name for the app. |
|
|
|
Example
{
"id": "abc123",
"name": "abc123",
"bundleId": "abc123",
"service": "GCM",
"externalProvider": "PINPOINT",
"externalProjectId": "abc123",
"description": "abc123",
"pushNotificationBindings": PushNotificationBindingType
}OCPPAuthentication
Open Charge Point Protocol (OCPP) authentication.
Take the given OCPP authentication details and trigger OCPP authentication.
The possible errors that can be raised are:
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4310: Unable to register OCPP authentication details.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}Example
{
"url": "abc123",
"username": "abc123"
}Fields
| Name | Description |
|---|---|
|
The amount of the payment in pence. |
|
The payment's id. |
|
Whether or not the payment can be amended. |
|
Whether or not the payment has been cancelled. |
|
The date that the payment was/will be made. |
Example
{
"id": "abc123",
"amount": 1,
"paymentDate": "2020-01-01",
"isAmendable": true,
"isCancelled": true
}ObtainKrakenJSONWebToken
The unifying approach used to get a Kraken token (JWT: JSON Web Token) with different types of input.
The currently supported inputs are: - account user email/password combination - account user API key - organization live secret key - pre-signed key - refresh token
The possible errors that can be raised are:
- KT-CT-1135: Invalid data.
- KT-CT-1134: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The body payload of the Kraken Token. The same information can be obtained by using JWT decoding tools on the value of the |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
A Unix timestamp representing the point in time at which the refresh token will expire. |
|
A token that can be used in a subsequent call to |
|
The Kraken Token. Can be used in the |
Example
{
"possibleErrors": [PossibleErrorType],
"token": "abc123",
"payload": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"refreshToken": "abc123",
"refreshExpiresIn": 1
}ObtainLongLivedRefreshToken
Obtain a long-lived refresh token.
This mutation is limited to authorized third-party organizations only.
Account users can only generate short-lived refresh tokens.
The short-lived refresh tokens (for account users) can be obtained from the 'refreshToken' field in 'obtainKrakenToken' mutation.
The possible errors that can be raised are:
- KT-CT-1120: The Kraken Token has expired.
- KT-CT-1121: Please use Kraken Token to issue long-lived refresh tokens.
- KT-CT-1132: Unauthorized.
- KT-CT-1122: Long-lived refresh tokens can only be issued for account users.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
|
|
Example
{
"possibleErrors": [PossibleErrorType],
"refreshToken": "abc123",
"refreshExpiresIn": 1
}OccupancyPeriodType
An occupancy period for a property.
Fields
| Name | Description |
|---|---|
|
Account number associated with this occupancy period. |
|
Date the occupancy period is effective from. |
|
Date the occupancy period is effective to. |
|
|
|
Whether the account associated with the occupancy period is an occupier account type. |
Example
{
"id": "abc123",
"effectiveFrom": "2020-01-01T00:00:00.000Z",
"effectiveTo": "2020-01-01T00:00:00.000Z",
"isOccupier": true,
"accountNumber": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
A Kraken Token that can be used to call the 'occupy' mutation for the account. |
|
Example
{
"account": "abc123",
"address": "abc123",
"date": "abc123",
"propertyId": 1,
"occupyToken": "abc123"
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"account": AccountInterface
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": OccupyPropertyProcessConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}OccupyPropertyProcessConnectionTypeEdge
A Relay edge containing a OccupyPropertyProcessConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OccupyPropertyProcessType,
"cursor": "abc123"
}OccupyPropertyProcessType
Represents a Occupy Property process.
Fields
| Name | Description |
|---|---|
|
The ID or the primary key of the lifecycle process. |
|
|
|
The status of the process. |
|
The supply points associated with the process. |
Example
{
"id": "abc123",
"status": "PENDING",
"occupyAt": "2020-01-01T00:00:00.000Z",
"supplyPoints": SupplyPointConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
The Device ID of the communication hub associated with the property of the Cared-For account, which must also have an Octopus Mini device installed. |
|
The first line of the address of the property associated with the Cared-For account. |
|
The ID of the property the Mini will be onboarded in. |
Example
{
"chfDeviceId": "abc123",
"propertyAddressLine1": "abc123",
"propertyId": "abc123"
}Fields
| Name | Description |
|---|---|
|
The Device ID of the smart meter associated with the property of the Cared-For account, which must also have an Octopus Mini device installed. |
|
The first line of the address of the property associated with the Cared-For account. |
Example
{
"meterDeviceId": "abc123",
"propertyAddressLine1": "abc123"
}Fields
| Name | Description |
|---|---|
|
The current enrollment status of the account. |
|
Describes whether or not the request user is the nominated user for this account. |
|
Describes whether or not this account is enrolled in the Octoplus campaign. Deprecated The 'isOctoplusEnrolled' field is deprecated. |
|
Information about an account's eligibility for joining the Octoplus campaign. |
|
URL for the octoplus snap page if account is eligible. |
|
Describes if the account should use v2. |
Example
{
"isOctoplusEnrolled": true,
"enrollmentStatus": "ENROLLED",
"isLoyaltyPointsUser": true,
"octoplusEligibility": OctoplusEligibilityType,
"octoplusSnapWebUrl": OctoplusSnapWebUrlType,
"shouldUseV2": true
}Fields
| Name | Description |
|---|---|
|
Describes why an account is ineligible for Octoplus. Will be null if the account is eligible. Deprecated The 'ineligibilityReason' field is deprecated. |
|
Returns multiple reasons for why an account is ineligible for Octoplus. Will be empty if the account is eligible. |
|
Describes whether or not this account is eligible to join the Octoplus campaign. |
Example
{
"isEligible": true,
"ineligibilityReason": "OCTOPLUS_DISABLED",
"ineligibilityReasons": "OCTOPLUS_DISABLED"
}Fields
| Name | Description |
|---|---|
|
Whether or not this account has been enrolled in the Octoplus campaign. |
Example
{
"hasEnrolled": true
}Fields
| Name | Description |
|---|---|
|
Describes whether or not the Octoplus campaign should be shown in clients. |
|
Describes whether or not Octoplus partner offer list should be shown in clients. |
|
Describes whether or not Octoplus partner offers should be shown in clients. |
|
Describes whether or not Octoplus rewards should be shown in clients. |
|
Describes whether or not Octoplus Shoptopus offers should be shown in clients. |
|
Describes whether or not the new Octopoints system should be shown in clients. |
Example
{
"shouldClientDisplayOctopointsV2": true,
"shouldClientDisplayOctoplus": true,
"shouldClientDisplayOctoplusRewards": true,
"shouldClientDisplayOctoplusPartnerOffers": true,
"shouldClientDisplayOctoplusShoptopusOffers": true,
"shouldClientDisplayOctoplusPartnerOfferList": true
}Fields
| Name | Description |
|---|---|
|
The FAQ answer field. |
|
The FAQ question field. |
Example
{
"question": "abc123",
"answer": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": OctoplusOfferGroupConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}OctoplusOfferGroupConnectionTypeEdge
A Relay edge containing a OctoplusOfferGroupConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OctoplusOfferGroupType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The mobile banner url. |
Example
{
"bannerMobile": "abc123"
}Fields
| Name | Description |
|---|---|
|
The type of offer group. |
|
Unique identifier of the Offer Group. |
|
The image urls for this offer. |
|
The name describing offer group. |
|
Example
{
"id": 1,
"name": "abc123",
"groupType": "abc123",
"imageUrls": OctoplusOfferGroupImageUrlsType,
"octoplusOffers": OctoplusOfferType
}Fields
| Name | Description |
|---|---|
|
The banner image url. |
|
The mobile banner url. |
|
The logo url. |
|
The mobile logo url. Deprecated The 'logoMobile' field is deprecated. |
Example
{
"banner": "abc123",
"bannerMobile": "abc123",
"logo": "abc123",
"logoMobile": "abc123"
}Fields
| Name | Description |
|---|---|
|
The available sites url for this offer. |
|
The category of the offer. |
|
Describes whether the user should be able to claim this offer, and the reason if not. |
|
The datetime at which the user should no longer be able to claim this offer. |
|
The short description of the offer. |
|
The faqs for this offer. |
|
The image urls for this offer. |
|
The long description of the offer. |
|
The name of the offer to be displayed to the user. |
|
The name of the reward partner. |
|
The partner site url for this offer. |
|
The points cost of claiming this offer. |
|
The price tag for this offer. |
|
The slug to be used as the offer identifier. |
|
The terms and conditions to display to the user. |
|
The instructions for the user as to how to use their claimed reward. |
Example
{
"slug": "abc123",
"name": "abc123",
"description": "abc123",
"longDescription": "abc123",
"partnerName": "abc123",
"priceTag": "abc123",
"pointsCost": 1,
"availableSitesUrl": "abc123",
"partnerSiteUrl": "abc123",
"imageUrls": OctoplusOfferImageUrlsType,
"termsAndConditions": "abc123",
"faqs": [OctoplusOfferFAQsType],
"usageInstructions": "abc123",
"category": "abc123",
"claimAbility": OctoplusRewardClaimAbilityType,
"claimBy": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Describes whether the user should be able to claim this offer. |
|
Describes why a user cannot claim this offer. |
Example
{
"canClaimOffer": true,
"cannotClaimReason": "OUT_OF_STOCK"
}Fields
| Name | Description |
|---|---|
|
The account number associated with this reward. |
|
The datetime at which the reward was initially claimed. |
|
The unique id of the reward. |
|
The offer claimed as part of this reward. |
|
The display name of the offer. Deprecated The 'offerName' field is deprecated. |
|
The human-readable identifier for the offer. Deprecated The 'offerSlug' field is deprecated. |
|
The name of the reward partner. Deprecated The 'partnerName' field is deprecated. |
|
The price tag for the offer. Deprecated The 'priceTag' field is deprecated. |
|
The current status of the reward. |
|
The instructions for how to use the reward. Deprecated The 'usageInstructions' field is deprecated. |
|
The voucher associated with this reward. |
Example
{
"id": 1,
"accountNumber": "abc123",
"offer": OctoplusOfferType,
"offerSlug": "abc123",
"offerName": "abc123",
"priceTag": "abc123",
"partnerName": "abc123",
"usageInstructions": "abc123",
"vouchers": [VoucherType],
"claimedAt": "2020-01-01T00:00:00.000Z",
"status": "PENDING"
}Fields
| Name | Description |
|---|---|
|
Domain for the snap web url, ex. 'octopus.energy'. |
|
Path for the snap web url, ex. 'snap/webview'. |
|
URL for the octoplus snap page if account is eligible. Eg. 'https://octopus.energy/snap/webview?abcd=efg'. |
Example
{
"url": "abc123",
"domain": "abc123",
"path": "abc123"
}Fields
| Name | Description |
|---|---|
|
The barcode value/code. |
|
The type of barcode to render. |
|
The value to be encoded in the rendered barcode. |
|
The voucher code. |
|
The datetime at which the voucher will no longer be useable. |
|
The type of voucher. |
Example
{
"code": "abc123",
"type": "abc123",
"barcode": "abc123",
"barcodeValue": "abc123",
"barcodeFormat": "abc123",
"expiresAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The date and time when offer group was created. |
|
The Actor who created the offer group. |
|
Identifier of the offer group. |
|
One or more Offers contained in the offer group. |
Fields
| Name | Description |
|---|---|
|
The date and time when offer was accepted. |
|
The Actor who created the offer. |
|
Description of the offer. |
|
Identifier of the Offer. |
|
The Quote this offer is related to. |
|
The date and time when offer was rejected. |
|
The date and time from which the offer becomes valid. |
|
The date and time until which the offer remains valid. |
Example
{
"identifier": "abc123",
"quote": QuoteType_,
"description": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"acceptedAt": "2020-01-01T00:00:00.000Z",
"rejectedAt": "2020-01-01T00:00:00.000Z",
"createdBy": ActorType
}Fields
| Name | Description |
|---|---|
|
The communication strategy for this appointment. |
|
Appointment job details. |
|
The type of job being booked for the appointment. |
Example
{
"jobType": NonEmptyString,
"commsStrategy": "SEND_ALL",
"jobDetails": OnSiteJobsAppointmentJobDetailsType
}Fields
| Name | Description |
|---|---|
|
Future payment mode for electricity asset. |
|
Future payment mode for gas asset. |
|
Whether the appointment requires medium pressure gas handling. |
|
Whether the appointment requires a three-phase installation. |
Example
{
"requiresThreePhaseInstall": true,
"requiresMediumPressureGas": true,
"elecFuturePaymentMode": "PREPAY",
"gasFuturePaymentMode": "PREPAY"
}OnSiteJobsAppointmentType
An appointment linked to a request
Fields
| Name | Description |
|---|---|
|
|
|
|
|
The external reference provided by the vendor/contractor for the appointment. |
|
|
|
|
|
The current status of the appointment. |
|
|
|
Example
{
"id": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"jobType": "abc123",
"appointmentDate": "2020-01-01",
"timeSlotStart": "00:00:00.000Z",
"timeSlotEnd": "00:00:00.000Z",
"createdAt": "2020-01-01T00:00:00.000Z",
"status": "BOOKED",
"externalReference": "abc123"
}Fields
| Name | Description |
|---|---|
|
The short name (first name) of the support user. |
Example
{
"shortName": "abc123"
}OperationsTeamType
An extension of the GBR OperationsTeamType with OEGB-specific fields.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
The leader of the operations team. |
|
The location of the operations team. |
|
Example
{
"id": 1,
"teamName": "abc123",
"isOffline": true,
"isAcceptingCalls": true,
"location": "abc123",
"leader": OperationsTeamLeaderType
}Fields
| Name | Description |
|---|---|
|
Lead legal contact email. |
|
Extra details about the opportunity. |
|
Lead legal name. |
|
Opportunity number. |
|
Opportunity ID. |
|
Lead legal contact phone number. |
|
Current stage in a funnel. |
Example
{
"opportunityId": "abc123",
"name": "abc123",
"email": "abc123",
"phoneNumber": "abc123",
"number": "abc123",
"stage": "abc123",
"extraDetails": {"key": "value"}
}OptInToCharityDonation
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-GB-11903: Could not opt in to charity donation.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Amount that will be donated each month. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"amount": "ONE"
}OptOutOfCharityDonation
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-GB-11902: Could not opt out of charity donation.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Has the account opted out of donating to charity. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"isOptedOut": true
}Fields
| Name | Description |
|---|---|
|
If known, this is the account that a call is about. For inbound calls, we attempt to identify the account based on the phone number of the incoming call. For outbound calls, the account will be automatically set if the call was initiated from an account page. For all call types, the account can be updated, for example to correct a misidentification of an incoming call. |
|
The ID of the call. |
|
Metadata related to the call, for example metrics or data passed via an interactive voice response (IVR). |
Example
{
"id": "abc123",
"account": AccountType,
"metadata": CallMetadataItemType
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"type": "SALE",
"category": "SUCCESS",
"reason": "abc123"
}PageInfo
The Relay compliant PageInfo type, containing data necessary to paginate this connection.
Fields
| Name | Description |
|---|---|
|
When paginating forwards, the cursor to continue. |
|
When paginating forwards, are there more items? |
|
When paginating backwards, are there more items? |
|
When paginating backwards, the cursor to continue. |
Example
{
"hasNextPage": true,
"hasPreviousPage": true,
"startCursor": "abc123",
"endCursor": "abc123"
}PauseDunning
Pause the dunning process for an account.
The possible errors that can be raised are:
- KT-CT-4178: No account found with given account number.
- KT-CT-11301: Account not in a dunning process for the given path name.
- KT-CT-11302: No active dunning process found.
- KT-CT-11303: Multiple active dunning processes found.
- KT-CT-11304: Dunning pause process failed verifying the dates.
- KT-CT-11305: Pausing the dunning process failed.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the pause has been successfully created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"pauseCreated": true
}Payment
A payment from the customer to the supplier.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the account the transaction belongs to. |
|
Gross amount including tax (when payable). Refer to the Deprecated The 'amount' field is deprecated. |
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The customer's resulting balance after this transaction has been applied, in the smallest unit of currency. |
|
The unique identifier for the most recent billing document linked with the transaction.Note: a transaction may be linked with multiple documents, but this field will only return the identifier for the most recent billing document. |
|
The date time when the transaction is created. |
|
Returns True if the transaction is linked with a statement. |
|
|
|
Deprecated. Deprecated The 'isAccountCharge' field is deprecated. |
|
Deprecated. Deprecated The 'isAccountPayment' field is deprecated. |
|
Deprecated. Deprecated The 'isCredit' field is deprecated. |
|
Whether the statement this transaction is on has been held. A held statement is not sent to a customer automatically, but is instead marked for manual attention by operations staff. Returns False if a statement is not linked with the transaction. |
|
Whether this transaction has been issued on any billing document.Note: Look for the most recently issued transaction instead of looking through all transactions as some accounts may have initial transactions that were not issued.This will return False if the transaction is not associated with any billing documents. |
|
Whether a payment has been reversed due to a late failure.Sometimes a payment is marked cleared, only for Kraken to be notified days/weeks later that the payment has failed. |
|
|
|
Returns the note field value for the transaction, which contains additional info. |
|
The transaction type of the payment. |
|
|
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123",
"amount": 1,
"amounts": TransactionAmountType,
"balanceCarriedForward": 1,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "abc123",
"billingDocumentIdentifier": "abc123",
"statementId": "abc123",
"isReversed": true,
"hasStatement": true,
"note": "abc123",
"reasonCode": "abc123",
"isLateFailedPayment": true,
"paymentTransactionType": "DD_FIRST_COLLECTION"
}PaymentAdequacyDetailsType
Payment adequacy adjusts fixed payment schedules to maintain a healthy ledger balance over a year.
Fields
| Name | Description |
|---|---|
|
This ledger will be exempt from default Payment Adequacy. This may mean that it is completely exempt, or handled with special rules. |
Example
{
"isCurrentlyExempt": true
}Fields
| Name | Description |
|---|---|
|
The suggested monthly payment amount in pence following the payment adequacy review. |
Example
{
"suggestedDirectDebitAmount": 1
}Fields
| Name | Description |
|---|---|
|
Temporary amount to cover debt. |
|
Amount which covers ongoing usage. |
|
Total to pay: ongoing + adjustment. |
Example
{
"total": 1,
"ongoing": 1,
"adjustment": 1
}Fields
| Name | Description |
|---|---|
|
Fingerprint. |
|
Returns True if the fingerprint exists, Fasle otherwise. |
|
Returns True if the fingerprint is risk-listed, Fasle otherwise. |
Example
{
"fingerprint": "abc123",
"isFound": true,
"isRiskListed": true
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PaymentForecastConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PaymentForecastConnectionTypeEdge
A Relay edge containing a PaymentForecastConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentForecastType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
The payment method used for the forecasted payment. |
|
Example
{
"paymentNumber": 1,
"date": "2020-01-01",
"amount": 1,
"method": "BACS_TRANSFER"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PaymentInstructionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PaymentInstructionConnectionTypeEdge
A Relay edge containing a PaymentInstructionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentInstructionType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The account user who is an owner of this payment instruction. |
|
The business who is an owner of this payment instruction. |
Example
{
"accountUser": AccountUserType,
"business": BusinessType
}PaymentInstructionType
Payment Instructions
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A masked reference to a recurring payment method. |
|
The owners of the financial account this instruction represents. |
|
|
|
|
|
The supplementary ledger for this payment instruction. |
|
|
|
Example
{
"id": "abc123",
"status": "abc123",
"sortCode": "abc123",
"iban": "abc123",
"accountHolder": "abc123",
"instructionType": "abc123",
"cardPaymentNetwork": "abc123",
"cardExpiryMonth": 1,
"cardExpiryYear": 1,
"supplementaryLedger": SupplementaryLedgerType,
"bankCode": "abc123",
"accountType": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"vendor": "abc123",
"cardNumber": "abc123",
"cardType": "abc123",
"maskedAccountIdentifier": "abc123",
"owners": [PaymentInstructionOwnerType]
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PaymentPlanConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PaymentPlanConnectionTypeEdge
A Relay edge containing a PaymentPlanConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentPlanType,
"cursor": "abc123"
}PaymentPlanPaymentType
An object that represents a planned payment for a payment plan.
Example
{
"payableDate": "2020-01-01",
"amount": 1,
"paymentType": "abc123"
}PaymentPlanType
An object that represents a payment plan.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
The ledger number for this payment plan or None if one does not exist. |
|
The next planned payment for this payment plan. |
|
|
|
|
|
|
|
|
|
The display name of the strategy used for this payment plan or None if one does not exist. |
|
Example
{
"id": "abc123",
"account": AccountType,
"initialScheduleType": "abc123",
"strategyName": "abc123",
"status": "abc123",
"offeredAt": "2020-01-01T00:00:00.000Z",
"offerExpiresAt": "2020-01-01T00:00:00.000Z",
"acceptedAt": "2020-01-01T00:00:00.000Z",
"payments": PaymentPlanPaymentType,
"nextPayment": PaymentPlanPaymentType,
"strategyDisplayName": "abc123",
"ledgerNumber": "abc123"
}PaymentPreferenceConnectionTypeConnection
Pagination object for PaymentPreferenceUnion
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PaymentPreferenceConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PaymentPreferenceConnectionTypeEdge
A Relay edge containing a PaymentPreferenceConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentPreferenceUnion,
"cursor": "abc123"
}PaymentRequestConnectionTypeConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PaymentRequestConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PaymentRequestConnectionTypeEdge
A Relay edge containing a PaymentRequestConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentRequestType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The amount the customer is expected to pay in minor currency. |
|
The date the payment is expected to be made. |
|
The amount that was funded by each funding source. |
|
The status of the payment. |
|
The total amount of the payment in minor currency. |
Example
{
"expectedPaymentDate": "2020-01-01",
"paymentStatus": "abc123",
"totalAmount": 1,
"customerAmount": 1,
"fundingSourceAmounts": FundingSourceAmountConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
A list of payment requests for a given ledger. |
Example
{
"paymentRequest": PaymentRequestConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PaymentScheduleConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PaymentScheduleConnectionTypeEdge
A Relay edge containing a PaymentScheduleConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentScheduleType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The arguments of the delay configuration. |
|
The code of the delay configuration. |
Example
{
"code": "abc123",
"args": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
A human-readable description of the value. |
|
Direction of payment day. |
Example
{
"direction": "OF_MONTH",
"description": "abc123"
}PaymentScheduleType
An object that represents when we have agreed to take payments from a payment instruction.
Fields
| Name | Description |
|---|---|
|
The delay configuration for this payment schedule. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Details of the payment_day value. |
|
The frequency of the payment schedule. |
|
|
|
|
|
The reason the payment schedule was created. |
|
The method of payment for the schedule. Deprecated The 'scheduleType' field is deprecated. |
|
The supplementary ledger for this payment schedule, if it is on one. |
|
The sum of the payment adequacy contributions on the payment schedule that are expected to be taken before the debt repayment is complete. |
|
|
|
Example
{
"id": "abc123",
"supplementaryLedger": SupplementaryLedgerType,
"validFrom": "2020-01-01",
"validTo": "2020-01-01",
"reason": "GENERAL_ACCOUNT_PAYMENT",
"paymentHolidayReason": "abc123",
"paymentDay": 1,
"paymentFrequency": "Weekly",
"paymentFrequencyMultiplier": 1,
"paymentAmount": 1,
"paymentAdequacyAdjustment": 1,
"paymentAdequacyAdjustmentExpiryDate": "2020-01-01",
"isVariablePaymentAmount": true,
"totalDebtAmount": 1,
"isPaymentHoliday": true,
"scheduleType": "BACS_TRANSFER",
"paymentDayDetails": PaymentSchedulePaymentDayDetailsType,
"delayConfiguration": PaymentScheduleDelayConfigurationType
}PaysByDirectDebitType
Represents a restriction for if an account should pay only by direct debit in a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true
}PerformBoostCharge
Initiate a boost charge for an electric vehicle (EV).
This will start charging the EV and will not stop until the battery reaches 100% charged.
If it is not possible to initiate a boost charge, a KT-CT-4357 error will be returned.
It may have a boostChargeRefusalReasons extension which lists the reasons why the boost
charge was refused. Possible reasons include:
BC_DEVICE_NOT_YET_LIVE(device is not yet live)BC_DEVICE_RETIRED(device is retired)BC_DEVICE_SUSPENDED(device is suspended)BC_DEVICE_DISCONNECTED(device is disconnected)BC_DEVICE_NOT_AT_HOME(device is not at home)BC_BOOST_CHARGE_IN_PROGRESS(boost charge already in progress)BC_DEVICE_FULLY_CHARGED(device is already fully charged)
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4356: A boost charge cannot currently be performed.
- KT-CT-4357: Unable to trigger boost charge.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}PerformMoveOut
The possible errors that can be raised are:
- KT-GB-6624: An error occurred when trying to process this house move.
- KT-GB-6625: An error occurred when trying to process this house move.
- KT-GB-6626: There was an error processing the PSR data.
- KT-GB-6627: There are missing agent appointments.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account to perform move out. |
|
The new account created as part of the move out process. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountInterface,
"newAccount": AccountInterface
}PerformTestCharge
Initiate a test charge of an electric vehicle (EV).
This is to ensure that the EV or EVSE (charge point) can be controlled remotely and successfully charged for a short period.
If it is not possible to initiate a test charge, a KT-CT-4355 error will be returned. It may have a
testChargeRefusalReasons extension which lists the reasons why the test charge was refused. Possible reasons
include:
TC_DEVICE_LIVE(device is already live)TC_DEVICE_ONBOARDING_IN_PROGRESS(test dispatch already in progress)TC_DEVICE_RETIRED(device is retired)TC_DEVICE_SUSPENDED(device is suspended)TC_DEVICE_DISCONNECTED(device is disconnected)TC_DEVICE_ALREADY_CHARGING(device is already charging)TC_DEVICE_AWAY_FROM_HOME(device is away from home)TC_DEVICE_NO_LOCATION_CONFIGURED(device has no location configured)TC_DEVICE_LOCATION_UNABLE_TO_IDENTIFY(unable to identify device location)TC_DEVICE_LOCATION_MISSING(device location is missing)
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4362: Device not ready for test charge.
- KT-CT-4355: Unable to trigger charge.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}Fields
| Name | Description |
|---|---|
|
|
|
The type of the bill. |
|
The closing balance of an issued billing document. |
|
Position of the billing document in the delinquent debt tracking system. |
|
The date of the constituent bill covered from. |
|
The ID of the constituent bill. |
|
The unique identifier for the billing document. Note: a pending billing document will not have an identifier yet; and not all finalized billing documents will have an identifier assigned to them, in which case this will be null. |
|
Whether the billing document has been annulled. |
|
The date the bill was sent to the customer. |
|
Requesting this field generates a temporary URL at which bill is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). This field can raise an error with errorClass NOT_FOUND if the bill document has not been created/issued yet. This field is deprecated use 'attachments' field instead. Deprecated The 'temporaryUrl' field is deprecated. |
|
The date of the constituent bill covered to. |
|
The total amounts for all charges on the billing document. |
|
The total amounts for all credits on the statement. |
|
Transactions on the given ledger. |
Example
{
"id": "abc123",
"billType": "STATEMENT",
"fromDate": "2020-01-01",
"toDate": "2020-01-01",
"temporaryUrl": "abc123",
"issuedDate": "2020-01-01",
"attachments": BillingAttachmentConnectionTypeConnection,
"identifier": "abc123",
"totalCharges": StatementTotalType,
"totalCredits": StatementTotalType,
"isAnnulled": true,
"transactions": BillTransactionConnectionTypeConnection,
"closingBalance": 1,
"documentDebtPosition": BillingDocumentPositionType
}Fields
| Name | Description |
|---|---|
|
All accounts that are linked to this phone number. A maximum of 26 results are returned. Results are ordered by most likely first. |
|
Our best guess for which account a call with this phone number would be about. |
|
All account users that are linked to this phone number. A maximum of 26 results are returned. Results are ordered by most likely first. |
|
Our best guess for which account user would be calling from this phone number. |
Example
{
"accountBestMatch": AccountType,
"accountAllMatches": AccountConnectionTypeConnection,
"accountUserBestMatch": AccountUserType,
"accountUserAllMatches": AccountUserConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
The action to perform when the button is pressed. |
|
The button style. |
|
Unique identifier of the object. |
|
Title text of the button. |
|
The name of the object's type. |
Example
{
"buttonStyle": "PRIMARY",
"title": "abc123",
"buttonAction": ActionType,
"id": "abc123",
"typename": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the viewer has been blocked due to spending all its allowed points. |
|
The maximum number of points the viewer gets for requests per hour. |
|
The remaining points for the viewer in one hour time limit. |
|
Time To Live: UNIX timestamp when the viewer will get a new allowance of points. |
|
The points used so far in one hour time limit. |
Example
{
"limit": 1,
"remainingPoints": 1,
"usedPoints": 1,
"ttl": 1,
"isBlocked": true
}PointsSizeType
A measurement in points.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the object. |
|
The points value. |
|
The name of the object's type. |
Example
{
"id": "abc123",
"typename": "abc123",
"points": 1
}PortfolioConnectionTypeConnection
Paginator of Operations Team
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PortfolioConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PortfolioConnectionTypeEdge
A Relay edge containing a PortfolioConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PortfolioType,
"cursor": "abc123"
}PortfolioType
An object that represents a portfolio.
Fields
| Name | Description |
|---|---|
|
The accounts associated with this portfolio. |
|
The ancestors of the given portfolio. |
|
|
|
The brand code associated with the portfolio. |
|
|
|
|
|
The depth of the portfolio in the hierarchy. |
|
The descendants of the given portfolio. |
|
|
|
The lead account for this portfolio. |
|
The name of the portfolio. |
|
|
|
Operations team for this portfolio. |
|
The parent portfolio of the given portfolio, if any. |
|
Example
{
"id": "abc123",
"number": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"updatedAt": "2020-01-01T00:00:00.000Z",
"billingName": "abc123",
"collectiveBilling": true,
"operationsTeam": OperationsTeamType,
"leadAccountNumber": "abc123",
"brand": "abc123",
"name": "abc123",
"depth": 1,
"parent": PortfolioType,
"ancestors": PortfolioConnectionTypeConnection,
"descendants": PortfolioConnectionTypeConnection,
"accounts": AccountConnectionTypeConnection
}PortfolioUserRoleType
The role a user has in association with one portfolio.
Fields
| Name | Description |
|---|---|
|
|
|
Portfolio object. |
|
The portfolio role. |
|
Example
{
"id": "abc123",
"user": AccountUserType,
"role": RoleString,
"portfolio": PortfolioType
}PossibleErrorType
The GraphQL error type for displaying information about GraphQL errors that might be raised from the API.
Fields
| Name | Description |
|---|---|
|
The error code that might be returned from the query/mutation. |
|
The error description that might be returned from the query/mutation. |
|
The error message that might be returned from the query/mutation. |
|
The error type that might be returned from the query/mutation. |
Example
{
"message": "abc123",
"code": "abc123",
"type": "abc123",
"description": "abc123"
}PossibleErrorsOutputType
Information and possible errors of the requested query/mutation.
Fields
| Name | Description |
|---|---|
|
Whether the possible authentication errors are included. |
|
Name of the query/mutation whose possible errors are returned. |
|
List of the errors the query/mutation is susceptible of raising. |
|
Type of the query (query or mutation). |
Example
{
"name": "abc123",
"type": "query",
"authErrors": true,
"possibleErrors": [PossibleErrorType]
}PostCredit
The possible errors that can be raised are:
- KT-CT-5316: Invalid data.
- KT-CT-5311: The credit reason with the requested code is deprecated.
- KT-CT-5312: The credit reason with the requested code does not exist.
- KT-CT-5313: An error occurred whilst posting the credit.
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Posted account credit. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"credit": Credit
}PostEVPublicChargingAccountCharge
Initiate a standalone payment for an account charge.
The possible errors that can be raised are:
- KT-CT-5813: Invalid data.
- KT-CT-5815: Invalid data.
- KT-CT-5817: External Account not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account Charge reference. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountCharge": AccountChargeType
}PostEVPublicChargingCharge
Initiate a standalone payment for a charging session.
The possible errors that can be raised are:
- KT-CT-5813: Invalid data.
- KT-CT-5814: Invalid data.
- KT-CT-5815: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Charging session charge reference. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountCharge": AccountChargeType
}PostEVPublicChargingCredit
The possible errors that can be raised are:
- KT-CT-5815: Invalid data.
- KT-CT-5816: Invalid data.
- KT-CT-5817: External Account not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Posts an EV Public charging credit. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"credit": Credit
}Power
Describes the power (not energy) being consumed (as electricity) or returned (as heat) by the system at a given point in time.
Differs from Energy in that it describes the rate at which energy is being transferred at
a given point in time.
Fields
| Name | Description |
|---|---|
|
The units in which the power is being measured. |
|
The amount of power (not energy) transmitted to or from the heat pump. |
Example
{
"value": "1.0",
"unit": "KILOWATT"
}Fields
| Name | Description |
|---|---|
|
|
|
The type of the bill. |
|
The date of the bill is covered from. |
|
The gross amount of the historical bill. |
|
The ID of the bill. |
|
The unique identifier of a historical bill. It will usually be present on the billing document itself. |
|
The date the bill was sent to the customer. |
|
The params associated with the historical bill. |
|
Requesting this field generates a temporary URL at which bill is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). This field can raise an error with errorClass NOT_FOUND if the bill document has not been created/issued yet. This field is deprecated use 'attachments' field instead. Deprecated The 'temporaryUrl' field is deprecated. |
|
The date of the bill is covered to. |
Example
{
"id": "abc123",
"billType": "STATEMENT",
"fromDate": "2020-01-01",
"toDate": "2020-01-01",
"temporaryUrl": "abc123",
"issuedDate": "2020-01-01",
"attachments": BillingAttachmentConnectionTypeConnection,
"identifier": "abc123",
"params": {"key": "value"},
"grossAmount": 1
}PreSignedToken
A pre-signed, expiring and opaque tokens that can be swapped for a limited scope JWT (Kraken Token).
Fields
| Name | Description |
|---|---|
|
|
|
|
|
The scope that the token will grant to the account user. |
Example
{
"key": "abc123",
"scope": "SUBMIT_METER_READINGS",
"isValid": true
}PreferredInstruction
Represents the preference of the user to be charged using a specific payment instruction.
Fields
| Name | Description |
|---|---|
|
The start time of the payment preference. |
|
The payment instruction preferred by the user. |
|
The status of the payment preference. |
Example
{
"forPaymentsAfter": "abc123",
"status": "abc123",
"paymentMethod": PaymentInstructionType
}Fields
| Name | Description |
|---|---|
|
The account number of the newly created account or the existing account to be re-used. |
|
Was a new account created. |
|
Was a new user created. |
|
The ID of the newly created or existing account user. |
Example
{
"isNewAccount": true,
"accountNumber": "abc123",
"isNewUser": true,
"userId": "abc123"
}PrepayBalanceSnapshotType
A snapshot of a prepay meter's credit and debt balance at a given point in time.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"creditInPence": 1,
"debtInPence": 1,
"emergencyCreditInPence": 1,
"asAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
The reason assigned to the Balance Transfer that originated the credit.If this endpoint is used to display prepay top-ups, then transfers with reason PREPAYBILLINGDUMPINFLIGHT_CREDIT must be excluded as these are transfers made during prepay billing after a credit removal and they are not top-ups. |
|
|
|
Deprecated The 'smartPrepayStatus' field is deprecated. |
|
Example
{
"id": "abc123",
"netAmount": 1,
"createdDate": "2020-01-01",
"smartPrepayStatus": "UTRN_REQUESTED",
"smartPrepayProcessStatus": "NOT_STARTED",
"utrn": "abc123",
"reason": "abc123"
}PrepayLedgersType
The ledgers associated to a prepayment meter. There are three types: a credit ledger for mirroring the meter's credit balance, a debt ledger for mirroring the meter's debt balance and payment ledger which is the inflight payments that we have not yet managed to resolve on the other two ledgers.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"creditLedger": SupplementaryLedgerType,
"debtLedger": SupplementaryLedgerType,
"paymentLedger": PrepayPaymentLedgerType
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PrepayPaymentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PrepayPaymentConnectionTypeEdge
A Relay edge containing a PrepayPaymentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PrepayPaymentType,
"cursor": "abc123"
}PrepayPaymentLedgerType
The in-flight payment ledger tracks the status of payments made to a prepay meter.
Fields
| Name | Description |
|---|---|
|
Transfers of credit from the account ledger to a smart prepay meter. |
|
The current final balance of the ledger in pence. |
|
Deprecated The 'ledgerId' field is deprecated. |
|
|
|
The display name of the ledger. |
|
The canonical name of the ledger. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Payments made to add credit to a smart prepay meter. |
Example
{
"id": "abc123",
"name": "abc123",
"ledgerType": "abc123",
"number": "abc123",
"currentBalance": 1,
"paymentAdequacy": PaymentAdequacyDetailsType,
"payments": [PrepayPaymentType],
"creditTransfers": [PrepayCreditTransferType]
}Fields
| Name | Description |
|---|---|
|
Amount of payment in pence |
|
|
|
|
|
The date this payment is scheduled to be debited |
|
|
|
Deprecated The 'smartPrepayStatus' field is deprecated. |
|
Example
{
"id": "abc123",
"amount": 1,
"paymentDate": "2020-01-01",
"smartPrepayStatus": "UTRN_REQUESTED",
"smartPrepayProcessStatus": "NOT_STARTED",
"utrn": "abc123",
"meter": Meter
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Whether the tariff is for exporting energy. |
|
|
|
|
|
|
|
|
|
Describes a particular tariff by combining the product code, number of rates, available from date and GSP code. |
|
Example
{
"id": "abc123",
"displayName": "abc123",
"fullName": "abc123",
"description": "abc123",
"productCode": "abc123",
"standingCharge": 1.0,
"preVatStandingCharge": 1.0,
"tariffCode": "abc123",
"isExport": true,
"unitRate": 1.0,
"preVatUnitRate": 1.0
}PriceForStream
Rate group prices for a product.
Fields
| Name | Description |
|---|---|
|
The characteristic mapping for the price. |
|
The price per unit. |
|
The scheme labels for the price. |
Example
{
"characteristicMapping": {"key": "value"},
"schemeLabels": {"key": "value"},
"price": "1.0"
}Fields
| Name | Description |
|---|---|
|
|
|
Unit that monetary amount relates to eg. 27 cents per kwh. |
Example
{
"amount": "1.0",
"unit": "KILOWATT_HOURS"
}PrintAttachmentType
Represents a print attachment
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Temporary URL at which the attachment is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). |
Example
{
"id": "abc123",
"filename": "abc123",
"s3Bucket": "abc123",
"s3Key": "abc123",
"temporaryUrl": "abc123"
}PrintBatchType
Represents print batch details
Fields
| Name | Description |
|---|---|
|
|
|
Messages in a print batch. |
|
The status of the print batch. |
Example
{
"id": "abc123",
"status": "OPEN",
"messages": PrintMessageTypeConnection
}Fields
| Name | Description |
|---|---|
|
|
|
The ID of the object |
|
Print message of the print event. |
|
Example
{
"id": "abc123",
"eventType": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z",
"message": PrintMessageType
}PrintMessageType
Represents a print communication.
Fields
| Name | Description |
|---|---|
|
|
|
Attachments of the message. |
|
Comms that are marked as high priority. |
|
The ID of the object |
|
Example
{
"id": "abc123",
"templateCode": "abc123",
"account": AccountType,
"attachments": [PrintAttachmentType],
"highPriority": true
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": PrintMessageTypeEdge,
"totalCount": 1,
"edgeCount": 1
}PrintMessageTypeEdge
A Relay edge containing a PrintMessageType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PrintMessageType,
"cursor": "abc123"
}ProductEligibilityType
Product eligibility verification result object.
Fields
| Name | Description |
|---|---|
|
List of product ineligibility reasons. |
|
Whether customer is eligible for product. |
Example
{
"isEligible": true,
"ineligibilityReasons": [ProductIneligibilityReasonDetails]
}ProductEnrolmentCandidateEligibilityType
Response type for eligibility checks run on a product enrolment candidate.
Fields
| Name | Description |
|---|---|
|
The candidate who has been evaluated for product enrolment. |
|
The result of the product eligibility check for the candidate. |
Example
{
"candidate": ProductEnrolmentCandidateType,
"eligibility": ProductEligibilityType
}ProductEnrolmentCandidateType
Represents a candidate for product enrolment, represented as a set of meter point mpxns.
Fields
| Name | Description |
|---|---|
|
The MPAN for the export electricity meter point. |
|
The MPRN for the gas meter point. |
|
The MPAN for the import electricity meter point. |
Example
{
"importMpan": "abc123",
"exportMpan": "abc123",
"gasMprn": "abc123"
}Fields
| Name | Description |
|---|---|
|
The name of the stage. |
|
The current status of the stage. |
|
The steps that are part of the enrolment stage. |
Example
{
"name": "abc123",
"status": "SKIPPED",
"steps": [ProductEnrolmentStepType]
}Fields
| Name | Description |
|---|---|
|
The name of the step. |
|
The current status of the step. |
|
The date time that the step was last updated. |
Example
{
"displayName": "abc123",
"status": "SKIPPED",
"updatedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
|
|
The electricity meter point associated with the enrolment. |
|
The gas meter point associated with the enrolment. |
|
|
|
The product associated with the enrolment. |
|
The stages that are part of the enrolment. |
|
Example
{
"id": "abc123",
"account": AccountType,
"status": "NOT_STARTED",
"product": EnergyProductType,
"electricityMeterPoint": ElectricityMeterPointType,
"gasMeterPoint": GasMeterPointType,
"stages": [ProductEnrolmentStageType]
}Fields
| Name | Description |
|---|---|
|
Ineligibility reason code. |
|
Customer ineligibility reason description. |
Example
{
"code": "abc123",
"description": "abc123"
}ProductRateOverrideConfigurationType
Configuration for Product Rate Override Configuration term.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
The indexation options for the product rate override configuration. |
|
Whether the term is variable. |
|
The schedules for the product rate override configuration. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true,
"indexationOptions": IndexationOptionsType,
"schedules": [ProductRateOverrideScheduleType]
}ProductRateOverrideItemType
Item for Product Rate Override Configuration term.
Fields
| Name | Description |
|---|---|
|
The price per unit for the product rate override item. |
|
The product code for the product rate override item. |
|
The rate band for the product rate override item. |
Example
{
"productCode": "abc123",
"rateBand": "abc123",
"pricePerUnit": "1.0"
}ProductRateOverrideScheduleType
Schedule for Product Rate Override Configuration term.
Fields
| Name | Description |
|---|---|
|
The effective from date for the product rate override schedule. |
|
The items for the product rate override schedule. |
Example
{
"items": [ProductRateOverrideItemType],
"effectiveFrom": "2020-01-01T00:00:00.000Z"
}ProductRateType
A single product rate.
Fields
| Name | Description |
|---|---|
|
The band category of the product rate. |
|
|
|
The gsp of the product rate. |
|
The payment_method of the product rate. |
|
|
|
|
|
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"bandCategory": "abc123",
"bandSubcategory": "abc123",
"pricePerUnit": "1.0",
"gsp": "abc123",
"paymentMethod": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Some tariffs expect customers to alter their usage patterns (e.g. EV tariffs) so will redistribute total consumption accordingly. |
|
|
|
|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"supplier": "abc123",
"tariffFullName": "abc123",
"tariffDisplayName": "abc123",
"tariffType": "abc123",
"tariffCode": "abc123",
"tariffEndsOn": "abc123",
"paymentMethod": "DIRECT_DEBIT",
"priceGuaranteedUntil": "abc123",
"exitFees": 1,
"exitFeesType": "abc123",
"additionals": "abc123",
"tariffComparisonRate": "1.0",
"estimatedAnnualCost": 1,
"annualStandingCharge": "1.0",
"standingCharge": "1.0",
"unitRateDay": "1.0",
"unitRateNight": "1.0",
"assumedAnnualConsumptionDay": 1,
"assumedAnnualConsumptionNight": 1,
"consumptionDistributionCoefficients": ConsumptionDistributionCoefficients
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"supplier": "abc123",
"tariffFullName": "abc123",
"tariffDisplayName": "abc123",
"tariffType": "abc123",
"tariffCode": "abc123",
"tariffEndsOn": "abc123",
"paymentMethod": "DIRECT_DEBIT",
"priceGuaranteedUntil": "abc123",
"exitFees": 1,
"exitFeesType": "abc123",
"additionals": "abc123",
"tariffComparisonRate": "1.0",
"estimatedAnnualCost": 1,
"annualStandingCharge": "1.0",
"standingCharge": "1.0",
"unitRate": "1.0",
"assumedAnnualConsumption": 1
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"supplier": "abc123",
"tariffFullName": "abc123",
"tariffDisplayName": "abc123",
"tariffType": "abc123",
"tariffCode": "abc123",
"tariffEndsOn": "abc123",
"paymentMethod": "DIRECT_DEBIT",
"priceGuaranteedUntil": "abc123",
"exitFees": 1,
"exitFeesType": "abc123",
"additionals": "abc123",
"tariffComparisonRate": "1.0",
"estimatedAnnualCost": 1,
"annualStandingCharge": "1.0",
"standingCharge": "1.0",
"unitRateDay": "1.0",
"unitRateNight": "1.0",
"unitRateOffPeak": "1.0",
"assumedAnnualConsumptionDay": 1,
"assumedAnnualConsumptionNight": 1,
"assumedAnnualConsumptionOffPeak": 1
}Fields
| Name | Description |
|---|---|
|
Index of carbon intensity ('low', 'high', etc.). |
|
|
Start of the half hourly carbon intensity projection period. |
|
Carbon intensity value. |
Example
{
"periodStart": "2020-01-01T00:00:00.000Z",
"value": 1.0,
"index": "VERY_LOW"
}Fields
| Name | Description |
|---|---|
|
List of projected regional carbon intensity values. |
Example
{
"projectedRegionalCarbonIntensity": [ProjectedRegionalCarbonIntensitiesType]
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"addressLine1": "abc123",
"addressLine2": "abc123",
"town": "abc123",
"county": "abc123",
"country": "abc123",
"postcode": "abc123"
}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. |
|
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. |
|
The 'street address' component. This value can (and often will) contain newline characters when appropriate. In some cases, data may appear in this field instead of the
below fields; e.g. a UK post town name may appear here
instead of in the If |
|
The 'street address' component, in a structured format. This field stores the same value as The exact structure of this value depends on the country of the address, which is not necessarily the same as the country this Kraken is configured to serve. For addresses outside of the countries listed below, this field will be left blank.
|
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"
}Fields
| Name | Description |
|---|---|
|
The matched property. |
|
A score representing the degree of confidence for a match. |
Example
{
"score": "1.0",
"property": PropertyType
}PropertyType
Represents a property. Conceptually, it collects supply points under an address.
Fields
| Name | Description |
|---|---|
|
The address of the property, formatted into a single string. |
|
Timeslots for which the property has the possibility to book a smart-meter installation. |
|
Coordinates for the property, useful for displaying the property on a map. |
|
Retrieve the details of electricity meter-points for a property. |
|
The embedded network this property belongs to, if any. |
|
Retrieve the details of gas meter-points for a property. |
|
|
|
|
|
Indicates if the property meets smart meter install preconditions. |
|
An optional label for the property. |
|
Measurements at a property |
|
Time periods during which the property is associated with an account. Useful to display information about house-moves, as performing a move out of a property will set the end date for the occupancy period. |
|
|
|
Property rich address. |
|
Retrieve any smartmeter devices connected to the property. |
|
List of address lines. |
|
Likelihood that a smart meter at the given postcode and address will get a stable network connection. |
Example
{
"id": "abc123",
"postcode": "abc123",
"address": "abc123",
"richAddress": PropertyRichAddressType,
"splitAddress": ["abc123"],
"label": "abc123",
"occupancyPeriods": [OccupancyPeriodType],
"coordinates": CoordinatesType,
"embeddedNetwork": EmbeddedNetworkType,
"measurements": MeasurementConnection,
"smartDeviceNetworks": [SmartMeterDeviceNetworkType],
"isChangeOfTenancyOngoing": true,
"isSmets2InstallationAllowed": true,
"electricityMeterPoints": [ElectricityMeterPointType],
"gasMeterPoints": [GasMeterPointType],
"wanCoverage": "HIGH",
"availableSmets2InstallationTimeslots": [Smets2InstallationTimeslotType]
}Fields
| Name | Description |
|---|---|
|
OAuth 2.0 URI for the provider. |
Example
{
"oauthUri": "abc123"
}ProviderVirtualKeyDetailsType
Details of a public key that can be added to devices for end-to-end authentication or encryption.
E.g. for Tesla the user visits a URL and the name can be used to show what the key is called. https://github.com/teslamotors/vehicle-command#distributing-your-public-key
Fields
| Name | Description |
|---|---|
|
Friendly human-readable name for the virtual key. |
|
URI for the virtual key. |
Example
{
"virtualKeyName": "abc123",
"virtualKeyUri": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ProvisionalTransactionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}ProvisionalTransactionConnectionTypeEdge
A Relay edge containing a ProvisionalTransactionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ProvisionalTransactionType,
"cursor": "abc123"
}ProvisionalTransactionType
A provisional transaction represents some debit or credit to or from a customer's account which we cannot yet finalise for some reason, but which is still useful to keep a note of, and display to the customer. Provisional transactions are purely to give guidance in the absence of finalised information. We therefore only return provisional transactions that have not been finalised. When a transaction is finalised, it is available through the transactions field.
Fields
| Name | Description |
|---|---|
|
The amount in pence for this provisional transaction. It will be negative for charges, positive for credits. |
|
The date at which the charge should be applied to the account. |
|
|
|
A user readable string that indicates what this transaction relates to. |
Example
{
"id": "abc123",
"title": "abc123",
"amount": 1,
"date": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
The AWS IoT endpoint hostname to connect to AWS APIs & services. |
|
The certificate which the controller will present to AWS IoT in order to validate its provisioning claim. It will contain the public key of the controller, and be signed by KF. |
|
This is the private key which will be used by the controller to make the provisioning claim, encrypted with the public key of the controller. |
Example
{
"certificate": "abc123",
"encryptedPrivateKey": "abc123",
"awsIotHostname": "abc123"
}Fields
| Name | Description |
|---|---|
|
The cost for the charge added during a charging session. |
|
The end time of a charging session. |
|
The energy added during a charging session. |
|
Location of the charging session. |
|
URL of the operator image. |
|
The start time of a charging session. |
|
The change in state of charge during a charging session. The value will be between 0 and 100, if not null. |
|
The final state of charge after a charging session. The value will be between 0 and 100, if not null. |
PublishTransactionalMessagingExternalTrigger
Publish an externally defined transactional messaging trigger.
The possible errors that can be raised are:
- KT-CT-4178: No account found with given account number.
- KT-CT-5421: Account user not found.
- KT-CT-9901: Invalid trigger type code.
- KT-CT-9905: Top-level context fields are missing.
- KT-CT-9906: Template variables do not match the defined schema.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The trigger that has been published. |
Example
{
"possibleErrors": [PossibleErrorType],
"trigger": Trigger
}PublishTransactionalMessagingTrigger
Publish a trigger within the transactional messaging service.
The possible errors that can be raised are:
- KT-CT-9901: Invalid trigger type code.
- KT-CT-9902: Invalid trigger type params.
- KT-CT-9903: Trigger type cannot be published externally.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The trigger that has been published. |
Example
{
"possibleErrors": [PossibleErrorType],
"trigger": Trigger
}PushNotificationBindingType
Represents a pairing of a single app installation to an account user.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"messages": SMSMessageType,
"user": AccountUserType,
"token": "abc123",
"application": NotifiableApplicationType,
"registeredAt": "2020-01-01T00:00:00.000Z",
"expiresAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The complexity of the query. |
Example
{
"complexityValue": 1
}QuoteAccountOnProducts
The possible errors that can be raised are:
- KT-CT-4616: Unable to create a quote.
- KT-GB-4614: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The generated quote. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": QuoteRequest
}Example
{
"addressLine1": "abc123",
"addressLine2": "abc123",
"addressLine3": "abc123"
}QuoteCampaignOffer
Quote a given account on a campaign offer.
Fields
| Name | Description |
|---|---|
|
Example
{
"quoteCode": "abc123"
}Fields
| Name | Description |
|---|---|
|
The cost for quoting this product. |
|
The date and time when the quote component was created. |
|
Identifier of the Quote. |
|
Identifier of the Product Component. |
|
The input data used for quoting this product component. |
Example
{
"identifier": "abc123",
"productComponentIdentifier": "abc123",
"costs": {"key": "value"},
"quotingParamsInputData": {"key": "value"},
"createdAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The generated quote. |
Example
{
"quoteRequest": QuoteRequest
}QuoteNewMeterPointsOnBespokeProducts
The possible errors that can be raised are:
- KT-CT-4616: Unable to create a quote.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The generated quote. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": QuoteRequest
}Fields
| Name | Description |
|---|---|
|
The code of the created quote. |
|
|
|
List of electricity supply points and their quoted products. |
|
List of gas supply points and their quoted products. |
|
List of terms and conditions for this quote. |
Example
{
"electricitySupplyPoints": [ElectricitySupplyPoint],
"gasSupplyPoints": [GasSupplyPoint],
"createdAt": "2020-01-01T00:00:00.000Z",
"termsAndConditions": [TermsAndConditions],
"code": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
List of electricity supply points and their quoted products. |
|
List of gas supply points and their quoted products. |
|
List of terms and conditions for this quote. |
Example
{
"electricitySupplyPoints": [ElectricitySupplyPoint],
"gasSupplyPoints": [GasSupplyPoint],
"createdAt": "2020-01-01T00:00:00.000Z",
"termsAndConditions": [TermsAndConditions]
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Deprecated. Use the consumptionEstimates query instead. Deprecated The 'consumption_estimates' field is deprecated. |
|
In kWh |
|
In kWh |
|
In kWh |
|
|
|
In kWh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The meter type for the quote. |
|
|
|
|
|
|
|
|
|
|
|
A list of the products that have been quoted for the usage provided at the time the quote was created. |
|
Example
{
"code": "abc123",
"postcode": "abc123",
"gspGroupId": "abc123",
"includesElectricity": true,
"includesGas": true,
"isBusiness": true,
"meterType": "NO_METER",
"mpan": "abc123",
"paymentMethod": "DIRECTDEBIT",
"elecAnnualConsumptionStandard": 1,
"elecAnnualConsumptionDay": 1,
"elecAnnualConsumptionNight": 1,
"elecEstimate": true,
"gasAnnualConsumption": 1,
"gasEstimate": true,
"partnerProductId": 1,
"latitude": 1.0,
"longitude": 1.0,
"address": QuoteAddressType,
"consumptionEstimates": ConsumptionEstimates,
"quotedProducts": [QuotedProductType],
"termsAndConditions": TermsAndConditionsType,
"mprn": "abc123"
}Fields
| Name | Description |
|---|---|
|
The date and time when the quote was created. |
|
The Actor who created the Quote. |
|
Identifier of the Quote. |
|
The product offering identifier this Quote is related to. |
|
Quote components of this quote. |
Example
{
"identifier": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"productOfferingIdentifier": "abc123",
"quoteComponents": [QuoteComponentType],
"createdBy": ActorType
}Fields
| Name | Description |
|---|---|
|
A list of dates allowable to start supply of the quoted product. |
|
Estimated cost in pence of the product over a year based on the quoted usage. |
|
Estimated saving in pence vs the 'Big 6' of the product over a year based on the quoted usage. |
|
The amount of co2 saved per year when this product is chosen. |
|
|
|
|
|
Electricity tariff information label (TIL) provides standardised information between suppliers about a tariff. |
|
|
|
Gas tariff information label (TIL) provides standardised information between suppliers about a tariff. |
|
|
|
|
|
Whether or not this is a variable product. |
|
Estimated cost in pence of the product per month based on the quoted usage. |
|
|
|
|
|
|
|
The number of trees it would take to offset the amount of co2 that is saved per year when this product is chosen. |
Example
{
"id": "abc123",
"name": "abc123",
"description": "abc123",
"product": EnergyProductType,
"recommended": true,
"monthlyAmount": 1,
"annualAmount": 1,
"annualSaving": 1,
"elecTariffCode": "abc123",
"gasTariffCode": "abc123",
"electricityTariffInformationLabel": TariffInformationLabelType,
"gasTariffInformationLabel": TariffInformationLabelStandard,
"isVariable": true,
"allowedSupplyStartDates": ["2020-01-01"],
"co2SavingInKg": 1,
"treesSaving": 1,
"includesCarbonOffsetting": true
}Fields
| Name | Description |
|---|---|
|
The MPAN of the meter point. |
|
The type of meter point. |
Example
{
"mpan": "abc123",
"type": "abc123"
}RateGroupEligibilityType
Represents a rate group eligibility term of in a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true
}RateGroupPrices
Rate group prices for a product.
Fields
| Name | Description |
|---|---|
|
The prices for the rate group. |
|
The rate group code. |
Example
{
"rateGroup": "abc123",
"prices": PriceForStream
}ReadInventory
Triggers an asynchronous request through the DCC adapter to read the Smart Metering Inventory.
Returns a request reference that can be used to track the status of the request.
The possible errors that can be raised are:
- KT-GB-4021: Invalid MPxN.
- KT-GB-4024: The provided device ID does not match any devices known by Kraken.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The reference for the associated request in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}Fields
| Name | Description |
|---|---|
|
The exclusive end of this reading's interval. |
|
The inclusive start of this reading's interval. |
|
The quality of this reading if applicable. |
|
The source of this reading if applicable. |
|
This reading's units. |
|
The recorded value for this reading. |
Example
{
"value": "1.0",
"units": "abc123",
"intervalStart": "2020-01-01T00:00:00.000Z",
"intervalEnd": "2020-01-01T00:00:00.000Z",
"source": "abc123",
"quality": "abc123"
}Fields
| Name | Description |
|---|---|
|
Reading consent granularity value. |
Example
{
"granularityValue": "abc123"
}ReadingsConnection
Pagination for utility usage readings.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ReadingsEdge,
"totalCount": 1,
"edgeCount": 1
}ReadingsEdge
A Relay edge containing a Readings and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Reading,
"cursor": "abc123"
}ReauthenticateDevice
Re-authenticate a device. The authentication details provided must be for the same device as was previously authenticated.
The possible errors that can be raised are:
- KT-CT-4313: Could not find KrakenFlex device.
- KT-CT-4314: Unable to get provider details.
- KT-CT-4315: Unable to re-authenticate device.
- KT-CT-4363: No capable devices found.
- KT-CT-4364: Multiple devices found.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}RebootHeatingController
Reboot a heating controller.
The possible errors that can be raised are:
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The unique ID associated with this reboot operation. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}RecordDepositAgreementAccepted
Record the customer's acceptance of a deposit agreement.
The possible errors that can be raised are:
- KT-CT-4177: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"isRecorded": true
}Fields
| Name | Description |
|---|---|
|
The action to perform when the button is pressed. |
|
The button style. |
|
Unique identifier of the object. |
|
Title text of the button. |
|
The name of the object's type. |
|
Colour style of button eg. filled, outlined, text_only. |
Example
{
"buttonStyle": "PRIMARY",
"title": "abc123",
"buttonAction": ActionType,
"id": "abc123",
"typename": "abc123",
"variant": "FILLED"
}RedeemLoyaltyPointsForAccountCredit
Redeem Loyalty Points as account credit.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-9201: No Loyalty Point ledger found for the user.
- KT-CT-9202: Loyalty Points adapter not configured.
- KT-CT-9203: No ledger entries for the ledger.
- KT-CT-9205: Insufficient Loyalty Points.
- KT-CT-9206: Indivisible points.
- KT-CT-9204: Negative or zero points set.
- KT-CT-9208: Invalid posted at datetime.
- KT-CT-9209: Negative Loyalty Points balance.
- KT-CT-9210: Unhandled Loyalty Points exception.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The number of loyalty points that were redeemed. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"pointsRedeemed": 1
}RedeemReferralClaimCode
The possible errors that can be raised are:
- KT-CT-6723: Unauthorized.
- KT-CT-6724: Referral claim code not found.
- KT-CT-6725: Referral claim code redeeming error.
- KT-CT-6726: Referral claim code has already been redeemed.
- KT-CT-6727: Referral claim code is not available.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether or not the request was successful. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}ReferralClaimCodeType
Referral claim code is a way of claiming promotional benefit coming from the partner-reward referral schemes.
Fields
| Name | Description |
|---|---|
|
Account referral associated with the claim code. |
|
Datetime when claim code was generated. |
|
Id of claim code instance. |
|
Referral scheme claim code belongs to. |
|
Value of claim code. |
Example
{
"id": 1,
"value": "abc123",
"referralScheme": ReferralSchemeType,
"accountReferral": ReferralType,
"createdAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total payment amount given to the referring account in the smallest unit. of the client's currency. If you filter the referrals by |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": ReferralConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1,
"referringUserTotalPaymentAmount": 1
}ReferralConnectionTypeEdge
A Relay edge containing a ReferralConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ReferralType,
"cursor": "abc123"
}ReferralSchemeType
A referral scheme is a way for one account to earn a reward for referring another. This is achieved by the referred account using a url (provided by the referring account) to sign up.
Fields
| Name | Description |
|---|---|
|
Whether the current account is eligible to be referred under this scheme. |
|
The unique code for the scheme. |
|
The reward amount received by the referrer and the referee combined. |
|
True if the the scheme has limit of uses, and if the usage is at capacity. |
|
The number of loyalty points to be awarded to the referrer in addition to the reward amount. |
|
Max number of times this referral code can be credited to a given account. |
|
A referral url for display purposes. |
|
A fully qualified url give people to create accounts referred by this scheme. |
|
The reward amount received by the referred party. |
|
The family name of the person making the referral. Deprecated The 'referrerFamilyName' field is deprecated. |
|
The given name of the person making the referral. |
|
The reward amount received by the referrer. |
|
Scheme type of the referral scheme. |
Example
{
"referralUrl": "abc123",
"referralDisplayUrl": "abc123",
"referrerRewardAmount": 1,
"referredRewardAmount": 1,
"combinedRewardAmount": 1,
"loyaltyPointsBonus": 1,
"canBeReferred": true,
"code": "abc123",
"referrerGivenName": "abc123",
"referrerFamilyName": "abc123",
"schemeType": "abc123",
"maxRecurrence": 1,
"isUsageAtCapacity": true
}Fields
| Name | Description |
|---|---|
|
A business scheme type |
|
A domestic scheme type |
|
A friends and family scheme type Deprecated The 'friendsAndFamily' field is deprecated. |
Example
{
"domestic": ReferralSchemeType,
"business": ReferralSchemeType,
"friendsAndFamily": ReferralSchemeType
}ReferralType
Details of an account referral
Fields
| Name | Description |
|---|---|
|
The referral code. |
|
The payment amount in the smallest unit of the clients currency received by the referrer and the referee combined. |
|
|
|
The date when the payment was made. |
|
The status of the payment. |
|
The date the referred user joined. |
|
The name of the referred user. |
|
Payment amount given to the referred account in the smallest unit of the client's currency. |
|
Payment amount given to the referring account in the clients fractional currency unit. |
|
The type of reward scheme. |
Example
{
"id": "abc123",
"paymentDate": "2020-01-01",
"schemeType": "REFERRAL_REWARD",
"code": "abc123",
"referredUserName": "abc123",
"paymentStatus": "abc123",
"referredUserJoinDate": "2020-01-01T00:00:00.000Z",
"referredUserPaymentAmount": 1,
"referringUserPaymentAmount": 1,
"combinedPaymentAmount": 1
}RefreshQuote
The possible errors that can be raised are:
- KT-GB-4612: Unable to refresh quote - quote not found.
- KT-GB-4613: Error generating quote.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"quote": QuoteType
}RefreshToken
An opaque token that can be used to renew a Kraken Token.
Fields
| Name | Description |
|---|---|
|
The datetime when the token will expire. |
|
|
|
Example
{
"key": "abc123",
"expiryDt": "2020-01-01T00:00:00.000Z",
"isValid": true
}Refund
A refund to the customer from the energy supplier.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the account the transaction belongs to. |
|
Gross amount including tax (when payable). Refer to the Deprecated The 'amount' field is deprecated. |
|
The net, tax and gross amounts for the transaction. Note: for payments and repayments, only the net amount is returned. |
|
The customer's resulting balance after this transaction has been applied, in the smallest unit of currency. |
|
The unique identifier for the most recent billing document linked with the transaction.Note: a transaction may be linked with multiple documents, but this field will only return the identifier for the most recent billing document. |
|
The date time when the transaction is created. |
|
Returns True if the transaction is linked with a statement. |
|
|
|
Deprecated. Deprecated The 'isAccountCharge' field is deprecated. |
|
Deprecated. Deprecated The 'isAccountPayment' field is deprecated. |
|
Deprecated. Deprecated The 'isCredit' field is deprecated. |
|
Whether the statement this transaction is on has been held. A held statement is not sent to a customer automatically, but is instead marked for manual attention by operations staff. Returns False if a statement is not linked with the transaction. |
|
Whether this transaction has been issued on any billing document.Note: Look for the most recently issued transaction instead of looking through all transactions as some accounts may have initial transactions that were not issued.This will return False if the transaction is not associated with any billing documents. |
|
|
|
Returns the note field value for the transaction, which contains additional info. |
|
|
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Example
{
"id": "abc123",
"postedDate": "2020-01-01",
"createdAt": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123",
"amount": 1,
"amounts": TransactionAmountType,
"balanceCarriedForward": 1,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "abc123",
"billingDocumentIdentifier": "abc123",
"statementId": "abc123",
"isReversed": true,
"hasStatement": true,
"note": "abc123",
"reasonCode": "abc123"
}RefundPayment
The possible errors that can be raised are:
- KT-CT-3924: Unauthorized.
- KT-CT-3928: Idempotency key used for another repayment request.
- KT-CT-3929: The payment is not in a refundable state.
- KT-CT-3933: Refund amount greater than payment amount.
- KT-CT-3937: Payment not eligible for refund.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The repayment for the requested refund. |
Example
{
"possibleErrors": [PossibleErrorType],
"repayment": AccountRepaymentType
}Fields
| Name | Description |
|---|---|
|
The amount of money requested. |
|
The payment which is being refunded. |
|
Internal code for the reason the refund is being requested. |
|
The ID of the refund request. |
|
The current status of the refund request. |
Example
{
"requestId": "abc123",
"amount": 1,
"payment": AccountPaymentType,
"reasonCode": "abc123",
"status": "REQUESTED"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": RefundRequestConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}RefundRequestConnectionTypeEdge
A Relay edge containing a RefundRequestConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": RefundPaymentRequestType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The requested refund amount which was submitted in the repayment. |
Example
{
"requestedAmountToReturn": 1
}RegenerateSecretKey
Regenerate the user's API key.
Fields
| Name | Description |
|---|---|
|
The generated key value, which is only ever available once (here). |
|
The currently authenticated user. |
Example
{
"key": "abc123",
"viewer": AccountUserType
}RegisterOpportunityFlowStatusEvent
The possible errors that can be raised are:
- KT-CT-8906: Opportunity not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType]
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"pushNotificationBinding": PushNotificationBindingType
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Example
{
"identifier": "abc123",
"name": "abc123",
"value": "abc123",
"digits": 1,
"isQuarantined": true
}RegisterSmartDevice
A request sent to notify Kraken of a new device, which will be prenotified to the adapter.
Fields
| Name | Description |
|---|---|
|
The reference for the associated request in Kraken. |
Example
{
"requestReference": "abc123"
}Fields
| Name | Description |
|---|---|
|
The name of the team responsible for completing the reminder. |
|
The username of the user responsible for completing the reminder. |
|
Reminder content. |
|
The date and time the account reminder was created. |
|
When the reminder is due. |
|
The unique ID of the reminder. |
|
If the reminder is managed by Kraken. |
|
The reminder type name. |
|
Reopen ink conversation. |
Example
{
"id": 1,
"reminderTypeName": "abc123",
"isKrakenManaged": true,
"content": "abc123",
"dueAt": "2020-01-01T00:00:00.000Z",
"assigneeUsername": "abc123",
"assigneeTeamName": "abc123",
"reopenInkConversation": true,
"createdAt": "2020-01-01T00:00:00.000Z"
}RemoveCampaignFromAccount
The possible errors that can be raised are:
- KT-CT-7424: Failed to remove campaign from account.
- KT-CT-7426: The account is not part of the given campaign.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the campaign was successfully removed from the account. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"campaignRemoved": true
}RemoveCampaignItems
The possible errors that can be raised are:
- KT-CT-11501: Voice campaign not found.
- KT-CT-11502: Cannot remove items from multiple campaigns at once.
- KT-CT-11505: Voice campaign item not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"campaignItems": [VoiceCampaignItemType]
}RemoveConsumerDevice
Remove a consumer device from the CHF/HAN. Currently limited to only CAD devices.
The possible errors that can be raised are:
- KT-GB-4012: Unable to find the CAD device.
- KT-GB-4032: Error sending the request to remove the device.
- KT-GB-4013: Received invalid device type to remove other than CAD.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The reference of the remove consumer device request in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}RemoveItemsFromRiskList
Remove existing items from risk list.
The possible errors that can be raised are:
- KT-CT-12106: Risk list item removal failed.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
List of successfully removed risk identifiers. |
Example
{
"possibleErrors": [PossibleErrorType],
"riskIdentifiers": [RiskListItemType]
}RemoveSensor
Remove a sensor from a heating controller device.
The possible errors that can be raised are:
- KT-CT-4309: Error trying to remove sensor from heat pump controller.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Unique ID associated with removing a sensor from a heat pump controller. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}RenewAgreementForMeterPoint
Renew agreement for a given meter point.
The possible errors that can be raised are:
- KT-GB-4112: Unable to renew agreements for meter point at this time. Please try again later.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"electricityAgreement": RestrictedElectricityAgreement,
"gasAgreement": RestrictedGasAgreement
}RenewAgreements
Renew agreements for an account.
This mutation calls tariff renewal use-case both for electricity and gas agreements.
This mutation renews agreements from midnight the day it is invoked in the case of flexible tariffs and fixed tariffs ending in more than 90 days. For fixed tariffs that end in less than 90 days, it creates follow on agreements that start when the fixed agreements end (or minimum of when they end in the case of misaligned agreements).
The possible errors that can be raised are:
- KT-GB-4125: Invalid data.
- KT-GB-4111: Unable to renew agreements for tariff renewal.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}RenewAgreementsForAccount
Renew agreements provided for an account.
The possible errors that can be raised are:
- KT-GB-4113: At least one list of agreements to renew is required.
- KT-GB-4126: Electricity and gas agreement input is invalid.
- KT-GB-4114: Unable to renew agreements.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Example
{
"slug": "abc123",
"product": EnergyProductType
}Fields
| Name | Description |
|---|---|
|
The repayment intervention outcome. |
|
The repayment intervention reason. |
Example
{
"outcome": "abc123",
"reason": "abc123"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": RepaymentRequestConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}RepaymentRequestConnectionTypeEdge
A Relay edge containing a RepaymentRequestConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": RepaymentRequestType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The amount of money requested. |
|
The payment instruction, if any, associated with the repayment request. |
|
The method by which the money will be transferred to the customer. |
|
Classifier code for repayment reason. |
|
The ID of the repayment request. |
|
The current status of the repayment request. |
Example
{
"requestId": "abc123",
"amount": 1,
"reasonCode": "abc123",
"method": "BANK_TRANSFER",
"instruction": PaymentInstructionType,
"status": "REQUESTED"
}ReplaceAgreement
Replace the given agreement with the given product.
TODO: Move this outside of plugin as it is applicable to the wider domain.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"account": AccountInterface
}Fields
| Name | Description |
|---|---|
|
The reference for the associated request in Kraken. |
Example
{
"requestReference": "abc123"
}ReportRemovedMeterDetails
The possible errors that can be raised are:
- KT-GB-4213: Application not found.
- KT-GB-4231: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"result": ReportRemovedMeterDetailsOutput
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"appointment": SiteworksAppointmentType,
"electricityMeterPoint": SiteworksBookingElectricityMeterPointType,
"gasMeterPoint": SiteworksBookingGasMeterPointType
}RequestConsumptionData
The possible errors that can be raised are:
- KT-GB-4033: No electricity device found matching device ID.
- KT-GB-4034: Error requesting consumption data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The reference for the associated request in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}RequestDoubleOptIn
Request a double opt in for a consent.
This mutation will create a consent with a value of PENDING and publish a double opt-in requested transactional messaging trigger.
The possible errors that can be raised are:
- KT-CT-9019: Invalid input.
- KT-CT-9018: Account not found.
- KT-CT-1111: Unauthorized.
- KT-CT-9016: Consent management not enabled.
- KT-CT-9017: Consent type not found.
- KT-CT-9023: Consent already accepted.
- KT-CT-1199: Too many requests.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The consent that was created or updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"consent": ConsentType
}Fields
| Name | Description |
|---|---|
|
The email that requested a password reset email. |
Example
{
"email": "abc123"
}RequestPrintedBill
Request an issued bill to be printed and (re)posted to billing address of the account.
The possible errors that can be raised are:
- KT-CT-3824: Unauthorized.
- KT-CT-9705: The billing document has not been issued.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether the request was successful. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}RequestProvisioningClaimCertificate
The possible errors that can be raised are:
- KT-CT-4332: Invalid data.
- KT-CT-4304: Error in preprovisioning step for Octopus Heat Pump.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The certificate and private key required to create a provisioning claim. |
Example
{
"possibleErrors": [PossibleErrorType],
"provisioningClaimBundle": ProvisioningClaimBundle
}Fields
| Name | Description |
|---|---|
|
Whether the account can request a refund. |
|
The reason why a refund cannot be requested. |
Example
{
"canRequestRefund": true,
"reason": "abc123"
}RequestRepaymentOutputType
Output for creating a repayment request.
Fields
| Name | Description |
|---|---|
|
The ID of the repayment request. |
|
The current status of the repayment request. |
Example
{
"requestId": "abc123",
"status": "REQUESTED"
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"quote": QuoteType
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"errors": [SerializerFieldErrorsType],
"clientMutationId": "abc123"
}Fields
| Name | Description |
|---|---|
|
A list of codes of which password validation the new password failed against if applicable.
One of:
- Deprecated The 'failureCodes' field is deprecated. |
|
A list of messages of which password validations the new password failed against if applicable. Deprecated The 'failureReasons' field is deprecated. |
|
True if the password update was successful, false otherwise. Deprecated The 'passwordUpdated' field is deprecated. |
|
The ID of the user whose password was changed. |
Example
{
"userId": "abc123",
"passwordUpdated": true,
"failureReasons": ["abc123"],
"failureCodes": ["abc123"]
}Fields
| Name | Description |
|---|---|
|
The ID of the object |
|
|
|
|
|
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"id": "abc123",
"tariffCode": "abc123"
}Fields
| Name | Description |
|---|---|
|
The ID of the object |
|
|
|
|
|
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"id": "abc123",
"tariffCode": "abc123"
}ResumeDeviceControl
Resume control of a device after having been away from home.
This is so that the device can be charged again according to the set preferences.
The possible errors that can be raised are:
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4359: Unable to resume device control.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}RevokeAgreement
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-1501: Agreement not found.
- KT-CT-1502: Billed agreements cannot be revoked.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account responsible for the revoked agreement. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}RewardType
A reward is based on a scheme that an account has applied for in order to be
eligible for a discount. Examples can include signup, promo, or partner codes that
were applied to an account.
Fields
| Name | Description |
|---|---|
|
The referral code. |
|
|
|
The date when the payment was made. |
|
The status of the reward payment. |
|
Reward amount given to the account in the smallest unit of the clients currency. |
|
The type of reward scheme. |
Example
{
"id": "abc123",
"paymentDate": "2020-01-01",
"schemeType": "REFERRAL_REWARD",
"code": "abc123",
"rewardAmount": 1,
"paymentStatus": "Pending"
}RichAddressType
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.
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. |
|
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. |
|
The 'street address' component. This value can (and often will) contain newline characters when appropriate. In some cases, data may appear in this field instead of the
below fields; e.g. a UK post town name may appear here
instead of in the If |
|
The 'street address' component, in a structured format. This field stores the same value as The exact structure of this value depends on the country of the address, which is not necessarily the same as the country this Kraken is configured to serve. For addresses outside of the countries listed below, this field will be left blank.
|
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"
}RiskListItemType
Represents the result of importing/removing risk identifiers into the risk list with detailed information.
Fields
| Name | Description |
|---|---|
|
The unique identifier of the edited risk identifier. |
Example
{
"riskIdentifierId": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the SEG installation is valid according to MCS. |
Example
{
"isValid": true
}Fields
| Name | Description |
|---|---|
|
|
|
The ID of the object |
|
SMS message of the SMS event. |
|
Example
{
"id": "abc123",
"eventType": "abc123",
"occurredAt": "2020-01-01T00:00:00.000Z",
"message": SMSMessageType
}SMSMessageType
Represents a SMS communication.
Fields
| Name | Description |
|---|---|
|
|
|
Attachments of the message. |
|
|
|
SMS recipient. |
|
SMS sender. |
|
|
|
SMS body. |
Example
{
"id": "abc123",
"sentAt": "2020-01-01T00:00:00.000Z",
"account": AccountType,
"attachments": [AttachmentType],
"sender": "abc123",
"recipient": "abc123",
"textBody": "abc123"
}Fields
| Name | Description |
|---|---|
|
Dispatch notice time of event (day before, within 1 day, etc). |
|
The start datetime of the joined event. |
|
Did the account opt-in to the event. |
|
The streak point the account had during the event. |
Example
{
"eventStartDate": "2020-01-01T00:00:00.000Z",
"isOptedIntoEvent": true,
"dispatchNotice": "DAY_AHEAD",
"streakPoints": 1
}Fields
| Name | Description |
|---|---|
|
The average payment amongst all customers per event. |
|
How much we thought the customer was going to use over the event period. |
|
The saved amount of CO2 in grams for the event. |
|
How much the customer actually used over the event period. |
|
The end datetime of the joined event. |
|
The energy saved in kWh for the event. |
|
The event ID of the joined event. |
|
The status of the event. |
|
Percent rank amongst all customers that reduced consumption. |
|
The total consumption reduction in percentage for the event. |
|
The datetime of when the results were set. |
|
Updated results status. |
|
The amount of OctoPoints the account has been awarded for their participation in the event. |
|
The start datetime of the joined event. |
|
The outcome of the account's participation of the event. Deprecated The 'status' field is deprecated. |
Example
{
"eventId": 1,
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"rewardGivenInOctoPoints": 1,
"energySavedInKwh": 1.0,
"status": "CALCULATING",
"eventStatus": "UPCOMING",
"resultsStatus": "CALCULATING",
"co2SavedInGrams": 1.0,
"percentageSaved": 1.0,
"netReductionPctRank": 1.0,
"avgCustomerRemunerationPounds": 1.0,
"baselineConsumptionDeltaKwh": 1.0,
"consumptionDeltaKwh": 1.0,
"resultsSetAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Example
{
"number": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the account is eligible to join the campaign. |
|
Meterpoints eligible for signup to Saving Sessions. |
|
The event streak history of the account. |
|
Whether the account joined the campaign. |
|
Whether the account is a business account. |
|
Whether the account is a tester account for the campaign. |
|
The events that the account has joined. |
|
The meter point signed up to Saving Sessions. |
Example
{
"canJoinCampaign": true,
"hasJoinedCampaign": true,
"eligibleMeterPoints": [EligibleMetersPointsType],
"signedUpMeterPoint": EligibleMetersPointsType,
"isBusinessAccount": true,
"isTesterAccount": true,
"joinedEvents": [SavingSessionsAccountJoinedEventsType],
"eventStreak": [SavingSessionsAccountEventStreakType]
}Fields
| Name | Description |
|---|---|
|
The event code. |
|
Whether this this a test event. |
|
The end of the event. |
|
The event ID. |
|
The batch ID for the opt-in invitations. |
|
The number of OctoPoints an account will earn per kWh of energy reduced, if successful. |
|
The start of the event. |
|
Status of the event. |
|
List of the target gsp group id's for the event, if any. |
|
The total number of participants who joined the event. |
Example
{
"id": 1,
"code": "abc123",
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"status": "UPCOMING",
"totalParticipants": 1,
"rewardPerKwhInOctoPoints": 1,
"targetGsp": [TargetGspType],
"optInInvitationBatchId": "500c164d-38c7-4f74-9ac6-be210197e9e4",
"devEvent": true
}Fields
| Name | Description |
|---|---|
|
The equivalent total CO2 saved in a phrase. |
|
Optional additional context for the CO2e statement. |
|
The equivalent total energy saved in a phrase. |
|
The amount of energy saved across all Saving Sessions, in kWh. |
|
The last datetime the stats were updated. |
Example
{
"energySavedInKwh": 1,
"energySavedEquivalentInWords": "abc123",
"co2SavedEquivalentInWords": "abc123",
"co2SavedEquivalentTooltip": "abc123",
"lastUpdatedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The last datetime the prize draw information was updated. |
|
A description of the the latest spot prize winner. |
|
A description of the spot prize for the next Saving Session. |
|
Whether there is prize draw information to show for the next Saving Session. |
Example
{
"showPrizeDraw": true,
"nextSessionPrizeDescription": "abc123",
"latestAwardedPrizeDescription": "abc123",
"lastUpdatedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The baseline consumption in MWh. |
|
Number of events the region has participated in. |
|
The grid supply point id for the region (eg. '_A'). |
|
The grid supply point group name of the region. |
|
The metered consumption in MWh. |
|
The consumption reduction in MWh. |
|
The consumption reduction in percentage. |
Example
{
"gspGroupId": "abc123",
"gspGroupName": "abc123",
"eventCount": 1,
"baselineMwh": 1.0,
"reductionMwh": 1.0,
"meteredMwh": 1.0,
"reductionPct": 1.0
}Fields
| Name | Description |
|---|---|
|
Info related to a specific account. The possible errors that can be raised are:
|
|
The total number of events. |
|
Saving Sessions events, ordered by start datetime. |
|
Combined statistics from all of the Savings Sessions so far. |
|
Prize draw information. |
|
Regional results from all of the Savings Sessions so far. |
Example
{
"account": SavingSessionsAccountType,
"events": [SavingSessionsEventType],
"eventCount": 1,
"nationalAggregatedStats": SavingSessionsNationalAggregatedStatsType,
"prizeDrawInformation": SavingSessionsPrizeDrawInformationType,
"regionalResults": [SavingSessionsRegionalResultType]
}Fields
| Name | Description |
|---|---|
|
A bitmask of the days this program is active for. |
|
A list of the Setting objects which make up this schedule. |
Example
{
"days": "abc123",
"settings": [Setting]
}ScheduleQuoteFollowUp
Schedule a quote follow up message to the provided recipient.
The possible errors that can be raised are:
- KT-CT-4619: Quote with given code not found.
- KT-CT-4632: Invalid recipient information.
- KT-CT-4633: Mutation not enabled in this environment.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether the message was scheduled successfully. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}Fields
| Name | Description |
|---|---|
|
Whether the scheduled transaction is a 'charge' or a 'credit'. |
|
Additional data that is consumed and associated with the scheduled transaction. |
|
Optional short note about the scheduled transaction for customer display. |
|
The gross amount of the scheduled transaction. |
|
Optional short note about the scheduled transaction for internal use. |
|
The ledger the scheduled transaction is for. |
|
Any extra data that is associated with scheduled transaction. |
|
The net amount of the scheduled transaction. |
|
The datetime after which the scheduled transaction can be added to the ledger. |
|
The reason why the scheduled transaction is added to the account. |
|
The tax amount of the scheduled transaction. |
|
The tax rate of the scheduled transaction. |
Example
{
"ledgerNumber": "abc123",
"action": "abc123",
"grossAmount": 1,
"netAmount": 1,
"salesTaxAmount": 1,
"salesTaxRate": "1.0",
"reason": "abc123",
"ancillaryData": {"key": "value"},
"metadata": {"key": "value"},
"internalNote": "abc123",
"displayNote": "abc123",
"postedAfter": "2020-01-01T00:00:00.000Z"
}ScreenActionType
An action which calls another backend screen via its screen id.
Fields
| Name | Description |
|---|---|
|
Whether to allow returning to the original caller screen. |
|
Unique identifier of the object. |
|
Map of the parameters (key-value pairs) to pass to the next backend screen. |
|
The ID of the screen to navigate to. |
|
The name of the action object's type. |
|
The name of the object's type. |
Example
{
"id": "abc123",
"typename": "abc123",
"typeName": "abc123",
"screenId": "abc123",
"params": BackendScreenParam,
"allowBack": true
}SectionType
A section containing a list of cards or carousel items
Fields
| Name | Description |
|---|---|
|
The content of the section. |
|
Unique identifier of the object. |
|
The order of the section. |
|
The name of the object's type. |
Example
{
"id": "abc123",
"typename": "abc123",
"content": SectionContent,
"order": 1
}SelectChargePointMake
Options for selecting a charge point's make from a list of options.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectChargePointMakeForSmartFlexOnboarding
Complete the select charge point make step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
The make of the charge point, e.g. myenergi. |
|
A unique identifier for this list item. |
Example
{
"id": "abc123",
"chargePointMake": ChargePointVariantType
}SelectChargePointVariant
Options for selecting a charge point's variant from a list of options.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectChargePointVariantForSmartFlexOnboarding
Complete the select charge point variant step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
The model variant of the charge point, e.g. Zappi. |
|
A unique identifier for this list item. |
Example
{
"id": "abc123",
"chargePointVariant": ChargePointVariantType
}SelectDeviceType
A type where the user must select the type of device to onboard.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectDeviceTypeForSmartFlexOnboarding
Select the type of device to start the onboarding process.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
A unique identifier for this list item. |
|
The device type, e.g. Electric Vehicle. |
Example
{
"id": "abc123",
"label": "abc123"
}SelectInverterMake
Options for selecting an inverter's make from a list of options.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectInverterMakeForSmartFlexOnboarding
Complete the select inverter make step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
A unique identifier for this list item. |
|
The make (manufacturer) of the inverter. |
Example
{
"id": "abc123",
"inverterMake": InverterVariantType
}SelectProducts
Mark chosen quoted products for quoted supply points on quote request as selected.
The possible errors that can be raised are:
- KT-CT-4619: Quote with given code not found.
- KT-CT-4634: Quoted product with given id not found.
- KT-CT-4626: No product selected for the given quote code.
- KT-CT-4635: Missing a quoted product for at least one quoted supply point on the quote request.
- KT-CT-4636: Quoted product not linked to a product.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether we successfully marked the chosen quoted products as selected. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}SelectUserVehicle
Options for selecting a user's vehicle from a list of options.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectUserVehicleForSmartFlexOnboarding
Complete the select user vehicle step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
A unique identifier for this list item. |
|
The selected electric vehicle when multiple vehicles were available. Deprecated The 'userVehicle' field is deprecated. |
|
A vehicle associated with the user's OEM account. |
Example
{
"id": "abc123",
"userVehicle": ElectricVehicleType,
"vehicle": VehicleInformationType
}SelectVehicleMake
Options for selecting a vehicle's make from a list of options.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectVehicleMakeForSmartFlexOnboarding
Complete the select vehicle make step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
A unique identifier for this list item. |
|
The make of the electric vehicle make, e.g. Tesla. |
Example
{
"id": "abc123",
"vehicleMake": ElectricVehicleType
}SelectVehicleVariant
Options for selecting a vehicle's variant from a list of options.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The options the user can select. |
|
The ID of the option that has been selected, if any. |
Example
{
"id": "abc123",
"options": SmartFlexListItemInterface,
"selectedOptionId": "abc123"
}SelectVehicleVariantForSmartFlexOnboarding
Complete the select vehicle variant step.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
A unique identifier for this list item. |
|
The model variant of the electric vehicle, e.g. Model Y. |
Example
{
"id": "abc123",
"vehicleVariant": ElectricVehicleType
}Fields
| Name | Description |
|---|---|
|
The reference of the Decommission Request in Kraken. |
Example
{
"requestReference": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
The live chat. |
|
The ID of the Ink Live Chat message that was created. |
Example
{
"liveChat": InkLiveChat,
"messageRelayId": "abc123",
"clientMutationId": "abc123"
}SendLossObjectionForChangeOfSupplier
The possible errors that can be raised are:
- KT-CT-4185: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Returns true if objection was successfully sent. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}SendQuoteSummary
Trigger the sending of a quote summary to the provided recipient.
The possible errors that can be raised are:
- KT-CT-4619: Quote with given code not found.
- KT-CT-4178: No account found with given account number.
- KT-CT-4632: Invalid recipient information.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether the triggering of the quote summary was successful. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": true
}SendVerificationEmail
The possible errors that can be raised are:
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
If the verification email was sent. |
Example
{
"possibleErrors": [PossibleErrorType],
"verificationStatus": true
}Fields
| Name | Description |
|---|---|
|
Whether or not a sensor is currently online. |
|
Time at which the status was retrieved. |
Example
{
"online": true,
"retrievedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The code name for a sensor. |
|
The connectivity/online status of a sensor. |
|
The telemetry data of a sensor. |
Example
{
"code": "abc123",
"connectivity": SensorConnectivity,
"telemetry": SensorTelemetry
}Fields
| Name | Description |
|---|---|
|
Percentage humidity recorded by the sensor. |
|
Time at which the telemetry was retrieved. |
|
Signal strength of a sensor measured in dBm (Received Signal Strength Indicator). |
|
Deprecated. Deprecated The 'rssiPercentage' field is deprecated. |
|
Temperature recorded by a sensor in celsius. |
|
Voltage recorded by a sensor. |
Example
{
"temperatureInCelsius": 1.0,
"humidityPercentage": 1,
"rssi": 1,
"rssiPercentage": 1,
"voltage": 1.0,
"retrievedAt": "2020-01-01T00:00:00.000Z"
}SensorUpdateTransactionId
A mapping of sensor codes to transaction ids as returned from a successful KF request.
Fields
| Name | Description |
|---|---|
|
The code of the sensor which was updated. |
|
A UUID representing the update operation for this sensor. |
Example
{
"sensorCode": "abc123",
"transactionId": "abc123"
}Example
{
"message": "abc123",
"code": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"field": "abc123",
"errors": [ErrorTypeUnion]
}SetBatteryChargingPreferences
Allow customers to set/update their battery's charging preferences.
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4353: An error occurred while trying to update your charging preferences.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The battery device updated, with the ID of the device in KrakenFlex. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": BatteryDeviceType
}SetClimateControlState
The possible errors that can be raised are:
- KT-CT-4337: Unable to set climate control state.
- KT-CT-4301: Unable to find device for given account.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The customer specific heat pump device details. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"heatPumpDevice": HeatPumpDeviceType
}SetHotWaterState
The possible errors that can be raised are:
- KT-CT-4336: Unable to set hot water state.
- KT-CT-4301: Unable to find device for given account.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The customer specific heat pump device details. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"heatPumpDevice": HeatPumpDeviceType
}SetLoyaltyPointsUser
Set the Loyalty Points user for the account.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-9210: Unhandled Loyalty Points exception.
- KT-CT-9214: Couldn't assign user loyalty points role.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
ID of the new Loyalty Points user. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"newLoyaltyPointsUserId": "abc123"
}SetOpportunityOutcome
The possible errors that can be raised are:
- KT-CT-8906: Opportunity not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Success message for now. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": "abc123"
}SetPaymentPreference
Choose how automatic payments will be collected.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-3967: Payment method is not valid.
- KT-CT-3968: Preference cannot be set this soon.
- KT-CT-3969: Preferences must change on a specific day of the week for weekly schedules.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType]
}SetReadingConsentGranularity
Update the reading consent granularity for a meter point.
This mutation allows the user to update the reading consent granularity for a specific meter point. Note that if the consent granularity is already set to the current value, no changes will be made, and the mutation will return a success response.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether the reading consent granularity was successfully submitted. |
Example
{
"possibleErrors": [PossibleErrorType],
"readingConsentGranularitySubmitted": true
}SetRoomTemperature
The possible errors that can be raised are:
- KT-CT-4329: Invalid data.
- KT-CT-4346: Unable to set the room temperature.
- KT-CT-7223: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The customer specific heat pump device details. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"heatPumpDevice": HeatPumpDeviceType
}SetUpDirectDebitInstruction
The possible errors that can be raised are:
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-3940: Invalid data.
- KT-CT-5415: Account user not found.
- KT-CT-11103: Business not found.
- KT-CT-3971: Instruction owners are not valid.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentInstruction": DirectDebitInstructionType
}SetVehicleChargingPreferences
Allow customers to set/update their vehicle's charging preferences.
The possible errors that can be raised are:
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4321: Serializer validation error.
- KT-CT-4353: An error occurred while trying to update your charging preferences.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}SetZoneMode
Turn a heating controller zone ON/OFF, set it to AUTO or BOOST it.
The possible errors that can be raised are:
- KT-CT-4333: Invalid data.
- KT-CT-4306: Error setting mode for heat pump controller zone.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Unique ID associated with a zone's mode operation. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}SetZonePrimarySensor
Set the primary sensor for a zone.
The primary sensor is the one which controls the heating for that zone. Other sensors merely provide data, at least currently.
The possible errors that can be raised are:
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The unique ID associated with this operation. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}SetZoneSchedules
Set a heating controller zone's schedule(s).
The possible errors that can be raised are:
- KT-CT-4334: Invalid data.
- KT-CT-4308: Error setting schedule(s) for heat pump controller zone.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Unique ID associated with adding schedule(s) for a zone. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whether the setting turns the zone on or off, or changes its temperature. |
|
Desired zone temperature (for zones which support setpoints). |
|
The time this setting becomes active. |
|
Whether the setting leaves the zone "ON" or "OFF". |
Example
{
"startTime": "00:00:00.000Z",
"action": "abc123",
"setpointInCelsius": 1.0,
"zoneState": "ON"
}ShareGoodsQuote
The possible errors that can be raised are:
- KT-CT-4122: Invalid email.
- KT-CT-8203: Received an invalid quote code.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Goods quote shared. |
Example
{
"possibleErrors": [PossibleErrorType],
"share": GoodsQuoteShare
}Fields
| Name | Description |
|---|---|
|
Denotes whether or not this voucher value is currently available. |
|
The voucher value. |
Example
{
"value": 1,
"availability": true
}Fields
| Name | Description |
|---|---|
|
The voucher code. |
Example
{
"code": "abc123"
}Fields
| Name | Description |
|---|---|
|
The current power in kW being consumed by the property from the solar panels, battery and grid. If power is being exported to the grid, that is offset againstconsumption. If power is being used to charge the battery, that doesn't count towards consumption; that'll only count as consumed when it is later used to power the property (this avoids double-counting it). |
|
The current power being exported from the property to the grid in kW. This will be 0 if no export is occurring, or otherwise a positive value. |
Example
{
"consumptionInKw": "1.0",
"exportInKw": "1.0"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": SiteworksAppointmentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}SiteworksAppointmentConnectionTypeEdge
A Relay edge containing a SiteworksAppointmentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": SiteworksAppointmentType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"appointmentDate": "2020-01-01",
"startTime": "00:00:00.000Z",
"endTime": "00:00:00.000Z",
"agentReference": "abc123",
"siteId": "abc123",
"slotId": "abc123",
"calculationId": "abc123",
"promiseId": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
The status of the fetch siteworks appointment operation. |
|
Example
{
"calculationId": "abc123",
"slots": [SiteworksAppointmentSlotType],
"expectedJobDurationMinutes": 1,
"fetchStatus": "PENDING"
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Override Field to add additional attributes and extend description with possible_errors |
|
Electricity meter points associated with this Siteworks appointment. |
|
Gas meter points associated with this Siteworks appointment. |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"activeAppointment": ActiveAppointmentType,
"account": AccountType,
"property": PropertyType,
"electricityMeterPoints": [SiteworksBookingElectricityMeterPointType],
"gasMeterPoints": [SiteworksBookingGasMeterPointType]
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": SiteworksBookingAccountConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}SiteworksBookingAccountConnectionTypeEdge
A Relay edge containing a SiteworksBookingAccountConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": SiteworksBookingAccountType,
"cursor": "abc123"
}SiteworksBookingAccountType
An object holding information about an account and its associated users, properties and meter points, used for administering siteworks bookings.
Fields
| Name | Description |
|---|---|
|
|
|
Active campaigns for the account. |
|
Name for this account. If one exists, the billing name of the portfolio will prepend this. |
|
The brand of the account. |
|
Data about whether or not an account can modify their payments. |
|
Retrieve all market supply agreements under this account. Note that when |
|
|
|
Properties linked to the account now and in the future. |
|
Siteworks requests associated to an account. |
|
The interest of an account in procuring smart meters. |
|
The current status of the account. |
|
Example
{
"number": "abc123",
"status": "PENDING",
"users": AccountUserType,
"billingName": "abc123",
"accountType": "abc123",
"properties": [SiteworksBookingPropertyType],
"marketSupplyAgreements": AgreementConnection,
"canModifyPayments": CanModifyPaymentsType,
"siteworksRequests": [SiteworksRequestType],
"activeCampaigns": [SiteworksCampaignType],
"smets2Interest": "PRIORITY",
"brand": "abc123"
}SiteworksBookingElectricityMeterPointType
This type holds information about an electricity meter point that is used by partner organisations to book siteworks.
Fields
| Name | Description |
|---|---|
|
A list of agents responsible for management of the meterpoint. |
|
|
|
|
|
The distribution network the grid supply point falls under. |
|
|
|
Whether this meter point has a meter which is due a reading. |
|
|
|
The latest supply period of the meterpoint. |
|
|
|
|
|
Standard settlement configuration |
|
|
|
Example
{
"id": "abc123",
"supplyEndDate": "2020-01-01",
"mpan": "abc123",
"ssc": "abc123",
"energisationStatus": "abc123",
"dccServiceFlag": "abc123",
"status": "abc123",
"isOnSupply": true,
"latestSupplyPeriod": SupplyPeriodType,
"isMeterReadingDue": true,
"meters": [ElectricityMeterType],
"gspGroupId": "abc123",
"agentContracts": [ElectricityAgentContractType]
}SiteworksBookingGasMeterPointType
This type holds information about a gas meter point that is used by partner organisations to book siteworks.
Fields
| Name | Description |
|---|---|
|
A list of agents responsible for management of the meterpoint. |
|
|
|
Whether this meter point has a meter which is due a reading. |
|
|
|
The latest supply period of the meterpoint. |
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"supplyEndDate": "2020-01-01",
"mprn": "abc123",
"status": "abc123",
"isOnSupply": true,
"latestSupplyPeriod": SupplyPeriodType,
"isMeterReadingDue": true,
"meters": [GasMeterType],
"agentContracts": [GasAgentContractType]
}SiteworksBookingPropertyType
This type is used by partner organisations to retrieve information about a property and its meter points that is used to book siteworks.
Fields
| Name | Description |
|---|---|
|
Retrieve the details of an electricity meter-point. |
|
Retrieve the details of a gas meter-point. |
|
|
|
|
|
Indicates if the property meets smart meter install preconditions. |
|
|
|
Retrieve any smartmeter devices connected to the property. |
|
List of address lines. |
Example
{
"id": "abc123",
"postcode": "abc123",
"smartDeviceNetworks": [SmartMeterDeviceNetworkType],
"isChangeOfTenancyOngoing": true,
"isSmets2InstallationAllowed": true,
"electricityMeterPoints": [SiteworksBookingElectricityMeterPointType],
"gasMeterPoints": [SiteworksBookingGasMeterPointType],
"splitAddress": ["abc123"]
}Example
{
"name": "abc123",
"slug": "abc123"
}Fields
| Name | Description |
|---|---|
|
Siteworks appointments associated to a request. |
Example
{
"appointments": [ActiveAppointmentType]
}SkipSSDPayment
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-GB-4137: Could not cancel SSD payment.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The amount of the next scheduled payment for the account. |
|
The date of the next scheduled payment for the account. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The amount of the skipped payment. |
|
The date of the payment that was skipped. |
Example
{
"possibleErrors": [PossibleErrorType],
"skippedPaymentAmount": 1,
"skippedPaymentDate": "2020-01-01",
"nextPaymentAmount": 1,
"nextPaymentDate": "2020-01-01"
}Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
Make of the battery. |
|
Model of the battery. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"make": "abc123",
"model": "abc123"
}SmartFlexChargePoint
Information about a charge point that has been registered with Kraken Flex.
Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
This contains more detail about the variant of the charge point model. |
|
The user's preferences for charging using this charge point. |
|
History of charging sessions for a SmartFlex device. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
The make of the charge point, e.g. myenergi. |
|
The model of the charge point, e.g. Zappi. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
|
This contains more detail about the variant of the vehicle model. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"chargingSessions": DeviceChargingSessionConnection,
"make": "abc123",
"model": "abc123",
"vehicleVariant": ElectricVehicleModelType,
"chargePointVariant": ChargePointVariantModelType,
"chargingPreferences": SmartFlexVehicleChargingPreferences
}SmartFlexChargePointStatus
The current status of a registered charge point.
Fields
| Name | Description |
|---|---|
|
The current status of the device. |
|
The current state of this SmartFlex device state machine. |
|
Whether control of the device is currently disabled. |
|
Information about the limits for the SoC. |
|
The reason for the most recent failed test dispatch (if any). |
Example
{
"current": "ONBOARDING",
"isSuspended": true,
"currentState": "AUTHENTICATION_PENDING",
"stateOfChargeLimit": StateOfChargeLimit,
"testDispatchFailureReason": "NONE"
}Fields
| Name | Description |
|---|---|
|
Possible cause of the charging error. |
Example
{
"cause": "SOC_LIMIT_REACHED"
}Fields
| Name | Description |
|---|---|
|
The cost for the charge added during a charging session. |
|
The charging session dispatch. |
|
The end time of a charging session. |
|
The energy added during a charging session. |
|
Charging problem(s) encountered during the session due to an error or truncation. |
|
The start time of a charging session. |
|
The change in state of charge during a charging session. The value will be between 0 and 100, if not null. |
|
The final state of charge after a charging session. The value will be between 0 and 100, if not null. |
|
The target type for a user's preferences. |
|
The type of charge, i.e. |
Example
{
"start": "2020-01-01T00:00:00.000Z",
"end": "2020-01-01T00:00:00.000Z",
"stateOfChargeChange": "1.0",
"stateOfChargeFinal": "1.0",
"energyAdded": Energy,
"cost": Money,
"type": "SMART",
"targetType": "ABSOLUTE_STATE_OF_CHARGE",
"dispatches": [SmartFlexDispatch],
"problems": [SmartFlexChargingProblem]
}Fields
| Name | Description |
|---|---|
|
The state of charge (in percent) that was possible, given the truncation. |
|
The state of charge (in percent) that could have been achieved, if not for truncation of the charging session. |
|
The cause for the truncation of a charging session. |
Example
{
"truncationCause": "DISCONNECTED",
"originalAchievableStateOfCharge": "1.0",
"achievableStateOfCharge": "1.0"
}SmartFlexDevice
Information about a device that has been registered for Smart Flex.
Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface
}SmartFlexDeviceAlert
Information about an alert relevant to a device registered for Smart Flex.
Fields
| Name | Description |
|---|---|
|
A device alert message. |
|
When a device alert message is published. |
Example
{
"message": "abc123",
"publishedAt": "2020-01-01T00:00:00.000Z"
}SmartFlexDevicePreferenceSchedule
A schedule entry for device preferences specifying target values for a specific day and time.
For information about valid value ranges, time constraints, and step increments,
query the device's preferenceSettings field which provides bounds and validation rules.
Fields
| Name | Description |
|---|---|
|
Day of week schedule applies to. |
|
Maximum value for the schedule. Usage depends on the targetType - e.g., maximum charge for EVs. For valid bounds and step increments, see the device's |
|
Minimum value for the schedule when applicable. Usage depends on the targetType - e.g., minimum temperature for heat pumps. May be null for device types that don't require a lower bound. For valid bounds and step increments, see the device's |
|
Time of day the preference applies. |
|
Upper limit value for the schedule when applicable.Usage depends on the targetType - e.g., charge level to never be exceeded for V2G EVs.May be null for device types that don't require an upper bound. |
Example
{
"dayOfWeek": "MONDAY",
"time": "00:00:00.000Z",
"min": 1.0,
"max": 1.0,
"upperLimit": 1.0
}Fields
| Name | Description |
|---|---|
|
The device's preference mode. |
|
The schedules of the device's preference. |
|
The target type of the preference. |
|
The unit of the preference schedules' min and max values. |
Example
{
"targetType": "ABSOLUTE_STATE_OF_CHARGE",
"unit": "CELSIUS",
"mode": "CHARGE",
"schedules": [SmartFlexDevicePreferenceSchedule]
}SmartFlexDeviceStatus
Information about the current status of a device registered for Smart Flex.
Fields
| Name | Description |
|---|---|
|
The current status of the device. |
|
The current state of this SmartFlex device state machine. |
|
Whether control of the device is currently disabled. |
Example
{
"current": "ONBOARDING",
"isSuspended": true,
"currentState": "AUTHENTICATION_PENDING"
}Fields
| Name | Description |
|---|---|
|
Import supply point ID. |
|
SmartFlex device ID. |
Example
{
"importSupplyPointId": "abc123",
"smartFlexDeviceId": "abc123"
}Fields
| Name | Description |
|---|---|
|
The end time of the dispatch. |
|
The energy added in kWh of the dispatch. |
|
The start time of the dispatch. |
|
The type of charge. |
Example
{
"start": "2020-01-01T00:00:00.000Z",
"end": "2020-01-01T00:00:00.000Z",
"type": "SMART",
"energyAddedKwh": "1.0"
}Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
The make of the heat pump, e.g. Daikin. |
|
The model of the heat pump, e.g. EDLA04E2V3. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The maximum power consumed by the heat pump in kilowatts. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"make": "abc123",
"model": "abc123",
"powerInKw": NormalizedDecimal
}Fields
| Name | Description |
|---|---|
|
The data related to the latest reported activity of the heat pump. |
|
The current status of the device. |
|
The current state of this SmartFlex device state machine. |
|
The data related to the latest reported temperature of different zones. |
|
Whether control of the device is currently disabled. |
|
The data related to the latest reported mode of the heat pump. |
|
The data related to the target temperature of the heat pump. |
Example
{
"current": "ONBOARDING",
"isSuspended": true,
"currentState": "AUTHENTICATION_PENDING",
"mode": FunctionalMode,
"currentTemperatures": [ZoneTemperature],
"targetTemperature": TargetTemperature,
"activity": Activity
}SmartFlexInverter
Information about an inverter that has been registered with KrakenFlex.
Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
The make of the inverter. |
|
The model of the inverter. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
|
Telemetry data for the inverter. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"make": "abc123",
"model": "abc123",
"telemetry": SmartFlexInverterTelemetry
}SmartFlexInverterTelemetry
Telemetry data for a registered inverter.
Fields
| Name | Description |
|---|---|
|
Information about the battery. |
|
Information about the grid. |
|
Information about the inverter. |
|
Information about the site. |
|
Information about the solar panels. |
Example
{
"inverter": InverterTelemetry,
"battery": BatteryTelemetry,
"solar": SolarTelemetry,
"grid": GridTelemetry,
"site": SiteTelemetry
}SmartFlexOnboardingDeviceRegistration
A type that returns True if the device(s) were successfully registered.
Fields
| Name | Description |
|---|---|
|
Returns true if the device(s) were successfully registered. |
|
A unique identifier for this onboarding step. |
Example
{
"id": "abc123",
"deviceRegistered": true
}Fields
| Name | Description |
|---|---|
|
A Backend Screen that renders the SmartFlex onboarding wizard. |
|
The completed steps for all onboarding wizards that are currently in progress. Note: - The last step is the most recent one. - If an onboarding journey is completed, it will not be included in this list. |
|
The next step of the SmartFlex onboarding wizard. Returns |
|
The onboarding wizard's selected device type to be onboarded. |
|
The onboarding wizard's display name extracted from the wizard's selected device attributes. |
|
A unique identifier for this SmartFlex onboarding wizard. |
|
Determines whether the wizard's onboarding journey can be resumed. |
Example
{
"id": "abc123",
"resumable": SmartFlexResumable,
"deviceType": "BATTERIES",
"displayName": "abc123",
"backendScreen": BackendScreenType,
"currentStep": SmartFlexOnboardingStepInterface,
"completedSteps": SmartFlexOnboardingStepInterface
}Fields
| Name | Description |
|---|---|
|
A boolean to determine whether the wizard's onboarding journey can be resumed. |
|
Reasons why a wizard cannot be resumed. |
Example
{
"isResumable": true,
"resumableReasons": ["abc123"]
}SmartFlexStorageHeaters
Information about storage heaters that have been registered with Kraken Flex.
Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface
}SmartFlexVehicle
Information about a vehicle that has been registered with Kraken Flex.
Fields
| Name | Description |
|---|---|
|
Active alert message(s) for a device, showing the latest first. |
|
This contains more detail about the variant of the charge point model. |
|
The user's preferences for charging this vehicle. Deprecated The 'chargingPreferences' field is deprecated. |
|
History of charging sessions for a SmartFlex device. |
|
The type of device. |
|
A UUID that identifies this device registration. Re-registering this device will result in a different ID. |
|
The third-party integration device ID. |
|
The make of the vehicle, e.g. Tesla. |
|
The model of the vehicle, e.g. Model 3. |
|
The user-friendly name for the device. |
|
The current onboarding wizard for a device. |
|
The preference setting for this device. |
|
The device's preference details. |
|
The id of the property linked to the device. |
|
The third-party that enables control of this device. |
|
Information about the current status of this device. |
|
This contains more detail about the variant of the vehicle model. |
Example
{
"id": "abc123",
"name": "abc123",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "abc123",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "abc123",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"chargingSessions": DeviceChargingSessionConnection,
"make": "abc123",
"model": "abc123",
"vehicleVariant": ElectricVehicleModelType,
"chargePointVariant": ChargePointVariantModelType,
"chargingPreferences": SmartFlexVehicleChargingPreferences
}SmartFlexVehicleChargingPreferences
The user's preferences for charging, e.g. target SoC (State of Charge).
Fields
| Name | Description |
|---|---|
|
The maximum SoC (percentage). |
|
The minimum SoC (percentage). |
|
The target SoC to achieve on a weekday (percentage). |
|
The time at which the target SoC should be achieved on a weekday. |
|
The target SoC to achieve on a weekend (percentage). |
|
The time at which the target SoC should be achieved on a weekend. |
Example
{
"weekdayTargetTime": "00:00:00.000Z",
"weekdayTargetSoc": 1,
"weekendTargetTime": "00:00:00.000Z",
"weekendTargetSoc": 1,
"minimumSoc": 1,
"maximumSoc": 1
}SmartFlexVehicleStatus
The current status of a registered vehicle.
Fields
| Name | Description |
|---|---|
|
The current status of the device. |
|
The current state of this SmartFlex device state machine. |
|
Whether control of the device is currently disabled. |
|
Information about the limits for the SoC. |
|
The reason for the most recent failed test dispatch (if any). |
Example
{
"current": "ONBOARDING",
"isSuspended": true,
"currentState": "AUTHENTICATION_PENDING",
"stateOfChargeLimit": StateOfChargeLimit,
"testDispatchFailureReason": "NONE"
}Fields
| Name | Description |
|---|---|
|
The reading frequency for the smart meter. |
|
Has the user given consent that their readings can be used for further analysis? |
|
The datetime when the user gave consent that their readings can be used for further analysis. |
Example
{
"readingFrequency": "DAILY",
"readingsAnalysisConsentProvided": true,
"readingsAnalysisConsentUpdatedDatetime": "2020-01-01T00:00:00.000Z"
}SmartMeterDeviceNetworkType
This is the network through which a set of SMETS2 devices communicates.
Fields
| Name | Description |
|---|---|
|
|
|
A list of devices attached to one network. |
Example
{
"id": "abc123",
"smartDevices": [SmartMeterDeviceType]
}SmartMeterDeviceType
A smart meter device.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The payment mode (e.g. credit or prepayment) that the device is currently operating in. |
|
|
|
|
|
|
|
The rate, in pence per week, that debt is being recovered from this device. |
Example
{
"id": "abc123",
"importElectricityMeter": ElectricityMeterType,
"exportElectricityMeter": ElectricityMeterType,
"gasMeter": GasMeterType,
"deviceNetwork": SmartMeterDeviceNetworkType,
"serialNumber": "abc123",
"deviceId": "abc123",
"type": "ESME",
"status": "PENDING",
"manufacturer": "abc123",
"model": "abc123",
"firmwareVersion": "abc123",
"paymentMode": "PREPAY",
"weeklyDebtRecoveryRateInPence": 1
}Fields
| Name | Description |
|---|---|
|
Total energy consumed by the meter measured in Wh. |
|
Energy consumption in Wh between the read_at and the next reading. |
|
Energy cost excluding VAT for the consumption delta in pence. |
|
Energy cost including VAT for the consumption delta in pence. |
|
Energy being demanded by the meter measured in W. |
|
Total energy exported by the meter measured in Wh. |
|
The start_at time of the telemetry data. E.g if querying in 30 minute intervals the reading may have been taken anywhere between 00:00:00 and 00:29:59 and represents the maximum reading taken in the time period. |
Example
{
"readAt": "2020-01-01T00:00:00.000Z",
"consumption": "1.0",
"export": "1.0",
"demand": "1.0",
"consumptionDelta": "1.0",
"costDelta": "1.0",
"costDeltaWithTax": "1.0"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"account": AccountType,
"meterPoint": ElectricityMeterPointType,
"product": EnergyProductType
}SmartTariffComparisonType
Consumption cost for different smart tariffs.
Fields
| Name | Description |
|---|---|
|
The datetime the consumption readings end. |
|
The datetime the consumption readings start. |
|
Costs comparisons for available smart tariffs. Note: if product type is not supported or product doesn't have unit rates - it will not be included in response. |
|
Total cost for a period. |
|
Total cost with tax for a period. |
Example
{
"currentCost": 1.0,
"currentCostWithTax": 1.0,
"costComparisons": [TariffComparisonType],
"consumptionReadingsStartAt": "2020-01-01T00:00:00.000Z",
"consumptionReadingsEndAt": "2020-01-01T00:00:00.000Z"
}SmartTariffOnboardingType
The smart tariff onboarding process. Only relevant for Kraken instances that support half hourly tariffs. Returns null if not applicable.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"latestStatus": "STARTED",
"latestTermsStatus": "TERMS_ACCEPTANCE_REQUIRED",
"smartTariffCode": "AGILE_OCTOPUS",
"lastUpdated": "abc123"
}Smets2InstallationTimeslotType
A timeslot for which a property can make an appointment for installation of a smart-meter.
Example
{
"appointmentDate": "2020-01-01",
"startTime": "00:00:00.000Z",
"endTime": "00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
List of caught Constantines for this set. |
|
List of Constantines not yet caught for this set. |
|
The name of the set of Constantines. |
|
Is this Constantine set completed (all constantines in set caught). |
|
The amount of prizes entries completing the set is worth. |
|
The slug for this kind of Constantine set. |
Example
{
"displayName": "abc123",
"slug": "abc123",
"isComplete": true,
"constantinesCaught": [CaughtConstantine],
"constantinesRemaining": [ConstantineType],
"prizeEntries": 1
}Fields
| Name | Description |
|---|---|
|
The date of the data. |
|
The numerical hour of the data. |
|
The estimated solar generation in kWh. |
Example
{
"date": "2020-01-01",
"hour": 1,
"value": 1.0
}Fields
| Name | Description |
|---|---|
|
A list of solar generation estimates. |
Example
{
"solarGenerationEstimates": [SolarGenerationEstimateType]
}Fields
| Name | Description |
|---|---|
|
The current power being generated by the solar panels in kW. This will be null if there are no solar panels, 0 if there are solar panels but they are not generating, or a positive value if they are generating. |
Example
{
"powerInKw": "1.0"
}SpecialCircumstanceRecordType
Any special circumstances that the user has notified us about, which may entitle them to some specialist services.
Fields
| Name | Description |
|---|---|
|
The date and time the special circumstance record was created. |
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"summary": "abc123",
"internalCode": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"gasPSRCode": "abc123",
"electricityPSRCode": "abc123"
}SpecialCircumstancesType
Information about the special circumstances that relate to a user.
Fields
| Name | Description |
|---|---|
|
Whether the user has consented for their data to be given to the appropriate industry or regulatory bodies. We typically only ask for this once, so this field can be used to decide whether to ask the user for their initial consent. |
|
A list of special circumstance records, both temporary and permanent. |
Example
{
"isSharingConsentGiven": true,
"records": [SpecialCircumstanceRecordUnion]
}SpinWheelOfFortune
The possible errors that can be raised are:
- KT-CT-7011: Terms must be accepted.
- KT-CT-7023: Unauthorized.
- KT-CT-7010: The account does not have any available submissions.
- KT-CT-7012: Wheel of Fortune submission error.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The result of the Wheel of Fortune spin. This field requires the |
Example
{
"possibleErrors": [PossibleErrorType],
"spinResult": WheelOfFortuneSpinResultType
}Fields
| Name | Description |
|---|---|
|
Absolute change in the percentage of daily consumption occurring in peak hours. e.g. if 14% pre and 12% post then this will relate to a 2% reduction in peak usage. |
|
True if peak consumption percentage has decreased after the clock change, False otherwise. |
|
Average percentage of total daily consumption that occurs during peak (4-7 PM) in the latest 14 days post clock change. |
|
Average percentage of total daily consumption that occurs during peak (4-7 PM) in the 14 days prior to spring clock change. |
|
Relative change in the percentage of daily consumption occurring in peak hours. e.g. if 14% pre and 12% post then this will relate to a 14.3% reduction in peak usage. |
Example
{
"priorPeakPercentage": 1.0,
"postPeakPercentage": 1.0,
"absoluteReductionPercentage": 1.0,
"relativeReductionPercentage": 1.0,
"isReduction": true
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Whether the tariff is for exporting energy. |
|
|
|
|
|
|
|
|
|
Describes a particular tariff by combining the product code, number of rates, available from date and GSP code. |
|
|
|
Is EPG applied to the unit rate. |
Example
{
"id": "abc123",
"displayName": "abc123",
"fullName": "abc123",
"description": "abc123",
"productCode": "abc123",
"standingCharge": 1.0,
"preVatStandingCharge": 1.0,
"tariffCode": "abc123",
"isExport": true,
"unitRate": 1.0,
"unitRateEpgApplied": true,
"preVatUnitRate": 1.0
}StartCustomerVerification
Start the customer verification using the provided verification method.
The possible errors that can be raised are:
- KT-CT-1701: Brand does not exist.
- KT-CT-4194: Verification type not supported yet.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The newly created verification process. |
Example
{
"possibleErrors": [PossibleErrorType],
"verificationProcess": VerificationProcess
}StartExportOnboardingProcess
Onboarding for export tariffs.
This mutation kicks off the export onboarding for electricity.
The possible errors that can be raised are:
- KT-GB-4103: Unable to start export onboarding process.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The product enrolment process created. |
Example
{
"possibleErrors": [PossibleErrorType],
"onboardingProcess": SmartOnboardingProcessType,
"productEnrolment": ProductEnrolmentType
}StartSmartFlexOnboarding
Create a wizard for onboarding a device with SmartFlex.
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}StartSmartOnboardingProcess
Onboarding for smart tariffs.
This mutation kicks off the smart onboarding for electricity.
The possible errors that can be raised are:
- KT-GB-4102: Unable to start smart onboarding process.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The product enrolment process created. |
Example
{
"possibleErrors": [PossibleErrorType],
"onboardingProcess": SmartOnboardingProcessType,
"productEnrolment": ProductEnrolmentType
}StartTestChargeForSmartFlexOnboarding
Attempt to start a test charge.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4371: Onboarding wizard ID is invalid.
- KT-CT-4372: Simultaneous attempts to update onboarding process.
- KT-CT-4375: Incorrect or missing parameters for SmartFlex onboarding step.
- KT-CT-4376: Unable to complete onboarding step. Please try again later.
- KT-CT-4377: Invalid onboarding step ID.
- KT-CT-4378: Invalid input or step id. Please make sure you are using the correct step id and providing the expected input params.
- KT-CT-4379: Vehicle is not ready for a test charge.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}Fields
| Name | Description |
|---|---|
|
Whether or not target SoC exceeds upper SoC limit. |
|
Time of the latest SoC limit reading. |
|
Maximum level of charge allowed by the battery relative to its capacity (in percent). |
Example
{
"upperSocLimit": 1,
"timestamp": "abc123",
"isLimitViolated": true
}StatementBillingDocumentConnectionTypeConnection
A statement is a billing document that contains all entries on a ledger during a period of time. A customer can understand how their ledger's balance has changed by looking at each statement in series.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": StatementBillingDocumentConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}StatementBillingDocumentConnectionTypeEdge
A Relay edge containing a StatementBillingDocumentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": StatementBillingDocumentType,
"cursor": "abc123"
}StatementBillingDocumentType
A statement is a billing document that contains all entries on a ledger during a period of time. A customer can understand how their ledger's balance has changed by looking at each statement in series.
Fields
| Name | Description |
|---|---|
|
Billing document that annuls this statement. |
|
Position of the billing document in the delinquent debt tracking system. |
|
The earliest charge date of the statement. |
|
The end of the statement's period. |
|
The date and time the statement was sent to the customer. |
|
|
|
The unique reference of the statement that can be used for identifying the statement externally. |
|
The latest charge date of the statement. |
|
The date due for payment for the statement. |
|
URL to the PDF of the statement. |
|
The start of the statement's period. |
|
The total amounts for all charges on the statement. |
|
The total amounts for all credits on the statement. |
|
Transactions on the statement |
Example
{
"id": 1,
"identifier": "abc123",
"startAt": "2020-01-01T00:00:00.000Z",
"endAt": "2020-01-01T00:00:00.000Z",
"firstIssuedAt": "2020-01-01T00:00:00.000Z",
"earliestChargeAt": "2020-01-01T00:00:00.000Z",
"latestChargeAt": "2020-01-01T00:00:00.000Z",
"paymentDueDate": "2020-01-01",
"pdfUrl": "abc123",
"annulledBy": AnnulmentBillingDocumentType,
"totalCharges": StatementTotalType,
"totalCredits": StatementTotalType,
"transactions": BillTransactionConnectionTypeConnection,
"documentDebtPosition": BillingDocumentPositionType
}Fields
| Name | Description |
|---|---|
|
The gross total amount for the statement (in minor currency units). |
|
The net total amount for the statement (in minor currency units). |
|
The total amount of tax on the statement (in minor currency units). |
Example
{
"netTotal": 1,
"taxTotal": 1,
"grossTotal": 1
}Fields
| Name | Description |
|---|---|
|
|
|
The type of the bill. |
|
This field returns the closing balance of an issued statement. |
|
The last day of consumption that this statement includes. |
|
The first day of consumption that this statement includes. |
|
The date of the constituent bill covered from. |
|
Retrieve the held status of a account statement. |
|
The ID of the constituent bill. |
|
Whether the bill originated in Kraken or externally. |
|
The date the bill was sent to the customer. |
|
This field returns the opening balance of a statement. |
|
The date the bill is due to be paid. |
|
How many charges have been reversed after the close date. |
|
Current status of the associated statement. |
|
Requesting this field generates a temporary URL at which bill is available. This URL will expire after approximately an hour. It is intended for redirection purposes, NOT persistence in any form (e.g. inclusion in emails or the body of a web page). This field can raise an error with errorClass NOT_FOUND if the bill document has not been created/issued yet. This field is deprecated use 'attachments' field instead. Deprecated The 'temporaryUrl' field is deprecated. |
|
Email recipient address. |
|
The date of the constituent bill covered to. |
|
The total amounts for all charges on the statement. |
|
The total amounts for all credits on the statement. |
|
Transactions on the bill. |
|
Email recipient user ID. |
Example
{
"id": "abc123",
"billType": "STATEMENT",
"fromDate": "2020-01-01",
"toDate": "2020-01-01",
"temporaryUrl": "abc123",
"issuedDate": "2020-01-01",
"attachments": BillingAttachmentConnectionTypeConnection,
"closingBalance": 1,
"openingBalance": 1,
"isExternalBill": true,
"transactions": TransactionConnectionTypeConnection,
"userId": 1,
"toAddress": "abc123",
"paymentDueDate": "2020-01-01",
"consumptionStartDate": "2020-01-01",
"consumptionEndDate": "2020-01-01",
"reversalsAfterClose": "ALL",
"status": "OPEN",
"heldStatus": HeldStatus,
"totalCharges": StatementTotalType,
"totalCredits": StatementTotalType
}Fields
| Name | Description |
|---|---|
|
Monetary cost of the statistic (excluding tax), if applicable. |
|
Monetary cost of the statistic (including tax), if applicable. |
|
Description of the statistic for the parent node. |
|
Display label of the statistic for the parent node. |
|
The type of statistic being measured for the parent node. |
|
Consumption / generation value of the statistic, if applicable. |
Example
{
"type": "STANDING_CHARGE_COST",
"label": "abc123",
"description": "abc123",
"costExclTax": EstimatedMoneyType,
"costInclTax": EstimatedMoneyType,
"value": "1.0"
}StopAutomatedPayments
Choose how automatic payments will be collected.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-3968: Preference cannot be set this soon.
- KT-CT-3969: Preferences must change on a specific day of the week for weekly schedules.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType]
}StoreElectricJuicePaymentInstruction
Store a new card instruction for Electric Juice from an embedded form.
The possible errors that can be raised are:
- KT-CT-3923: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentInstruction": PaymentInstructionType
}StorePaymentInstruction
Store a new payment instruction created through the embedded process.
The possible errors that can be raised are:
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-4177: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The stored payment instruction. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentInstruction": PaymentInstructionType
}SubmitCustomerFeedback
The possible errors that can be raised are:
- KT-CT-5514: Unable to submit feedback.
- KT-CT-5511: The feedback_id should be provided for feedback source.
- KT-CT-5512: The feedback doesn't match the account.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"customerFeedback": CustomerFeedbackType
}SubmitRepaymentRequest
Mutation for executing the repayment request use case.
The possible errors that can be raised are:
- KT-CT-1132: Unauthorized.
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-3926: Unauthorized.
- KT-CT-3927: Invalid Amount.
- KT-CT-3928: Idempotency key used for another repayment request.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The newly created repayment request. |
Example
{
"possibleErrors": [PossibleErrorType],
"repaymentRequest": RequestRepaymentOutputType
}SupplementaryLedgerType
Ledgers provide the foundation of Kraken’s bookkeeping functionality. Similar to a bank account, they allow us to keep track of financial activity on a particular Kraken account.
Fields
| Name | Description |
|---|---|
|
The current final balance of the ledger in pence. |
|
Deprecated The 'ledgerId' field is deprecated. |
|
|
|
The display name of the ledger. |
|
The canonical name of the ledger. |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"id": "abc123",
"name": "abc123",
"ledgerType": "abc123",
"number": "abc123",
"currentBalance": 1,
"paymentAdequacy": PaymentAdequacyDetailsType
}Fields
| Name | Description |
|---|---|
|
The end date of the supply period. |
|
The start date of the supply period. |
Example
{
"supplyStartAt": "2020-01-01T00:00:00.000Z",
"supplyEndAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": SupplyPointConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}SupplyPointConnectionTypeEdge
A Relay edge containing a SupplyPointConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": SupplyPointType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Supply point external identifier. |
|
Supply point market name. |
|
Requested supply start date. |
Example
{
"externalIdentifier": "abc123",
"marketName": "abc123",
"requestedSupplyStartDate": "2020-01-01"
}SupplyPointType
Represents a SupplyPoint.
Fields
| Name | Description |
|---|---|
|
The external identifier of the supply point. |
|
The ID of the supply point. |
|
The market this supply point belongs to. |
|
The meter point associated with this supply point. |
|
The supply point's property |
|
Get readings from this supply point. |
Example
{
"id": "abc123",
"marketName": "abc123",
"externalIdentifier": "abc123",
"property": PropertyType,
"readings": ReadingsConnection,
"meterPoint": MeterPointType
}SupplyProductType
GraphQL type for a supply product.
Fields
| Name | Description |
|---|---|
|
The product availability status. |
|
The date and time the product is available from. |
|
The date and time the product is available to. |
|
The brand code of the product. |
|
The product code. |
|
The product description. |
|
The product description. |
|
The date the product ends. |
|
The product title. |
|
|
|
Whether the product is hidden. |
|
The name of the market the product belongs to. |
|
The product notes. |
|
The product parameters. |
|
Tags associated with the product. |
|
The product term in months. |
|
Active terms and conditions for a market supply product. |
|
The product contract type. |
Example
{
"id": "abc123",
"code": "abc123",
"notes": "abc123",
"fullName": "abc123",
"displayName": "abc123",
"description": "abc123",
"availableFrom": "2020-01-01T00:00:00.000Z",
"availableTo": "2020-01-01T00:00:00.000Z",
"isHidden": true,
"term": 1,
"endsAt": "2020-01-01T00:00:00.000Z",
"brandCode": "abc123",
"marketName": "abc123",
"availabilityStatus": "EVERYONE",
"termsContractType": "abc123",
"termsAndConditionsTypes": TermsAndConditionsType,
"params": {"key": "value"},
"tags": "abc123"
}Fields
| Name | Description |
|---|---|
|
The maximum number of spins per month, per fuel type. |
|
The number of spins remaining for this month, per fuel type. |
|
The number of spins used this month, per fuel type. |
Example
{
"maxSpinsPerMonth": 1,
"remainingSpinsThisMonth": 1,
"usedSpinsThisMonth": 1
}SuspendDeviceControl
Suspend control of a device while away from home, e.g. on holiday.
This is to prevent charging during that period.
The possible errors that can be raised are:
- KT-CT-4301: Unable to find device for given account.
- KT-CT-4358: Unable to suspend device control.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"krakenflexDevice": KrakenFlexDeviceType
}SwitchAccountToVariablePaymentSchedule
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-3921: Account not found.
- KT-CT-3922: Ledger not found for the account.
- KT-CT-3947: An unexpected error occurred.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
New payment schedule. |
Example
{
"possibleErrors": [PossibleErrorType],
"schedule": PaymentScheduleType
}SwitchMeterPointProducts
Switch the provided meter points to the specified product.
The possible errors that can be raised are:
- KT-GB-4116: Invalid data.
- KT-GB-4617: Quoted product not found.
- KT-CT-4623: Unauthorized.
- KT-GB-4117: Unable to process product switch.
- KT-GB-4119: Meter point already on another account.
- KT-GB-4120: MPxN has no active agreement.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The account associated with the meter points whose products were switched. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}Fields
| Name | Description |
|---|---|
|
Grid Supply Point group id, eg. '_A'. |
Example
{
"groupId": "abc123"
}Fields
| Name | Description |
|---|---|
|
The time the data was submitted. |
|
The target temperature in Celsius. |
Example
{
"value": "1.0",
"timestamp": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
Cost of a tariff. |
|
Cost of a tariff with tax. |
|
Product code. |
|
Tariff name. |
Example
{
"tariff": "abc123",
"productCode": "abc123",
"cost": 1.0,
"costWithTax": 1.0
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"supplier": "abc123",
"tariffName": "abc123",
"tariffType": "abc123",
"tariffCode": "abc123",
"paymentMethod": "abc123",
"tariffEndsOn": "abc123",
"priceGuaranteedUntil": "abc123",
"exitFees": 1,
"exitFeesType": "abc123",
"additionals": "abc123",
"tariffComparisonRate": 1.0,
"standingCharge": 1.0,
"estimatedAnnualCost": 1,
"annualStandingCharge": 1.0,
"unitRateDay": 1.0,
"unitRateNight": 1.0,
"assumedAnnualConsumptionDay": 1,
"assumedAnnualConsumptionNight": 1
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"supplier": "abc123",
"tariffName": "abc123",
"tariffType": "abc123",
"tariffCode": "abc123",
"paymentMethod": "abc123",
"tariffEndsOn": "abc123",
"priceGuaranteedUntil": "abc123",
"exitFees": 1,
"exitFeesType": "abc123",
"additionals": "abc123",
"tariffComparisonRate": 1.0,
"standingCharge": 1.0,
"estimatedAnnualCost": 1,
"annualStandingCharge": 1.0,
"unitRate": 1.0,
"assumedAnnualConsumption": 1
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"supplier": "abc123",
"tariffName": "abc123",
"tariffType": "abc123",
"tariffCode": "abc123",
"paymentMethod": "abc123",
"tariffEndsOn": "abc123",
"priceGuaranteedUntil": "abc123",
"exitFees": 1,
"exitFeesType": "abc123",
"additionals": "abc123",
"tariffComparisonRate": 1.0,
"standingCharge": 1.0,
"estimatedAnnualCost": 1,
"annualStandingCharge": 1.0,
"unitRateDay": 1.0,
"unitRateNight": 1.0,
"unitRateOffPeak": 1.0,
"assumedAnnualConsumptionDay": 1,
"assumedAnnualConsumptionNight": 1,
"assumedAnnualConsumptionOffPeak": 1
}Fields
| Name | Description |
|---|---|
|
The error message if the task failed. |
|
The result of the task. |
|
The status of the task. |
Example
{
"status": "STARTED",
"result": {"key": "value"},
"error": "abc123"
}Temperature
Describes the temperature of something that is relevant to the heating system.
Fields
| Name | Description |
|---|---|
|
The units in which the temperature is being measured. |
|
The temperature measured. |
Example
{
"value": "1.0",
"unit": "DEGREES_CELSIUS"
}Fields
| Name | Description |
|---|---|
|
The maximum allowable temperature in range. |
|
The minimum allowable temperature in range. |
Example
{
"minimum": Temperature,
"maximum": Temperature
}TemporarySpecialCircumstanceRecordType
Any special circumstances that the user has notified us about, which may entitle them to some specialist services. These circumstances have an end date, after which they will not longer apply. Having young children is an example of this in the UK.
Fields
| Name | Description |
|---|---|
|
The date and time the special circumstance record was created. |
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "abc123",
"summary": "abc123",
"internalCode": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"gasPSRCode": "abc123",
"electricityPSRCode": "abc123",
"expiryDate": "2020-01-01"
}TerminateCreditTransferPermission
Mutation to terminate a credit transfer permission.
The possible errors that can be raised are:
- KT-CT-3822: Unauthorized.
- KT-CT-3825: Credit transfer permission not found.
- KT-CT-3827: The ledger is not valid.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Datetime when the credit transfer permission ends. |
Example
{
"possibleErrors": [PossibleErrorType],
"validTo": "2020-01-01T00:00:00.000Z"
}TerminationFeeType
Represents the termination term of a contract.
Fields
| Name | Description |
|---|---|
|
The amount of the termination fee. |
|
The description of the term. |
|
The display name of the term. |
|
The type of termination fee. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true,
"amount": "1.0",
"feeType": TerminationFeeType
}Fields
| Name | Description |
|---|---|
|
The date from which these terms and conditions are effective. |
|
The html of the terms and conditions document rendered as a JSON string. |
|
The url location of the pdf. |
|
The text body of the terms and conditions. |
|
The major version of the terms and conditions. |
|
The minor version of the terms and conditions. |
Example
{
"versionMajor": 1,
"versionMinor": 1,
"text": "abc123",
"html": "abc123",
"pdfUrl": "abc123",
"effectiveFrom": "2020-01-01T00:00:00.000Z"
}TermsAndConditionsConnectionTypeConnection
Pagination for terms and conditions.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": TermsAndConditionsConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}TermsAndConditionsConnectionTypeEdge
A Relay edge containing a TermsAndConditionsConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": TermsAndConditionsType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
The html of the terms and conditions document rendered as a JSON string. |
|
The markdown text of the terms and conditions. |
|
|
|
|
|
Example
{
"name": "abc123",
"pdfUrl": "abc123",
"brandCode": "abc123",
"markdown": "abc123",
"html": "abc123",
"version": "abc123",
"effectiveFrom": "2020-01-01T00:00:00.000Z"
}TeslaModifyScopes
A step which indicates that the Tesla permission scopes need to be granted by the user in order to register their vehicle.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
Returns the URI to update the permission scopes. |
|
The redirect URI to return to after updating the permission scopes. |
Example
{
"id": "abc123",
"modifyScopesUri": "abc123",
"redirectUri": "abc123"
}TeslaRegistrationFailed
A step which indicates that the Tesla registration failed and the user must re-grant permission scopes to register their vehicle.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
Returns:- |
Example
{
"id": "abc123",
"modifyScopesSelected": true
}TeslaSetupVirtualKey
A step which indicates that the user must add the given URI as a virtual key in their Tesla account.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
The name of the key to add. |
|
The URI to add as a virtual key in the user's Tesla account. |
Example
{
"id": "abc123",
"key": "abc123",
"uri": "abc123"
}TestCharge
A step which indicates if we're able to test charge the user's vehicle(s).
Fields
| Name | Description |
|---|---|
|
Returns the error raised from a failed test charge. |
|
A unique identifier for this onboarding step. |
|
Returns |
|
Returns |
|
Returns the dispatch status of test charge. Deprecated The 'status' field is deprecated. |
Example
{
"id": "abc123",
"error": TestChargeError,
"isReady": true,
"status": "TRIGGERED",
"isStarted": true
}TestChargeError
Errors can be of two kinds (assuming the user is querying this type with message,
reasons, errorType, and descriptions fields):
If we were unable to start a test charge, the response will be:
{ "message": "TestChargeRefused", "reasons": [Returns a list of values from `TestChargeRefusalReason`], "errorType": "UNABLE_TO_INITIATE_TEST_CHARGE", "descriptions": [Returns a list of descriptions for the refusal reasons] }Where
descriptionscan be: -DEVICE_LIVE: "device is already live" -DEVICE_ONBOARDING_IN_PROGRESS: "test dispatch already in progress" -DEVICE_RETIRED: "device is retired" -DEVICE_SUSPENDED: "device is suspended" -DEVICE_DISCONNECTED: "device is disconnected" -DEVICE_ALREADY_CHARGING: "device is already charging" -DEVICE_AWAY_FROM_HOME: "device is away from home" -DEVICE_NO_LOCATION_CONFIGURED: "device has no location configured" -DEVICE_LOCATION_UNABLE_TO_IDENTIFY: "unable to identify device location" -DEVICE_LOCATION_MISSING: "device location is missing"If an error occurred during a test charge, the response will be:
{ "message": "Test dispatch failed", "reasons": [Returns a list of values from `TestDispatchAssessmentFailureReason`], "errorType": "UNABLE_TO_COMPLETE_TEST_CHARGE", "descriptions": [Returns a list of descriptions for the refusal reasons] }Where
descriptionscan be: -ASSESSMENTS_FAILED: "Both power-based and charge status-based assessments failed" -NOT_AT_HOME: "Device location not at home" -UNKNOWN: "Unknown failure" -UNABLE_TO_COMMUNICATE: "Unable to communicate with device" -DEVICE_DISCONNECTED: "Device disconnected" -SOC_LIMIT_REACHED: "State of charge limit reached" -ERROR: "Could not fetch the test charge failure reason" -NONE: "No failure reason"
Fields
| Name | Description |
|---|---|
|
A list of error descriptions for a failed test charge attempt. |
|
The type of test charge error. |
|
A human readable error message. |
|
A list of reasons for a failed test charge attempt. |
|
A list of refusal reasons from the failed test charge attempt. Deprecated The 'refusalReasons' field is deprecated. |
Example
{
"message": "abc123",
"refusalReasons": "DEVICE_LIVE",
"errorType": "UNABLE_TO_INITIATE_TEST_CHARGE",
"reasons": ["abc123"],
"descriptions": ["abc123"]
}TextType
A block of text.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the object. |
|
The text alignment. |
|
The text style, i.e. header, body. |
|
The name of the object's type. |
|
The text content. |
Example
{
"value": "abc123",
"textStyle": "TITLE1",
"textAlignment": "START",
"id": "abc123",
"typename": "abc123"
}ThirdPartyCompleteDeviceRegistration
Complete the registration of a device.
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-4322: Unable to complete registration error.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The response showing account validity and optional tariff information. |
Example
{
"possibleErrors": [PossibleErrorType],
"success": ThirdPartyCompleteDeviceRegistrationType
}Fields
| Name | Description |
|---|---|
|
If the account is valid. |
|
If a switch to the required tariff is in progress. |
|
The tariff the account is on, if the switch is complete. |
Example
{
"isAccountValid": true,
"isTariffSwitchInProgress": true,
"tariff": ThirdPartyTariffsType
}ThirdPartyOrganizationType
Type for the third party organization.
Fields
| Name | Description |
|---|---|
|
|
|
Holds information about the permissions of the current viewer. |
Example
{
"name": "abc123",
"permissions": [ThirdPartyPermission]
}ThirdPartyPermission
Holds information about a specific permission.
Fields
| Name | Description |
|---|---|
|
The short name of the permission |
Example
{
"permission": "abc123"
}Fields
| Name | Description |
|---|---|
|
Day(s) of the week of the tariff interval. |
|
Local 24hr end time of the tariff interval (format hh:mm). |
|
Local 24hr start time of the tariff interval (format hh:mm). |
|
The type of tariff this is (e.g. peak or offPeak). |
Example
{
"startTime": "abc123",
"endTime": "abc123",
"daysOfWeek": "abc123",
"tariffType": "abc123"
}Fields
| Name | Description |
|---|---|
|
Currency according to the ISO 4217 standard. |
|
Price per kWh in the given currency. |
|
The type of tariff this is (e.g. peak or offPeak). |
Example
{
"currency": "abc123",
"price": "1.0",
"type": "abc123"
}Fields
| Name | Description |
|---|---|
|
Tariff intervals of the charging location. |
|
Tariff rates of the charging location. |
Example
{
"tariffs": ThirdPartyTariffType,
"tariffIntervals": ThirdPartyTariffIntervalType
}Fields
| Name | Description |
|---|---|
|
|
|
Is EPG applied to the unit rate. |
|
|
|
|
|
|
|
|
|
Whether the tariff is for exporting energy. |
|
|
|
Is EPG applied to the unit rate. |
|
|
|
Is EPG applied to the unit rate. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Describes a particular tariff by combining the product code, number of rates, available from date and GSP code. |
Example
{
"id": "abc123",
"displayName": "abc123",
"fullName": "abc123",
"description": "abc123",
"productCode": "abc123",
"standingCharge": 1.0,
"preVatStandingCharge": 1.0,
"tariffCode": "abc123",
"isExport": true,
"dayRate": 1.0,
"dayRateEpgApplied": true,
"nightRate": 1.0,
"nightRateEpgApplied": true,
"offPeakRate": 1.0,
"offPeakRateEpgApplied": true,
"preVatDayRate": 1.0,
"preVatNightRate": 1.0,
"preVatOffPeakRate": 1.0
}Fields
| Name | Description |
|---|---|
|
The discount that is rewarded when the power crosses the corresponding threshold. Ranges from 0.0 - 1.0. |
|
The power (kW) that must be surpassed to achieve the corresponding discount. |
|
The wind speed (m/s) that corresponds to the power cut-off for this threshold. |
Example
{
"power": "1.0",
"discount": "1.0",
"windSpeed": "1.0"
}TimeOfUseOverrideType
Represents a time-of-use override to be applied in a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
The type of the term. |
Example
{
"type": NonEmptyString,
"displayName": NonEmptyString,
"description": NonEmptyString,
"identifier": NonEmptyString,
"isVariable": true
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Token's identifying value. |
Example
{
"value": "abc123",
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z"
}TrackOptionType
Key value pair for the choice of tracks.
Fields
| Name | Description |
|---|---|
|
The value save for the user to indicate their choice of track. |
|
The title of the track. |
Example
{
"trackTitle": "abc123",
"trackCode": "abc123"
}Fields
| Name | Description |
|---|---|
|
URL for tracker demo. |
|
Today's electricity costs (in pence). |
|
Today's gas costs (in pence). |
Example
{
"demoUrl": "abc123",
"electricity": 1,
"gas": 1
}Fields
| Name | Description |
|---|---|
|
The gross amount (in minor currency units). |
|
The net amount (in minor currency units). |
|
The amount of tax (in minor currency units). |
Example
{
"net": 1,
"tax": 1,
"gross": 1
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": TransactionConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}TransactionConnectionTypeEdge
A Relay edge containing a TransactionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": TransactionType,
"cursor": "abc123"
}TransferLedgerBalance
Trigger balance transfer between accounts.
The possible errors that can be raised are:
- KT-CT-3822: Unauthorized.
- KT-CT-3823: Unauthorized.
- KT-CT-9701: Balance transfer to same account is not allowed.
- KT-CT-9702: Balance transfer is not support for debit account with Zero balance.
- KT-CT-9703: Balance transfer is not supported for debit account.
- KT-CT-9704: Balance transfer amount should be non-zero.
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Balance transfer details. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"balanceTransfer": AccountBalanceTransferType
}TransferLoyaltyPointsBetweenUsers
Transfer Loyalty Points between users.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-9205: Insufficient Loyalty Points.
- KT-CT-9204: Negative or zero points set.
- KT-CT-9208: Invalid posted at datetime.
- KT-CT-9209: Negative Loyalty Points balance.
- KT-CT-9210: Unhandled Loyalty Points exception.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The number of loyalty points that were transferred. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"pointsTransferred": 1
}Fields
| Name | Description |
|---|---|
|
The date/time that the trigger was created. |
|
The ID of the trigger. |
|
The messages created in response to this trigger. |
|
The current processing status of this trigger. |
|
The trigger type code for this trigger. |
Example
{
"id": "abc123",
"triggerTypeCode": "abc123",
"createdAt": "2020-01-01T00:00:00.000Z",
"messages": MessageConnection,
"processingStatus": "UNPROCESSED"
}TriggerPostUploadOperations
The possible errors that can be raised are:
- KT-CT-8710: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"operationsTriggered": true
}Fields
| Name | Description |
|---|---|
|
The non-human-legible address in a single string. |
|
First address line. |
|
Second address line. |
|
Third address line. |
|
Fourth address line. |
|
Fifth address line. |
|
The complete and human-legible address in a single string. |
|
Postcode. |
|
Unique Property Reference Number. |
Example
{
"uprn": "abc123",
"addressLine1": "abc123",
"addressLine2": "abc123",
"addressLine3": "abc123",
"addressLine4": "abc123",
"addressLine5": "abc123",
"postcode": "abc123",
"display": "abc123",
"addressKey": "abc123"
}Fields
| Name | Description |
|---|---|
|
Unique Property Reference Number. |
Example
{
"uprn": "abc123"
}UnenrollAccountFromLoyaltyProgram
Unenroll an account from the loyalty program.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-9220: Ineligible loyalty points unenrollment.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Outcome of the loyalty points campaign enrollment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"outcome": UnenrollAccountFromLoyaltyProgramOutcome
}Fields
| Name | Description |
|---|---|
|
Indicates whether the account has been unenrolled from the loyalty points campaign. |
Example
{
"hasUnenrolled": true
}Fields
| Name | Description |
|---|---|
|
The human-legible address in a single string, excluding the postcode. |
|
Dependant locality e.g. 'Durham'. |
|
Double dependant locality e.g. 'Durham East'. |
|
The postcode of the address. |
|
Primary Addressable Object description, normally the name or number of the property e.g. 'London House'. |
|
Secondary Addressable Object description, e.g. 'Flat 2'. This is only relevant for a child property. |
|
The thoroughfare e.g. 'Witton Grove'. |
|
Dependant thoroughfare e.g. 'Witton Grove East'. |
|
The town or city e.g. 'London'. |
|
The Unique Property Reference Number assigned to the addressable location. |
Example
{
"uprn": "abc123",
"display": "abc123",
"primaryName": "abc123",
"secondaryName": "abc123",
"street1": "abc123",
"street2": "abc123",
"locality1": "abc123",
"locality2": "abc123",
"town": "abc123",
"postcode": "abc123"
}Fields
| Name | Description |
|---|---|
|
Price in pence (not including VAT). |
|
|
|
|
|
Price in pence (inc VAT). |
Example
{
"validFrom": "2020-01-01T00:00:00.000Z",
"validTo": "2020-01-01T00:00:00.000Z",
"value": 1.0,
"preVatValue": 1.0
}UpdateAPIException
The possible errors that can be raised are:
- KT-CT-7804: No fields present in the input for updating the APIException.
- KT-CT-7803: Received an invalid apiExceptionId.
- KT-CT-7809: Update results in no changes to API Exception.
- KT-CT-7805: Too many tags associated with this API Exception.
- KT-CT-7806: Cannot create duplicate tags for the same API exception.
- KT-CT-7801: Received an invalid operationsTeamId.
- KT-CT-7811: Received an invalid assignedUserId.
- KT-CT-7812: Support user is inactive.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated APIException. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"apiException": APIExceptionType
}UpdateAPIExceptionNote
The possible errors that can be raised are:
- KT-CT-7807: Received an invalid apiExceptionNoteId.
- KT-CT-7808: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updates APIExceptionNote. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"apiException": APIExceptionType
}UpdateAccountBillingAddress
The possible errors that can be raised are:
- KT-CT-4145: Invalid address.
- KT-CT-7123: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated account. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}UpdateAccountBillingEmail
Update the billing email for the input account number to the received email value.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-4122: Invalid email.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account that was changed. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountInterface
}UpdateAccountConsents
Update the consents for an account using consent management system
The possible errors that can be raised are:
- KT-CT-9014: Duplicate consent.
- KT-CT-9016: Consent management not enabled.
- KT-CT-9017: Consent type not found.
- KT-CT-9018: Account not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Consents linked to this account. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"consents": ConsentType
}UpdateAccountReference
Update a reference for a particular account and namespace.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-8310: Invalid data.
- KT-CT-8311: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountReference": AccountReferenceType
}UpdateAccountSmartMeterInterest
Set stated interest in acquiring a smart meter of an account.
The possible errors that can be raised are:
- KT-GB-4115: Could not create smart meter interest for account.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The interest of an account in procuring smart meters. |
|
The source category of the smart meter interest update. |
|
The reason why the account holder is not interested in having a smart meter installed. |
Example
{
"possibleErrors": [PossibleErrorType],
"interestUpdated": true,
"smets2Interest": "PRIORITY",
"smets2InterestSource": "WEBSITE",
"smets2RefusalReason": "SMETS2_INTEREST_REASON_DO_NOT_OWN_HOME"
}UpdateAccountUserCommsPreferencesMutationPayload
Update the account user comms preferences.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"isOptedInToClientMessages": true,
"isOptedInToOfferMessages": true,
"isOptedInToRecommendedMessages": true,
"isOptedInToUpdateMessages": true,
"isOptedInToThirdPartyMessages": true,
"isOptedInMeterReadingConfirmations": true,
"isOptedInToSmsMessages": true,
"isUsingInvertedEmailColours": true,
"fontSizeMultiplier": 1.0,
"emailFormat": "abc123",
"preferredHoldMusic": "abc123",
"errors": [ErrorType],
"commsPreferences": AccountUserCommsPreferences,
"clientMutationId": "abc123"
}UpdateAccountUserConsents
Update the consents from an account user using consent management system
The possible errors that can be raised are:
- KT-CT-9014: Duplicate consent.
- KT-CT-9016: Consent management not enabled.
- KT-CT-9017: Consent type not found.
- KT-CT-1111: Unauthorized.
- KT-CT-5421: Account user not found.
- KT-CT-5422: Invalid data.
- KT-CT-1605: Invalid input.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
All the consents for an account user. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountUserConsents": AccountUserConsents
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"givenName": "abc123",
"familyName": "abc123",
"pronouns": "abc123",
"mobile": "abc123",
"email": "abc123",
"dateOfBirth": "2020-01-01",
"landline": "abc123",
"errors": [ErrorType],
"clientMutationId": "abc123"
}UpdateActivePurchase
The possible errors that can be raised are:
- KT-CT-8225: Received an invalid purchaseId.
- KT-CT-8226: The provided purchase is not active.
- KT-CT-8206: Invalid data.
- KT-CT-8227: Available grants could not be applied.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Goods purchase updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"goodsPurchase": GoodsPurchase
}UpdateAffiliateLink
Update an affiliate link of an existing sales agent.
The possible errors that can be raised are:
- KT-CT-7711: Invalid data.
- KT-CT-7713: Invalid data.
- KT-CT-7714: Invalid data.
- KT-CT-7715: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated affiliate link. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"affiliateLink": AffiliateLinkType
}UpdateAffiliateOrganisation
Update an affiliate organisation.
The possible errors that can be raised are:
- KT-CT-7717: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated affiliate organisation. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"affiliateOrganisation": AffiliateOrganisationType
}UpdateAgreementPeriod
Update the period of an agreement.
The possible errors that can be raised are:
- KT-CT-4178: No account found with given account number.
- KT-CT-1501: Agreement not found.
- KT-CT-1503: Agreement validto date must be later than validfrom date.
- KT-CT-1504: Account does not match with the agreement.
- KT-CT-1505: Unable to edit agreement.
- KT-CT-1506: Agreement period is not within the supply and property period.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account responsible for the update agreement. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}UpdateAutoTopUpAmount
The possible errors that can be raised are:
- KT-CT-3815: No active payment schedule found for this account.
- KT-CT-3941: Invalid data.
- KT-CT-3942: An unexpected error occurred.
- KT-CT-3947: An unexpected error occurred.
- KT-CT-3953: The payment schedule is not a balance triggered schedule.
- KT-CT-3820: Received both ledger ID and number.
- KT-CT-3821: Received neither ledger ID nor ledger number.
- KT-CT-3822: Unauthorized.
- KT-CT-4123: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The new schedule created. |
Example
{
"possibleErrors": [PossibleErrorType],
"schedule": PaymentScheduleType
}UpdateCharityDonation
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-GB-11901: Could not update charity donation.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Amount that will be donated each month. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"amount": "ONE"
}UpdateCollectionProcessRecordToActive
Update the Collection Process Record from raised status to active
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-11202: No External reference provided.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the collection process was successfully updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessActivated": UpdateCollectionProcessRecordToActiveOutputType
}UpdateCollectionProcessRecordToActiveOutputType
Output for updating a Collection process Record to Active.
Fields
| Name | Description |
|---|---|
|
The number of the collection process record. |
|
The current status of the collection process record. |
Example
{
"number": "abc123",
"status": "PENDING"
}UpdateCollectionProcessRecordToComplete
Update the Collection Process Record from raised status to complete
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-11203: No Completion reason provided.
- KT-CT-11204: No Completion details provided.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the collection process was successfully updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessComplete": UpdateCollectionProcessRecordToCompleteOutputType
}UpdateCollectionProcessRecordToCompleteOutputType
Output for updating a Collection process Record to Complete.
Fields
| Name | Description |
|---|---|
|
The number of the collection process record. |
|
The current status of the repayment request. |
Example
{
"number": "abc123",
"status": "PENDING"
}UpdateCommsDeliveryPreference
Update the comms delivery preference for the input account number to the received commsDeliveryPreference value.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-4136: Cannot set comms preference to email when account has no email.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountInterface
}UpdateCommsHubStatus
Update the status of the communications hub.
The possible errors that can be raised are:
- KT-GB-4026: Either the mpxn or mpan input must be provided.
- KT-GB-4027: If both mpxn and mpan are provided, they must match.
- KT-GB-4028: Please input a valid MPxN.
- KT-GB-4029: Meter point not found for MPAN.
- KT-GB-4030: Meter point not found for MPRN.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The id of the Request object in Kraken. |
Example
{
"possibleErrors": [PossibleErrorType],
"requestReference": "abc123"
}UpdateDCAProceeding
The possible errors that can be raised are:
- KT-CT-11610: unable to edit the debt collection proceeding.
- KT-CT-11604: Active debt collection proceeding does not exist for account.
- KT-CT-11605: Multiple active Proceeding's found for same agency and campaign on account.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the update has been applied. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"dcaProceedingUpdateStatus": DCAProceedingUpdateStatus
}UpdateFlowTemperatureConfiguration
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Unique ID associated with this operation. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}UpdateLeadAssignment
The possible errors that can be raised are:
- KT-CT-8907: Lead not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Arguments passed. |
Example
{
"possibleErrors": [PossibleErrorType],
"updatedLeadData": {"key": "value"}
}UpdateLeadDetails
The possible errors that can be raised are:
- KT-CT-8907: Lead not found.
- KT-CT-8913: Organisation is not valid to be assigned.
- KT-CT-8914: Stage not found.
- KT-CT-8915: Stages are not in the same funnel.
- KT-CT-8916: Current stage mismatch.
- KT-CT-8917: Stage transition not allowed.
- KT-CT-8918: Stage precondition not met.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Arguments passed. |
Example
{
"possibleErrors": [PossibleErrorType],
"updatedLeadData": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
|
|
Confirmed tags. |
Example
{
"tags": InkTag,
"clientMutationId": "abc123"
}UpdateMetadata
Update existing metadata on an object.
The possible errors that can be raised are:
- KT-CT-4323: Unauthorized.
- KT-CT-8413: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"metadata": Metadata
}UpdateOpportunityAssignment
The possible errors that can be raised are:
- KT-CT-8906: Opportunity not found.
- KT-CT-8903: Unable to update opportunity.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Arguments passed. |
Example
{
"possibleErrors": [PossibleErrorType],
"updatedOpportunityData": {"key": "value"}
}UpdateOpportunityExtraDetails
The possible errors that can be raised are:
- KT-CT-8903: Unable to update opportunity.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The opportunity's extra details to be added or updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"extraDetails": {"key": "value"}
}UpdateOpportunityStage
The possible errors that can be raised are:
- KT-CT-8903: Unable to update opportunity.
- KT-CT-8910: Received opportunity current stage is not valid.
- KT-CT-8914: Stage not found.
- KT-CT-8915: Stages are not in the same funnel.
- KT-CT-8916: Current stage mismatch.
- KT-CT-8917: Stage transition not allowed.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Placeholder success message for now. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": "abc123"
}UpdatePassword
Update user's password.
Note this is different from the ResetPassword mutation, which is used to reset a password when the user has forgotten it. This mutation is used to update the password when the user is already authenticated and wants to change their password.
Ideally, this mutation would simply receive a "new_password" and use the current password update usecase, but, until we're ready for a breaking change, we'll need to use the Django form to also validate the old password and two new passwords.
The possible errors that can be raised are:
- KT-CT-5460: Old password is invalid.
- KT-CT-5450: Password is invalid.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The currently authenticated user. This field requires the |
Example
{
"possibleErrors": [PossibleErrorType],
"viewer": AccountUserType
}UpdatePaymentSchedulePaymentAmount
The possible errors that can be raised are:
- KT-GB-3919: Invalid payment schedule amount.
- KT-GB-3920: Cannot update payment schedule amount.
- KT-CT-3923: Unauthorized.
- KT-CT-3941: Invalid data.
- KT-CT-3942: An unexpected error occurred.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentSchedule": PaymentScheduleType
}UpdatePaymentSchedulePaymentDay
The possible errors that can be raised are:
- KT-GB-3918: Account not found.
- KT-GB-3910: This feature is not available to business accounts.
- KT-GB-3911: Your payment day cannot be changed at this time.
- KT-GB-3912: Unable to update payment day.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentSchedule": PaymentScheduleType
}UpdateProductPricesOutput
Rate group prices for a product.
Fields
| Name | Description |
|---|---|
|
The rate group prices. |
Example
{
"prices": RateGroupPrices
}UpdateSensorDisplayName
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Unique ID associated with updating a sensor attribute. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}UpdateSiteworksRequest
The possible errors that can be raised are:
- KT-CT-4231: Unauthorized.
- KT-CT-4232: Status passed is not valid.
- KT-CT-4233: Request does not exist.
- KT-CT-4234: Terminated Request cannot be updated.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The siteworks request after the update. |
Example
{
"possibleErrors": [PossibleErrorType],
"siteworksRequest": CoreSiteworksRequestType
}UpdateSmartMeterDataPreferences
Update smart meter data preferences of an account.
The possible errors that can be raised are:
- KT-CT-4023: Unauthorized.
- KT-GB-4015: Cannot update smart meter reading frequency preferences.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
|
|
Example
{
"possibleErrors": [PossibleErrorType],
"preferencesUpdated": true,
"smartMeterDataPreferences": SmartMeterDataPreferencesType
}UpdateSpecialCircumstances
The possible errors that can be raised are:
- KT-GB-5411: Failed to update special circumstance record.
- KT-CT-9404: Received an invalid accountUserId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Return type displaying an AccountUser's special circumstances. |
Example
{
"possibleErrors": [PossibleErrorType],
"specialCircumstances": SpecialCircumstancesType
}UpdateSpecialCircumstancesAsOrganization
The possible errors that can be raised are:
- KT-GB-5411: Failed to update special circumstance record.
- KT-CT-9404: Received an invalid accountUserId.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Return type displaying an AccountUser's special circumstances. |
Example
{
"possibleErrors": [PossibleErrorType],
"specialCircumstances": SpecialCircumstancesType
}UpdateSsd
Mutation to update the Supply Start Date (SSD) of an account.
The possible errors that can be raised are:
- KT-GB-4101: Unable to update SSD for account.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"ssdUpdated": true,
"estimatedSsd": "2020-01-01"
}UpdateSupplyPointMetadata
The possible errors that can be raised are:
- KT-CT-8413: Invalid data.
- KT-CT-8415: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated metadata. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"metadata": Metadata
}UpdateUserMutation
The possible errors that can be raised are:
- KT-CT-5413: Invalid data.
- KT-CT-5414: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"viewer": AccountUserType
}UpdateWaterSetpoint
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Unique ID associated with this operation. |
Example
{
"possibleErrors": [PossibleErrorType],
"transactionId": "abc123"
}UploadPostRequest
Information that should be used in the POST request to the S3 API.
For more details please see this.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"url": "abc123",
"fields": {"key": "value"},
"key": "abc123"
}Fields
| Name | Description |
|---|---|
|
Present for completed dispatches, otherwise |
|
Present for planned dispatches, otherwise |
Example
{
"source": "abc123",
"location": "abc123"
}Fields
| Name | Description |
|---|---|
|
Energy in kWh (import has a negative value). |
|
This field has been replaced by Deprecated The 'deltaKwh' field is deprecated. |
|
The end time of the dispatch. |
|
This field has been replaced by Deprecated The 'endDt' field is deprecated. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The start time of the dispatch. |
|
This field has been replaced by Deprecated The 'startDt' field is deprecated. |
Example
{
"start": "2020-01-01T00:00:00.000Z",
"end": "2020-01-01T00:00:00.000Z",
"startDt": "abc123",
"endDt": "abc123",
"deltaKwh": 1,
"delta": "1.0",
"meta": UpsideDispatchMetaType
}Fields
| Name | Description |
|---|---|
|
URL to book a smart meter installation for the given account and property. |
|
Pre-signed URL to the saving session dashboard. |
|
Pre-signed URL to join the Saving Sessions campaign. |
|
The tariff renewal URL for the given account. Deprecated The 'tariffRenewal' field is deprecated. |
|
The Wheel of Fortune URL for the given account's electricity meter. Deprecated The 'wheelOfFortuneElec' field is deprecated. |
|
The Wheel of Fortune URL for the given account's gas meter. Deprecated The 'wheelOfFortuneGas' field is deprecated. |
Example
{
"wheelOfFortuneElec": "abc123",
"wheelOfFortuneGas": "abc123",
"tariffRenewal": "abc123",
"bookSmartMeterInstallation": "abc123",
"savingSessionsJoinCampaign": "abc123",
"savingSessionsDashboard": "abc123"
}UserActionReason
A type that returns a user action that needs to be completed for the device to be successfully registered.
Fields
| Name | Description |
|---|---|
|
Description of the required user action. |
|
An optional uri that, if provided, can navigate the user to where they can resolve this required action. |
|
Reference key to the required user action. |
Example
{
"userAction": "abc123",
"description": "abc123",
"uri": "abc123"
}UserActionRequired
A type that returns user actions that need to be completed for the device to be successfully registered
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
List of actions the user must resolve in order for the device to be registered. |
Example
{
"id": "abc123",
"userActions": [UserActionReason]
}UserManagedPayment
Represents the preference of the user to pay himself, instead of get charged.
Fields
| Name | Description |
|---|---|
|
The start time of the payment preference. |
Example
{
"forPaymentsAfter": "abc123"
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Example
{
"vehicleId": "abc123",
"information": VehicleInformationType
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"bankName": "abc123",
"branch": "abc123",
"county": "abc123",
"line1": "abc123",
"line2": "abc123",
"line3": "abc123",
"line4": "abc123",
"town": "abc123",
"postcode": "abc123"
}ValidateEmail
Validate whether a user's email is a valid email via the Kickbox API.
Fields
| Name | Description |
|---|---|
|
Whether the email is valid or not. |
Example
{
"isValid": true
}ValidatePhone
Validate whether a user's phone number is a valid phone number.
Fields
| Name | Description |
|---|---|
|
Whether the phone number is valid or not. |
Example
{
"isValid": true
}VaryContractTermsOutput
Output type for varying contract terms.
Fields
| Name | Description |
|---|---|
|
The contract with the varied terms. |
Example
{
"contract": Contract
}Fields
| Name | Description |
|---|---|
|
The maximum state of charge (soc) %, if available. |
|
The minimum state of charge (soc) %, if available. |
|
|
|
|
|
|
|
Example
{
"weekdayTargetTime": "abc123",
"weekdayTargetSoc": 1,
"weekendTargetTime": "abc123",
"weekendTargetSoc": 1,
"minimumSocPercentage": 1,
"maximumSocPercentage": 1
}Fields
| Name | Description |
|---|---|
|
|
|
The (user chosen) display name of the vehicle, if available. |
|
The model name of the vehicle, if available (e.g. i3s 120). |
|
|
|
The year of the vehicle model, if available. |
Example
{
"vin": "abc123",
"brand": "abc123",
"model": "abc123",
"year": 1,
"displayName": "abc123"
}Fields
| Name | Description |
|---|---|
|
Verification process status. |
|
Verification type. |
|
Customer with pending verification. |
Example
{
"userNumber": "abc123",
"status": "abc123",
"type": "abc123"
}VerifyCustomer
Verify a customer using the provided code and verification type.
The possible errors that can be raised are:
- KT-CT-4191: Error while verifying the customer.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The currently authenticated user. |
Example
{
"possibleErrors": [PossibleErrorType],
"user": AccountUserType
}VerifyEmail
The possible errors that can be raised are:
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Whether the email is verified. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"isVerified": true
}VerifyIdentity
The possible errors that can be raised are:
- KT-CT-1145: Account/user details do not match.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
An expiring token that can be used to request to update the user's email address. |
Example
{
"possibleErrors": [PossibleErrorType],
"token": "abc123"
}VoiceCampaignConnectionTypeConnection
Paginator of Voice Campaigns
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": VoiceCampaignConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}VoiceCampaignConnectionTypeEdge
A Relay edge containing a VoiceCampaignConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": VoiceCampaignType,
"cursor": "abc123"
}VoiceCampaignItemConnectionTypeConnection
Paginator of Campaign Items
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": VoiceCampaignItemConnectionTypeEdge,
"totalCount": 1,
"edgeCount": 1
}VoiceCampaignItemConnectionTypeEdge
A Relay edge containing a VoiceCampaignItemConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": VoiceCampaignItemType,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
The account ID associated with the item. If the phone number for the item is not set, the account ID will be used to determine the phone number to call. |
|
Together with |
|
Together with |
|
The ID of the campaign item. |
|
Metadata about the item. This enables items to be filtered based on additional information such as location. It is a dictionary of key-value pairs, with both keys and values being strings. |
|
The phone number of the campaign item. This is used to determine the phone number to call when the item is processed. If it is not set, the account ID will be used instead to call the phone number associated with the account. |
|
The status of the campaign item that determines what actions can be taken on it. |
Example
{
"id": "abc123",
"phoneNumber": "abc123",
"status": "UNASSIGNED",
"callWindowStart": "2020-01-01T00:00:00.000Z",
"callWindowEnd": "2020-01-01T00:00:00.000Z",
"accountId": "abc123",
"metadata": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
The items that are part of the campaign. These are the items that contain information about what phone numbers or accounts to call while this campaign is active. |
|
The type of campaign, e.g. preview or predictive. |
|
If appropriate, a custom number to use as the caller id for calls from this campaign. |
|
Additional information to describe the purpose of the campaign. |
|
The ID of the campaign. |
|
The name of the campaign. This is used to identify the campaign in the system, and must be unique. |
|
Flag to indicate whether not to create a duplicate record when uploading campaign items that already exist for a given account number and/or phone number |
|
The status of the campaign. Indicates whether calls can be made for items in the campaign or not. |
|
The call tags that can be used within this campaign. |
Example
{
"id": "abc123",
"name": "abc123",
"description": "abc123",
"customOutboundPhoneNumber": "abc123",
"tags": CallTagConnectionTypeConnection,
"status": "ACTIVE",
"campaignType": "PREVIEW",
"campaignItems": VoiceCampaignItemConnectionTypeConnection,
"preventDuplicateRecords": true
}WaitForLiveIntegration
Indicates a step where the integration is pending activation.
Progress to the next onboarding step is blocked until the integration becomes active.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
Returns |
Example
{
"id": "abc123",
"isLive": true
}WaitForTransition
A generic step that can be used to hold an onboarding wizard until the device has transitioned from one onboarding state to another.
Generally, this step should be completed via a KF AMI event handler after the device has been registered and transitioned to the desired state.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
Example
{
"id": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"postcode": "abc123",
"addressIdentifier": "abc123",
"isCoverageAvailable": true,
"anticipatedCoverageAt": "abc123",
"wanTechnology": "abc123",
"auxiliaryEquipment": "abc123",
"connectivityLikelihood": "abc123",
"additionalInformation": "abc123"
}Fields
| Name | Description |
|---|---|
|
Get the Warm Home Discount applications against this account. These are ordered to return the most recent first. |
|
Get the Warm Home Discount records attached to this account. These are ordered to return the most recent first. |
Example
{
"applications": WarmHomeDiscountApplicationConnection,
"records": WarmHomeDiscountRecordConnection
}WarmHomeDiscountApplication
Get details about a Warm Home Discount application.
Fields
| Name | Description |
|---|---|
|
Which component criteria was chosen for the Warm Home Discount application. |
|
Which criteria was chosen for the Warm Home Discount application. |
|
Reason for rejecting a Warm Home Discount application. |
|
The status of the Warm Home Discount application. |
|
The tax year for which the application was made. |
|
The last date on which this application was updated. |
|
Example
{
"qualifyingCriteria": "SAVINGS_ELEMENT_OF_PENSION_CREDIT",
"qualifyingComponent": "PERSONAL_INDEPENDENCE_PAYMENTS",
"yearEnding": 1,
"status": "PENDING",
"rejectionReason": "APPLICATIONS_NOT_OPEN",
"taxYear": "abc123",
"updatedAt": "2020-01-01"
}WarmHomeDiscountApplicationConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": WarmHomeDiscountApplicationEdge,
"totalCount": 1,
"edgeCount": 1
}WarmHomeDiscountApplicationEdge
A Relay edge containing a WarmHomeDiscountApplication and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": WarmHomeDiscountApplication,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"errors": [SerializerFieldErrorsType],
"id": "abc123"
}Fields
| Name | Description |
|---|---|
|
Is the customer eligible to apply for the Warm Home Discount as part of the Scottish Broader Group. |
|
Reason why the customer is unable to apply. |
Example
{
"isEligible": true,
"rejectionReason": "abc123"
}WarmHomeDiscountRecord
Get details about a Warm Home Discount record.
Fields
| Name | Description |
|---|---|
|
Type of account receiving the discount. Either credit the account or payment via prepay cards. |
|
Amount in pence that was credited to the account as a result of the discount. |
|
Which component criteria was chosen for the Warm Home Discount. |
|
Which criteria was chosen for the Warm Home Discount. |
|
The tax year for which the credit was given. |
|
Example
{
"accountType": "SMART_PREPAY",
"yearEnding": 1,
"qualifyingCriteria": "SAVINGS_ELEMENT_OF_PENSION_CREDIT",
"qualifyingComponent": "PERSONAL_INDEPENDENCE_PAYMENTS",
"credit": 1,
"taxYear": "abc123"
}WarmHomeDiscountRecordConnection
This field is a connection type. Connections are used to implement cursor based pagination.
Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
Example
{
"pageInfo": PageInfo,
"edges": WarmHomeDiscountRecordEdge,
"totalCount": 1,
"edgeCount": 1
}WarmHomeDiscountRecordEdge
A Relay edge containing a WarmHomeDiscountRecord and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": WarmHomeDiscountRecord,
"cursor": "abc123"
}Fields
| Name | Description |
|---|---|
|
Serial number. |
|
Meter point reference. |
|
The frequency of the reading. |
Example
{
"marketSupplyPointId": "abc123",
"deviceId": "abc123",
"readingFrequencyType": "RAW_INTERVAL"
}Fields
| Name | Description |
|---|---|
|
The current temperature of the hot water tank in Celsius. |
|
Example
{
"waterTemperatureEnabled": true,
"currentWaterTemperature": "1.0"
}Fields
| Name | Description |
|---|---|
|
The allowable range for the maximum value of flow temperature. |
|
The allowable range for the minimum value of flow temperature. |
|
The minimum and maximum temperatures which may be selected, dictated by the device. Deprecated The 'allowableRange' field is deprecated. |
|
The min and max flow temperatures currently selected by the user. |
|
Whether weather compensation is enabled or not. |
Example
{
"enabled": true,
"allowableRange": TemperatureRange,
"allowableMinimumTemperatureRange": TemperatureRange,
"allowableMaximumTemperatureRange": TemperatureRange,
"currentRange": TemperatureRange
}Fields
| Name | Description |
|---|---|
|
The account identifier. |
|
The account number of the customer. |
|
The corresponding index (very-low, low, moderate, high, very-high). |
|
Where the customer ranks for carbon intensity within their region. (1=Greenest, 100=Dirtiest). |
|
Achieved unit rate over that week period. |
|
The name given to the GSP as per NG API. |
|
The corresponding total grams of C02 over that week period. |
|
The total consumption over that week period. |
|
The GSP. |
|
Whether or not the customer has full readings within the week period. |
|
If the week is the latest week i.e if the date is 2024-03-06 (Wed) then the latest full week should be 2024-02-26 (Mon). |
|
The meter point identifier. |
|
Corresponding MPAN. |
|
The number of smart meter readings we have within the week period (should be 336). |
|
The last meter reading we have for this customer within week period. |
|
The first meter reading we have for this customer within week period. |
|
The property identifier. |
|
The Monday of the week in question. |
Example
{
"accountId": 1,
"meterPointId": 1,
"weekStart": "2020-01-01T00:00:00.000Z",
"accountNumber": "abc123",
"propertyId": 1,
"mpan": "abc123",
"gspGroupId": "abc123",
"apiGspGroupName": "abc123",
"consumptionKwh": "abc123",
"carbonGrams": 1.0,
"achievedCarbonRate": 1.0,
"achievedCarbonIndex": "VERY_LOW",
"periodStart": "2020-01-01T00:00:00.000Z",
"periodEnd": "2020-01-01T00:00:00.000Z",
"numberPeriods": "abc123",
"hasFullReadings": "abc123",
"isLatestWeek": "abc123",
"achievedCarbonRank": "abc123"
}Fields
| Name | Description |
|---|---|
|
Whatsapp text message body. |
Example
{
"body": "abc123"
}Fields
| Name | Description |
|---|---|
|
The amount won in cents. |
Example
{
"prizeAmount": 1
}Fields
| Name | Description |
|---|---|
|
The integer values that make up the WoF segments. |
Example
{
"segments": [1]
}Fields
| Name | Description |
|---|---|
|
List of winter gas comparison values. |
Example
{
"winterGasComparison": [WinterGasComparisonType]
}Fields
| Name | Description |
|---|---|
|
The comparison group of the data (how we calculated the result). |
|
The properties number of bedrooms. |
|
The measured gas consumption in comparison to group in percentage (can be negative). |
|
First day of the month the data is representing. Eg. '2024-11-01' for November. |
|
The properties postcode areacode. Eg. 'NW'. |
|
The properties postcode outcode. Eg. 'W1W'. |
|
The property type, eg. 'Terraced'. |
Example
{
"periodStart": "2020-01-01T00:00:00.000Z",
"comparisonGroup": "PROPERTY_BEDROOM_AREACODE",
"propertyType": "abc123",
"numberOfBedrooms": 1,
"percentageAboveGroupAvg": 1.0,
"postcodeOutcode": "abc123",
"postcodeAreacode": "abc123"
}WithdrawDunning
The possible errors that can be raised are:
- KT-CT-4178: No account found with given account number.
- KT-CT-11301: Account not in a dunning process for the given path name.
- KT-CT-11302: No active dunning process found.
- KT-CT-11303: Multiple active dunning processes found.
- KT-CT-11306: Withdrawing the dunning process failed.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether the dunning process was withdrawn successfully. |
Example
{
"possibleErrors": [PossibleErrorType],
"withdrawSuccessful": true
}Fields
| Name | Description |
|---|---|
|
The identifier of the work schedule (also known as the 'slug'). |
|
Whether the work schedule is currently open. |
|
Whether today is a public holiday, according to the work schedule. |
|
Name of the work schedule. |
|
The reason the Work Schedule is open or closed. |
Example
{
"identifier": "abc123",
"name": "abc123",
"isOpen": true,
"isPublicHoliday": true,
"openOrClosedReason": "CLOSED_DUE_TO_PUBLIC_HOLIDAY"
}Fields
| Name | Description |
|---|---|
|
Whether or not boost is enabled for a sensor. |
|
Code name of the sensor. |
|
User determined name for a sensor. |
|
Sensor firmware version. |
|
Sensor ID. |
|
Sensor type (Zigbee). |
Example
{
"code": "abc123",
"displayName": "abc123",
"type": "ZIGBEE",
"id": "abc123",
"firmwareVersion": "abc123",
"boostEnabled": true
}Fields
| Name | Description |
|---|---|
|
Whether the zone is calling for heat. |
|
Code name of the zone. |
|
Current operation. |
|
User determined name for a zone. |
|
Default mode, if the zone loses connection to the primary sensor. |
|
Enabled allows zone to heat when |
|
Whether there is demand for heat (True) or not (False). |
|
Previous operation. |
|
Primary sensor for the zone. |
|
All associated sensors and ADCs. |
|
What the zone is used for (heating, water etc). |
Example
{
"code": "WATER",
"zoneType": "HEAT",
"enabled": true,
"displayName": "abc123",
"primarySensor": "abc123",
"currentOperation": ZoneCurrentOperation,
"previousOperation": ZonePreviousOperation,
"callForHeat": true,
"heatDemand": true,
"emergency": true,
"sensors": [SensorConfiguration]
}Fields
| Name | Description |
|---|---|
|
For zones which do not support setpoints, whether the operation was an ON or an OFF. |
|
End time for the current operation. |
|
Heating mode in zone. |
|
Target temperature for a zone, in celsius. |
Example
{
"mode": "ON",
"setpointInCelsius": 1.0,
"action": "ON",
"end": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The transaction ID issued for the zone's name update. |
|
The code of the heat pump controller zone. |
Example
{
"zoneCode": "WATER",
"transactionId": "abc123"
}Fields
| Name | Description |
|---|---|
|
Configuration for a zone. |
|
The heating schedules being used by this zone. |
Example
{
"configuration": ZoneConfiguration,
"schedules": [Schedule]
}Fields
| Name | Description |
|---|---|
|
For zones which do not support setpoints, whether the operation was an ON or an OFF. |
|
Heating mode in zone. |
|
Target temperature for a zone, in celsius. |
Example
{
"mode": "ON",
"setpointInCelsius": 1.0,
"action": "ON"
}Fields
| Name | Description |
|---|---|
|
The telemetry data of a zone. |
|
The heat pump controller zone, i.e. WATER, ZONE1, ZONE2 or AUXILIARY. |
Example
{
"zone": "WATER",
"telemetry": ZoneTelemetry
}Fields
| Name | Description |
|---|---|
|
Whether there is demand for heat (True) or not (False). |
|
Heating mode in zone. |
|
Whether relay is currently switched on (True) or off (False). |
|
Time at which the telemetry was retrieved. |
|
Target temperature for a zone, in celsius. |
Example
{
"setpointInCelsius": 1.0,
"mode": "ON",
"relaySwitchedOn": true,
"heatDemand": true,
"retrievedAt": "2020-01-01T00:00:00.000Z"
}Fields
| Name | Description |
|---|---|
|
The time the temperature was reported. |
|
Value of the temperature in Celsius. |
|
Name of the zone. |
Example
{
"zone": "abc123",
"value": "1.0",
"timestamp": "2020-01-01T00:00:00.000Z"
}Authentication Server
Fields
| Name | Description |
|---|---|
|
The client ID of the application. |
|
The name of the application. |
Example
{
"name": "abc123",
"clientId": "abc123"
}CreateMfaDevice
Create a multi-factor authentication (MFA) device for user.
The possible errors that can be raised are:
- KT-CT-1128: Unauthorized.
- KT-CT-1153: Unable to create MFA device.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Email address to send the MFA code by default. |
|
Phone number to send the MFA code by default. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Secret to setup Time-based One-Time Passwords (TOTP) in your authenticator or password manager manually. |
Example
{
"possibleErrors": [PossibleErrorType],
"deviceEmail": "abc123",
"devicePhone": "abc123",
"totpSecret": "abc123"
}DeleteMfaDevice
Delete a multi-factor authentication (MFA) device for the authenticated user.
The possible errors that can be raised are:
- KT-CT-1150: MFA device not found.
- KT-CT-1154: Unable to delete MFA device.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Flag to indicate if the MFA device has been successfully deleted. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"deviceDeleted": true
}KrakenVersionType
Information about what version of Kraken is being executed by this service.
Fields
| Name | Description |
|---|---|
|
The git commit SHA that is being executed. |
|
The version number that is being executed. |
Example
{
"number": "abc123",
"SHA": "abc123"
}Fields
| Name | Description |
|---|---|
|
The type of MFA device. |
|
Whether the MFA device is confirmed or not. |
Example
{
"deviceType": "abc123",
"isConfirmed": true
}PossibleErrorType
The GraphQL error type for displaying information about GraphQL errors that might be raised from the API.
Fields
| Name | Description |
|---|---|
|
The error code that might be returned from the query/mutation. |
|
The error description that might be returned from the query/mutation. |
|
The error message that might be returned from the query/mutation. |
|
The error type that might be returned from the query/mutation. |
Example
{
"message": "abc123",
"code": "abc123",
"type": "abc123",
"description": "abc123"
}ValidateMfaDevice
Validate multi-factor authentication (MFA) devices for user.
The possible errors that can be raised are:
- KT-CT-1150: MFA device not found.
- KT-CT-1151: MFA device not found.
- KT-CT-1152: Invalid MFA token.
- KT-CT-1155: Enabled backup device is needed.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Flag to indicate if the device has been verified, so it can be used for MFA. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"deviceIsValid": true
}