Objects
Objects in GraphQL represent the resources you can access. An object can contain a list of fields, which are specifically typed.
The example data in the variables and responses below are autogenerated values designed to resemble real inputs. They do not represent actual customer data, and in some cases may require additional validation.
API Site
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": "foreign-loss-knowledge-any-let",
"status": "SCHEDULED",
"apiType": "GRAPHQL",
"startsAt": "guess-general-cultural-spend-check",
"endsAt": "training-test-surface-in-enough"
}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": 87,
"edgeCount": 67
}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": "project-but-different-scene-listen"
}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": "28521409",
"correlationId": "34042585",
"operationName": "night-middle-good-executive-sense",
"inputData": {"key": "value"},
"response": {"key": "value"},
"context": {"key": "value"},
"createdAt": "1979-02-04T07:17:17.214073+00:00"
}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": 48,
"edgeCount": 98
}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": "soon-democratic-another-employee-four"
}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": "34709593",
"eventType": "seem-sister-two-face-fear",
"category": "serve-water-term-top-yes",
"description": "project-room-weight-democratic-deep",
"context": {"key": "value"},
"createdAt": "1986-10-19T15:19:33.748290+00:00"
}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": "14992418",
"body": "sometimes-newspaper-born-hold-should",
"createdAt": "1982-08-13T23:23:19.573925+00:00"
}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": "18944136",
"externalIdentifier": "14627599",
"createdAt": "1982-11-10T21:04:49.729969+00:00",
"channel": "moment-new-health-including-floor",
"category": "ACCOUNT",
"accountNumber": "A-A922659E",
"userId": 1,
"customerContact": "former-nation-around-everyone-law",
"supplyPointIdentifier": "60476903",
"resolutionStatus": "ASSIGNED",
"resolutionType": "AUTOMATIC",
"priority": "LOW",
"apiCalls": [APICallType],
"events": [APIExceptionEventType],
"tags": "MOVE_IN",
"notes": [APIExceptionNoteType],
"operationsTeam": OperationsTeamType,
"context": {"key": "value"},
"keyDate": "2003-05-24",
"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.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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
}Account
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 is_in_hardship 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. |
|
A list of available demand response campaigns in which this account can participate. |
|
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 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. |
|
Check whether the account can be withdrawn. |
|
Data about whether or not an account can modify their payments. |
|
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. |
|
A JSON object containing consent information. |
|
Consents linked to this account. |
|
Contribution agreements for account. |
|
The datetime that the account was originally created. |
|
Debt collection proceedings for account. |
|
The demand response campaigns associated with an account. |
|
The direct debit instructions of the account |
|
The document accessibility preference of the account. |
|
The account events that were recorded for the account. |
|
Files attached to this account. |
|
Check whether the account has an active energy agreement. |
|
Check whether the account has a future energy agreement. |
|
|
|
True if there is an active Hardship Agreement for this account. False otherwise. |
|
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. |
|
Lifeline Agency application. |
|
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 current account overdue balance. |
|
Files attached to this account. |
|
Paginated payment forecasts for an account. Starts from today's date (inclusive). The interface supports |
|
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 instructions of the account. |
|
The payment plans that have been created for this account. |
|
The customer's preferred payment methods. |
|
Current active payment schedule detail of the 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. |
|
Properties linked to the account now and in the future. |
|
|
|
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. |
|
List of billing address lines. |
|
The current status of the account. |
|
Fetch transactions that have taken place on the account. |
|
Unique reference number from a 3rd party enrolment. |
|
Example
{
"id": "61499217",
"number": "avoid-interview-issue-near-player",
"status": "PENDING",
"paymentSchedules": PaymentScheduleConnectionTypeConnection,
"users": AccountUser,
"complaints": ComplaintConnectionTypeConnection,
"brand": "out-protect-bill-morning-morning",
"balance": 26,
"overdueBalance": 45,
"urn": "green-management-system-act-visit",
"billingName": "coach-level-child-age-trouble",
"billingSubName": "by-yeah-summer-forget-anything",
"billingEmail": "time-successful-what-decide-occur",
"billingAddress": "under-see-tonight-present-decide",
"billingAddressLine1": "why-maybe-pass-career-adult",
"billingAddressLine2": "rule-art-paper-general-simple",
"billingAddressLine3": "certain-allow-financial-wide-hair",
"billingAddressLine4": "your-none-ok-case-major",
"billingAddressLine5": "rule-produce-college-since-budget",
"billingAddressPostcode": "nearly-because-performance-those-teach",
"billingCountryCode": "they-debate-over-capital-attack",
"billingDeliveryPointIdentifier": "19254104",
"splitBillingAddress": ["between-around-thought-total-leg"],
"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": 17,
"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": "entire-artist-able-population-play",
"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": "1982-03-12T15:50:10.790046+00:00",
"preferredLanguageForComms": "possible-process-certain-call-Congress",
"consents": ConsentType,
"reminders": AccountReminderConnectionTypeConnection,
"properties": [Property],
"marketSupplyAgreements": AgreementConnection,
"canModifyPayments": CanModifyPaymentsType,
"consentData": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"paymentSchedule": PaymentScheduleType,
"paymentInstructions": PaymentInstructionConnectionTypeConnection,
"paymentPreferences": PaymentPreferenceConnectionTypeConnection,
"availableDemandResponseCampaignsForRegistration": ["American-view-financial-opportunity-wind"],
"demandResponseCampaignParticipants": [DemandResponseCampaignParticipantType],
"canBeWithdrawn": true,
"hasActiveAgreement": true,
"hasFutureAgreement": true,
"lifelineAgencyApplication": LifelineAgencyApplication
}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": 5,
"edgeCount": 68
}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": "simply-dog-there-role-quite"
}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": "fund-law-year-sell-high",
"salesSubchannel": "benefit-name-wall-radio-service",
"dateOfSale": "2014-04-11",
"coolingOffEndDate": "2022-07-10",
"isMigrated": true,
"migrationSource": "truth-kitchen-administration-international-all",
"preferredSsd": "2024-03-11"
}Fields
| Name | Description |
|---|---|
|
Debit details. |
|
Credit details. |
|
Balance transfer ID. |
|
The reason for the balance transfer. |
Example
{
"id": "52800072",
"accountCharge": AccountChargeType,
"accountCredit": AccountCreditType,
"reason": "apply-yes-vote-indicate-director"
}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": 72,
"edgeCount": 85
}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": "thought-bank-glass-it-respond"
}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": "2000-05-29",
"name": "though-board-write-attention-anything",
"slug": "card-daughter-forget-sometimes-letter",
"expiryDate": "1987-06-11",
"startDate": "1970-08-14"
}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": "2013-04-30T07:23:12.188432+00:00"
}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. |
|
JSON metadata containing unstructured data about the account charge. |
|
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": "29634935",
"netAmount": 1,
"grossAmount": 1,
"salesTaxAmount": 1,
"cclAmount": 1,
"reason": "head-natural-phone-prove-score",
"note": "western-idea-way-ball-next",
"displayNote": "government-candidate-main-include-glass",
"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": 8,
"edgeCount": 45
}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": "economic-radio-science-him-save"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"data": {"key": "value"},
"updatedAt": "2011-05-24T23:00:31.709823+00:00"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "97471070",
"grossAmount": 1,
"netAmount": 1,
"salesTaxAmount": 1,
"note": "we-amount-another-thank-share",
"reason": "talk-respond-order-hit-people",
"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": 45,
"edgeCount": 58
}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": "page-also-American-base-seat"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
The ID of the object |
|
Is the file ready for use / downloadable? |
|
Is the file uploaded to S3? |
|
Example
{
"id": "89593209",
"filename": "attention-approach-ago-better-whether",
"category": "impact-throughout-only-during-moment",
"isUploaded": true,
"isReady": true,
"fetchUrl": "doctor-year-later-keep-actually",
"sizeInBytes": 99
}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": 39,
"edgeCount": 27
}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": "eye-each-evening-term-once"
}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": 99,
"totalMonetaryAmount": 30
}Example
{
"body": "senior-important-evidence-turn-democratic",
"isPinned": true,
"createdAt": "2001-10-11T07:08:30.300691+00:00",
"unpinAt": "1985-07-05T11:04:24.164190+00:00"
}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": 45,
"edgeCount": 2
}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": "about-local-business-head-door"
}Fields
| Name | Description |
|---|---|
|
Amount of payment in the currency's minor unit |
|
The billing document identifier to which the payment relates. |
|
|
|
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": "19983577",
"amount": 1,
"paymentDate": "1975-06-04",
"reference": "almost-trade-spring-film-suggest",
"transactionType": "DD_FIRST_COLLECTION",
"status": "SCHEDULED",
"paymentInstruction": PaymentInstructionType,
"surchargeAmount": 73
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Example
{
"namespace": "use-appear-trouble-free-land",
"value": "across-lead-record-medical-popular",
"createdAt": "2012-06-07T10:07:20.363748+00:00",
"updatedAt": "1992-08-18T18:34:19.405764+00:00",
"account": AccountType
}Fields
| Name | Description |
|---|---|
|
Reminder content. |
|
When the reminder is due. |
|
The reminder type. |
Example
{
"reminderType": "AD_HOC",
"content": "sometimes-present-rather-year-someone",
"dueAt": "1975-07-16T18:06:19.161729+00:00"
}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": 45,
"edgeCount": 50
}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": "involve-big-feel-difference-worker"
}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": 58,
"edgeCount": 79
}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": "politics-rock-top-herself-national"
}Fields
| Name | Description |
|---|---|
|
Amount of payment in the currency's minor unit |
|
|
|
The date this payment is scheduled to be debited |
|
The current status of the repayment. |
Example
{
"id": "65480583",
"amount": 1,
"paymentDate": "2021-08-20",
"status": "REQUESTED"
}AccountSearchItemType
A single account search hit
Fields
| Name | Description |
|---|---|
|
The account found. |
|
How well the account matched the search terms. |
Example
{
"account": AccountType,
"score": "1.0"
}AccountUser
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 |
|---|---|
|
Additional user details, if they exist. |
|
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. |
|
This user's address. |
|
List of alternative phone numbers for the account user. |
|
List of businesses that the user has access to through their granted roles. |
|
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. |
|
|
|
Whether this user is active. |
|
Designates whether this user is deceased. |
|
True if user is linked to an account with an active hardship agreement. |
|
A free text field to help identifying the customer (e.g. for a job title). |
|
|
|
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": "72626398",
"number": "quite-condition-author-image-report",
"accounts": AccountInterface,
"givenName": "Paul",
"familyName": "Smith",
"email": "set-suggest-behind-office-stay",
"mobile": "financial-beat-political-side-shoulder",
"landline": "take-trouble-upon-activity-difficult",
"title": "boy-bring-charge-fact-article",
"pronouns": "join-alone-idea-ok-fine",
"isDeceased": true,
"liveSecretKey": "give-reflect-sit-hand-for",
"createdAt": "1995-10-01T01:52:53.879224+00:00",
"portfolios": PortfolioConnectionTypeConnection,
"address": RichAddressType,
"dateOfBirth": "2004-11-28",
"label": "available-care-huge-only-firm",
"isActive": true,
"details": [AccountUserDetailType],
"permissions": [AccountUserPermission],
"displayName": "anyone-relationship-view-wish-situation",
"firstName": "wide-follow-type-off-second",
"lastName": "computer-when-wonder-make-themselves",
"fullName": "theory-data-account-light-after",
"preferredName": "half-science-item-live-garden",
"portfolioId": "91905912",
"portfolioIds": ["97136656"],
"businesses": BusinessConnectionTypeConnection,
"specialCircumstances": SpecialCircumstancesType,
"preferences": AccountUserCommsPreferences,
"landlinePhoneNumber": "alone-blood-question-article-try",
"alternativePhoneNumbers": ["build-individual-all-price-want"],
"hasFamilyIssues": true,
"isInHardship": true,
"accountUserRoles": [AccountUserRoleType],
"portfolioUserRoles": [PortfolioUserRoleType],
"consents": ConsentType,
"paymentMethods": PaymentInstructionConnectionTypeConnection,
"accountUserMeta": AccountUserMeta
}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 the user is opted in to life support call. |
|
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. |
|
The date the SMS opt-in was last changed. |
Example
{
"isOptedInToClientMessages": true,
"isOptedInToOfferMessages": true,
"isOptedInToRecommendedMessages": true,
"isOptedInToUpdateMessages": true,
"isOptedInToThirdPartyMessages": true,
"emailFormat": "TEXT",
"isUsingInvertedEmailColours": true,
"fontSizeMultiplier": 896.28,
"isOptedInMeterReadingConfirmations": true,
"isOptedInToSmsMessages": true,
"preferredHoldMusic": "NO_SONG_PREFERRED",
"smsOptInLastChangeDate": "2018-12-14T15:11:21.831304+00:00",
"isOptedInToLifeSupportCall": 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": AccountUserConnectionTypeEdge,
"totalCount": 39,
"edgeCount": 85
}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": "important-feeling-stuff-cost-present"
}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": "economic-central-difference-trade-local",
"value": "have-success-office-house-have",
"isSensitive": true
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"kanjiGivenName": "Carrie",
"kanjiFamilyName": "Owens",
"kanaGivenName": "David",
"kanaFamilyName": "Martin"
}AccountUserPermission
Holds information about a specific permission.
Fields
| Name | Description |
|---|---|
|
The short name of the permission. |
Example
{
"permission": "drive-share-age-gun-baby"
}AccountUserRoleType
The role a user has in association with one account.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
The account role. |
|
Example
{
"id": "29160224",
"user": AccountUserType,
"account": AccountType,
"role": ADMIN
}ActivateTemplatesOutput
Output type for activating templates.
Fields
| Name | Description |
|---|---|
|
Identifiers of templates that were activated. |
Example
{
"activatedIdentifiers": "feel-soldier-say-worker-politics"
}Fields
| Name | Description |
|---|---|
|
The time the data was reported. |
|
The latest reported activity of the heat pump. |
Example
{
"value": "PRE_HEATING",
"timestamp": "1996-08-21T12:11:23.283874+00:00"
}Fields
| Name | Description |
|---|---|
|
Username of the Actor. |
Example
{
"username": "might-cultural-usually-decade-billion"
}Fields
| Name | Description |
|---|---|
|
The contract actualized. |
Example
{
"contract": Contract
}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-1111: Unauthorized.
- 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
}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]
}AddNoteToInkConversation
The possible errors that can be raised are:
- KT-CT-7612: The Ink conversation was not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The ink conversation note. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"note": InkNote
}Fields
| Name | Description |
|---|---|
|
Add-on details. |
|
Add-on's product rate details. |
Example
{
"addon": AddOnType,
"productRate": ProductRate
}Fields
| Name | Description |
|---|---|
|
Rate band for rates matching this add-on. |
|
Customer-facing long description. |
|
What family does the add-on belong to. |
|
Customer-facing short title. |
Example
{
"band": "whatever-wish-draw-shoulder-million",
"title": "tax-guess-provide-partner-with",
"family": "draw-job-third-similar-whatever",
"description": "claim-yes-color-girl-couple"
}AddPortfolioReference
Add a reference to an existing portfolio.
The possible errors that can be raised are:
- KT-CT-9403: Received an invalid portfolioId.
- KT-CT-9410: Conflicting portfolio reference.
- KT-CT-9408: Invalid portfolio number format.
- KT-CT-9409: Invalid portfolio 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. |
Example
{
"possibleErrors": [PossibleErrorType]
}AddProperty
Add a property to an account.
The possible errors that can be raised are:
- KT-CT-6623: Unauthorized.
- KT-CT-6629: 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 property that was added to the account. |
Example
{
"possibleErrors": [PossibleErrorType],
"property": PropertyType
}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
}AddStorylineToInkConversation
The possible errors that can be raised are:
- KT-CT-7612: The Ink conversation was not found.
- KT-CT-7651: Only one storyline entry can be marked as the root cause.
- 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 storyline that was added to the conversation. |
Example
{
"possibleErrors": [PossibleErrorType],
"storyline": InkStoryline
}AddUserToPortfolio
The possible errors that can be raised are:
- KT-CT-5461: Invalid role code.
- KT-CT-5462: Invalid user number format.
- KT-CT-5463: Unauthorized.
- KT-CT-9407: Unauthorized.
- KT-CT-9408: Invalid portfolio number format.
- 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 |
|---|---|
|
Country code of billing address. |
|
Line 1 of address. |
|
Line 2 of address. |
|
Line 3 of address. |
|
Line 4 of address. |
|
Line 5 of address. |
|
Postcode of billing address. |
Example
{
"line1": "mention-including-general-control-small",
"postcode": "main-former-base-way-out",
"countryCode": "office-himself-glass-technology-wish",
"line2": "street-information-process-range-support",
"line3": "house-discuss-style-arm-hair",
"line4": "tend-would-degree-allow-just",
"line5": "fear-suffer-low-approach-would"
}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": "have-none-us-instead-with",
"bucket": "its-range-and-personal-physical",
"fields": {"key": "value"},
"preSignedUrl": "already-debate-blood-road-subject"
}AffiliateLinkType
Affiliate link for the organization.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
Affiliate Organisation. |
|
|
|
Example
{
"id": "39315385",
"organisation": AffiliateOrganisationType,
"subdomain": "financial-imagine-listen-wall-simply",
"trainingStatus": "NOT_APPLICABLE",
"isBusiness": true,
"contactName": "without-pressure-audience-pass-young",
"contactEmail": "according-west-reality-newspaper-race",
"landingUrl": "suffer-by-concern-born-similar"
}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": "65168626",
"name": "check-culture-together-international-serve",
"contactEmail": "foreign-church-must-energy-perform",
"canRenewTariffs": true,
"defaultAccountType": "BUSINESS",
"allowAlternativePaymentMethods": true,
"canRegisterBusinessMeterPoints": true,
"canRegisterPortfolioAccounts": true,
"canRegisterCustomersWithoutEmailAddress": true,
"canUseIvrSupportApi": true,
"skipMeterPointAddressValidation": true,
"salesChannel": "DEFAULT_SUPPLY",
"salesChannelCode": "central-answer-land-receive-you",
"isFieldSalesOnlyProduct": true
}AffiliateSessionType
A tracked session for the affiliate link.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Affiliate Link. |
|
|
|
Example
{
"id": "85209173",
"ipAddress": "surface-energy-per-newspaper-local",
"userAgent": "training-a-final-either-art",
"queryParams": {"key": "value"},
"link": AffiliateLinkType
}Fields
| Name | Description |
|---|---|
|
The ID of the agent call center status. |
|
The ID of the most recent call handled by the agent. If the agent status is BUSY then this will be the ID of the current call. |
|
The current status of the agent in the call center. |
|
The timestamp when the status was last updated. |
Example
{
"id": "34237875",
"status": "month-ground-pretty-as-person",
"updatedAt": "2003-03-27T01:42:08.055727+00:00",
"mostRecentCallId": 10877614
}Fields
| Name | Description |
|---|---|
|
List of add-on rates on the agreement. |
|
The datetime the agreement was entered. |
|
The datetime the agreement was terminated. |
|
The ID of the agreement. |
|
Whether the agreement is revoked. |
|
The agreement additional params. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The deadline datetime for rescinding the agreement. |
|
The start datetime of the agreement. |
|
The end datetime of the agreement. |
Example
{
"id": 57991133,
"product": Product,
"monthlyStandingCharge": "1.0",
"netMonthlyStandingCharge": "1.0",
"standingChargeGrossRateInformation": [GrossRateInformation],
"unitRatePerKwh": "1.0",
"unitRateGrossRateInformation": [GrossRateInformation],
"unitRateInformation": UnitRateInformation,
"estimatedMonthlyBillInEuros": "1.0",
"estimatedAnnualConsumption": 67,
"validFrom": "1978-04-12T12:47:15.861103+00:00",
"validTo": "1971-07-11T14:48:07.255216+00:00",
"agreedAt": "2018-08-24T19:35:25.016924+00:00",
"isRevoked": true,
"isActive": true,
"isTerminated": true,
"isAffectedByPriceBrake": true,
"earliestCancellationDate": "1993-12-06",
"unitRateForecast": [UnitRateForecastType]
}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": 99,
"edgeCount": 60
}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": "act-improve-bag-action-state"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
List of tag names associated with this agreement rollover. |
|
Example
{
"id": "53918330",
"number": "method-family-clearly-easy-later",
"agreement": CommonAgreementType,
"rolledOnTo": CommonAgreementType,
"quoteRequests": MarketSupplyQuoteRequestType,
"rolloverType": "DEFAULT",
"expectedSendDate": "2005-07-13",
"status": "PENDING",
"params": {"key": "value"},
"failureReason": "star-show-me-charge-the",
"actualSendDate": "1974-09-18",
"suppressComms": true,
"tags": ["experience-as-between-fish-wish"],
"createdAt": "2024-11-15T01:25:49.721659+00:00",
"updatedAt": "2004-01-24T02:17:46.800617+00:00"
}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": 11942112,
"transactionType": "CREDIT",
"transactionAmount": 72,
"allocationAmount": 56,
"allocationReason": "suddenly-computer-child-natural-today"
}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": 37,
"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": "60824707",
"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
}AmperageChangeInitiated
AmperageChange was successfully initiated.
Fields
| Name | Description |
|---|---|
|
The message to display to the user on amperage change initiation. |
Example
{
"message": "listen-organization-simply-require-laugh"
}Fields
| Name | Description |
|---|---|
|
The requested change date provided by the customer. |
|
The requested amperage value to change to, provided by the customer. |
Example
{
"requestedAmperageValue": 66,
"amperageChangeDate": "1980-04-23"
}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": "century-figure-hundred-capital-focus",
"horizontalAlignment": "START",
"accessibilityHidden": true,
"accessibilityLabel": "radio-hotel-people-machine-month",
"id": "96489606",
"typename": "thank-seek-final-about-small"
}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": 35,
"edgeCount": 21
}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": "hundred-imagine-machine-anyone-skin"
}AnnualStatementType
Annual statements that are sent to the account. They summarize important information about usage and tariffs.
Example
{
"periodStartsAt": "2025-06-16T23:10:14.013649+00:00",
"periodEndsAt": "1994-07-26T07:01:53.240158+00:00",
"id": "18031970",
"pdfUrl": "window-write-one-individual-necessary"
}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. |
|
ID for the annulment billing document. |
|
URL to the PDF of the annulment. |
Example
{
"id": 96132316,
"annulledBillingDocumentId": 63285276,
"firstIssued": "1970-09-15T12:34:04.147406+00:00",
"pdfUrl": "many-you-politics-game-fine"
}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": 91,
"edgeCount": 51
}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": "son-bad-president-mission-his"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Post town |
|
County |
|
|
|
|
|
|
|
|
|
|
|
The location accuracy level in meters |
|
|
|
|
|
A list of outcomes associated with the app session. |
|
|
|
|
|
|
|
|
|
|
|
Example
{
"startedAt": "2011-11-05T19:55:08.396199+00:00",
"stoppedAt": "2010-12-03T13:27:52.781230+00:00",
"addressLine1": "yeah-away-any-miss-animal",
"addressLine2": "family-ask-tend-response-source",
"addressLine3": "bad-policy-act-entire-parent",
"addressLine4": "southern-within-model-too-four",
"addressLine5": "nor-age-organization-indeed-rest",
"id": "9c7b2fc6-3578-4b89-aaab-ae42da005e1f",
"link": AffiliateLinkType,
"isArchived": true,
"postcode": "close-many-beautiful-tax-different",
"account": AccountType,
"locationAt": "1971-01-02T12:46:23.304078+00:00",
"locationHorizontalAccuracy": 72,
"locationLatitude": "1.0",
"locationLongitude": "1.0",
"salesMode": "DOOR",
"type": AppSessionType,
"createdAt": "2018-11-09T02:45:09.542258+00:00",
"updatedAt": "1982-10-10T15:58:54.443801+00:00",
"outcomes": [OutcomeType]
}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-3973: Repayment request is not in a state to be approved.
- 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": "support-whether-once-since-type",
"isPaused": true
}AssignInkBucket
The possible errors that can be raised are:
- KT-CT-7612: The Ink conversation was not found.
- KT-CT-7613: The Ink bucket was not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The bucket that the conversation will be assigned to. |
|
The conversation that will be assigned to the bucket. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"conversation": InkConversation,
"bucket": InkBucket
}Fields
| Name | Description |
|---|---|
|
The ID of the assigned user. |
|
The username of the assigned user. |
Example
{
"id": "35235064",
"username": "authority-let-American-total-animal"
}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": "occur-break-card-head-coach",
"activeFrom": "1976-04-07",
"activeTo": "1989-04-10"
}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-11216: Invalid extra_details for associated item type.
- 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": "be-child-collection-think-what",
"itemId": "42325697"
}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": "73066636",
"filename": "sense-strategy-clearly-wonder-body",
"temporaryUrl": "likely-model-goal-indeed-for"
}Fields
| Name | Description |
|---|---|
|
The app session associated with this audio recording. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "820b56a1-5c93-40c0-88d4-3571597e36f8",
"appSession": AppSessionType,
"contentType": "forward-alone-church-care-clearly",
"duration": 642.87,
"fileSize": 45,
"startedAt": "2022-12-09T23:21:31.501002+00:00",
"stoppedAt": "2007-04-06T16:13:23.029404+00:00",
"s3Bucket": "there-whom-generation-on-visit",
"s3Key": "subject-street-check-authority-happy",
"createdAt": "2005-12-21T13:04:11.733611+00:00",
"updatedAt": "1999-10-01T12:52:23.240779+00:00"
}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": "73591288",
"redirectUri": "level-so-single-become-lay",
"authorizationUri": "security-view-himself-section-family"
}Fields
| Name | Description |
|---|---|
|
The client ID of the application. |
|
The name of the application. |
Example
{
"name": "force-probably-room-admit-hour",
"clientId": "68580624"
}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-9219: Loyalty points user not found.
- 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": 39,
"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": "kitchen-training-himself-now-become",
"id": "10828078",
"typename": "drug-who-fine-bar-who",
"eventId": "99114592",
"params": BackendScreenParam
}BackendScreenParam
A key-value pair (both Strings) which is passed as a parameter to a screen.
Example
{
"key": "world-dinner-product-skill-pattern",
"value": "assume-oil-really-environmental-cell"
}Fields
| Name | Description |
|---|---|
|
Indicates whether the provided bank details are valid. |
|
Provides additional information about validation result. |
Example
{
"areValid": true,
"message": "central-from-yes-father-certain"
}Fields
| Name | Description |
|---|---|
|
Account that has switched to bank transfer payment method. |
Example
{
"accountNumber": "A-FB7DD7B9"
}BespokeRateConfigurationType
The BespokeRateConfiguration 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 schedules for the bespoke rate configuration. |
|
The type of the term. |
Example
{
"type": "significant-current-job-specific-good",
"displayName": "phone-buy-animal-read-teach",
"description": "herself-hear-occur-contain-bank",
"identifier": "70923358",
"isVariable": true,
"schedules": [BespokeRateScheduleType]
}BespokeRateItemType
Item for the BespokeRateConfiguration term.
Fields
| Name | Description |
|---|---|
|
The price per unit for the bespoke rate item. |
|
The rate specification code for the bespoke rate item. |
|
The variant profile for the bespoke rate item. |
Example
{
"pricePerUnit": "1.0",
"rateSpecificationCode": "early-ten-wonder-most-no",
"variantProfile": VariantProfile
}BespokeRateScheduleType
Schedule for the BespokeRateConfiguration term.
Fields
| Name | Description |
|---|---|
|
The items for the bespoke rate schedule. |
|
The product code for the bespoke rate schedule. |
|
The external identifier of the supply point this schedule targets. |
|
The datetime the schedule of bespoke rates is valid from. |
|
The datetime the schedule of bespoke rates is valid to. |
Example
{
"items": [BespokeRateItemType],
"productCode": "whose-surface-religious-often-huge",
"validFrom": "2016-10-08T08:07:14.246528+00:00",
"validTo": "2018-06-21T04:47:10.897859+00:00",
"supplyPointIdentifier": "35877116"
}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. |
|
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. |
|
Supporting information about this charge (if any is available). |
|
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": "12138918",
"postedDate": "2012-02-17",
"createdAt": "1989-06-04T05:08:32.548116+00:00",
"amounts": TransactionAmountType,
"title": "card-fly-bank-agent-article",
"note": "employee-court-my-wait-free",
"reasonCode": "middle-officer-design-bank-business",
"consumption": Consumption,
"detail": ChargeDetail
}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": 14,
"edgeCount": 34
}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": "result-six-north-my-word"
}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": "45876875",
"postedDate": "1975-01-15",
"createdAt": "2007-01-17T06:44:45.528652+00:00",
"amounts": TransactionAmountType,
"title": "realize-first-throw-go-weight",
"note": "defense-then-protect-always-today",
"reasonCode": "language-figure-next-space-serve"
}BillDueDateType
Represents bill due dates 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": "hold-company-situation-sound-yourself",
"displayName": "much-act-fight-pattern-so",
"description": "population-side-remember-section-east",
"identifier": "19675005",
"isVariable": true
}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": "56908177",
"postedDate": "2022-08-22",
"createdAt": "1981-03-21T04:15:24.746414+00:00",
"amounts": TransactionAmountType,
"title": "loss-station-production-perhaps-whom",
"note": "move-class-hour-opportunity-fear",
"reasonCode": "others-produce-trip-effect-just"
}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": "34714012",
"postedDate": "2025-02-20",
"createdAt": "1978-10-10T09:35:21.215652+00:00",
"amounts": TransactionAmountType,
"title": "image-foot-pay-cause-subject",
"note": "though-music-result-positive-type",
"reasonCode": "sometimes-evening-use-myself-rule"
}BillRepresentationConnectionTypeConnection
A connection that can provide links to the representations of a 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": BillRepresentationConnectionTypeEdge,
"totalCount": 14,
"edgeCount": 69
}BillRepresentationConnectionTypeEdge
A Relay edge containing a BillRepresentationConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": BillRepresentationType,
"cursor": "economy-compare-plan-interest-trade"
}BillRepresentationType
representations are associated with a bill files and can be used to provide additional information to the customer.
Fields
| Name | Description |
|---|---|
|
The type of representation. |
|
The name of the file. |
|
The |
|
The expiry datetime field of the temporary URL. |
|
The version of the representation. |
Example
{
"code": "would-after-must-left-story",
"version": 47,
"temporaryUrl": "owner-certainly-computer-act-right",
"temporaryUrlExpiresAt": "2002-12-05T15:15:14.965390+00:00",
"filename": "specific-bar-area-certainly-stop"
}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": 3,
"edgeCount": 33
}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": "despite-scientist-under-quality-audience"
}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": 21,
"edgeCount": 42
}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": "field-lay-add-stock-research"
}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": "national-data-everyone-claim-course",
"temporaryUrlExpiresAt": "2001-05-28T15:04:28.226967+00:00",
"filename": "finally-assume-take-maybe-dinner"
}BillingDocumentIssuanceFrequencyType
Represents billing document issuance frequency to be applied during a contract.
Fields
| Name | Description |
|---|---|
|
The description of the term. |
|
The display name of the term. |
|
Billing frequency. |
|
The identifier of the term. |
|
Whether the term can be amended after creation. |
|
Multiplier applied to the frequency. |
|
Start day of the billing period. |
|
Start month of the billing period. |
|
The type of the term. |
Example
{
"type": "word-rich-that-foot-offer",
"displayName": "such-type-full-while-forget",
"description": "collection-better-lawyer-child-a",
"identifier": "32724125",
"isVariable": true,
"frequency": "capital-new-deal-technology-toward",
"periodStartDay": 100,
"periodStartMonth": 74,
"multiplier": 98
}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": "1997-07-09",
"expectedAmount": 70,
"remainingAmount": 51,
"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": 92,
"periodLength": "MONTHLY",
"periodLengthMultiplier": 45,
"isFixed": true,
"currentBillingPeriodStartDate": "1986-06-16",
"currentBillingPeriodEndDate": "2018-01-14",
"nextBillingDate": "1990-08-28"
}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": "13253421",
"repaymentIntervention": RepaymentInterventionType
}BusinessConnectionTypeConnection
Paginator of Businesses
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": BusinessConnectionTypeEdge,
"totalCount": 13,
"edgeCount": 34
}BusinessConnectionTypeEdge
A Relay edge containing a BusinessConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": BusinessType,
"cursor": "everything-necessary-consumer-read-focus"
}Fields
| Name | Description |
|---|---|
|
The key of the business detail. |
|
The value of the business detail. |
Example
{
"key": "heavy-nature-idea-town-individual",
"value": "audience-move-land-film-goal"
}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": "98933308",
"segment": SegmentType,
"startAt": "1971-08-14T23:04:11.271628+00:00",
"endAt": "1977-04-11T16:57:31.382108+00:00"
}Fields
| Name | Description |
|---|---|
|
The billing address of the business. |
|
The company type of a business account. |
|
The details of the business. |
|
The business ID. |
|
Company name in Kana. |
|
Company name in Kanji. |
|
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 sectors the business operates in. |
|
The segment this business is assigned to. |
Example
{
"id": "25134853",
"name": "security-door-thousand-middle-reach",
"number": "gas-world-wish-animal-glass",
"businessType": "SOLE_TRADER",
"sectors": None,
"details": [BusinessDetailType],
"billingAddress": RichAddressType,
"legalAddress": RichAddressType,
"linkedAccountNumber": "A-DBB87AD5",
"linkedAccountNumbers": "88247621",
"segmentName": "economy-various-upon-teach-until",
"paymentMethods": PaymentInstructionConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
The key of the call metadata item. |
|
The value of the call metadata item. |
Example
{
"key": "method-own-summer-able-include",
"value": "exist-according-case-executive-trip"
}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": 35,
"edgeCount": 7
}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": "television-site-local-appear-deal"
}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": "35828793",
"name": "scene-answer-give-well-health",
"isActive": true
}Fields
| Name | Description |
|---|---|
|
Whether or not the account can amend payments. |
|
Whether or not the account can cancel payments. |
Example
{
"canAmendPayments": true,
"canCancelPayments": true
}CancelAmperageChangeRequest
Cancel an amperage change request.
This mutation is used for cancelling amperage change requests by organizations.
The possible errors that can be raised are:
- KT-CT-4501: Unauthorized.
- KT-JP-4501: Unauthorized.
- KT-JP-4502: Unauthorized.
- KT-JP-4511: Invalid data.
- KT-JP-4520: Unable to process request.
- KT-JP-4515: Amperage change process not found.
- KT-JP-4516: Unable to cancel amperage change process.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Success message. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": "step-year-consumer-stuff-improve"
}CancelMoveOut
The possible errors that can be raised are:
- KT-JP-4537: Move out cancel input data is invalid.
- KT-JP-4501: Unauthorized.
- KT-JP-4536: Move out active process not found.
- KT-JP-4535: Move out cancel cannot self-service.
- KT-JP-4101: Unauthorized.
- KT-JP-4520: Unable to process request.
- KT-JP-4538: Move out process not withdrawable.
- 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. |
|
Supply point identification number. |
Example
{
"possibleErrors": [PossibleErrorType],
"spin": "far-fly-interest-positive-skill"
}CancelOnSiteJobsAppointment
The possible errors that can be raised are:
- KT-CT-13001: Appointment does not exist.
- KT-CT-13017: Appointment cancellation not supported.
- KT-CT-13018: Unable to record cancellation_category/cancellation_sub_category.
- KT-CT-13019: Vendor not found.
- KT-CT-13053: Failed to cancel the appointment with the agent.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The Appointment that was cancelled. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"onSiteJobsAppointment": OnSiteJobsAppointmentType
}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": "58152339",
"status": "REQUESTED"
}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": "include-some-return-vote-yet",
"id": "37964664",
"typename": "health-drug-agent-floor-though",
"items": CardItemType
}Fields
| Name | Description |
|---|---|
|
The list of cards. |
|
Unique identifier of the object. |
|
The name of the object's type. |
Example
{
"id": "97043074",
"typename": "history-game-prepare-card-whatever",
"cards": CardComponentType
}CatalogProductType
Represents a product in the catalog.
Fields
| Name | Description |
|---|---|
|
Unique identifier of the component. |
|
Customer-facing description of the product. |
|
Customer-facing name of the product. |
|
Unique identifier of the product. |
|
Internal name of the product. |
|
The market the product is associated with. |
|
The type of product. |
|
Tags associated with this product for classification. |
Example
{
"identifier": "70736571",
"internalName": "sense-rule-special-source-other",
"customerName": "debate-remember-floor-responsibility-go",
"customerDescription": "hotel-themselves-within-attorney-argue",
"code": "return-win-for-consider-community",
"marketName": "improve-yes-of-common-consumer",
"sourceProductType": "SUPPLY",
"tags": [TagType]
}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. |
|
List of characteristic overrides. |
|
The type of the term. |
Example
{
"type": "speech-stuff-gun-because-water",
"displayName": "democratic-year-rise-side-run",
"description": "choose-though-their-wall-even",
"identifier": "33483507",
"isVariable": true,
"overrides": CharacteristicOverrideType
}CharacteristicOverrideType
An override for a specific characteristic.
Fields
| Name | Description |
|---|---|
|
The characteristic being overridden. |
|
The value to override the characteristic with. |
|
Optional product code. If specified, the override applies only to this product. |
Example
{
"characteristic": CharacteristicType,
"overrideValue": CharacteristicValueType,
"productCode": "figure-alone-his-pay-learn"
}CharacteristicType
A characteristic associated with a product.
Fields
| Name | Description |
|---|---|
|
The code of the characteristic. |
|
The description of the characteristic. |
|
The name of the characteristic. |
|
The possible values for the characteristic (can be strings or integers). |
Example
{
"code": "garden-particular-building-since-interview",
"name": "board-left-foot-try-owner",
"description": "understand-big-worker-your-seem",
"values": CharacteristicValueType
}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. |
|
Supporting information about this charge (if any is available). |
|
Returns True if the transaction is linked with a statement. |
|
Unique identifier for the transaction. |
|
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. |
|
|
|
The line items that make up the charge. |
|
Returns the note field value for the transaction, which contains additional info. |
|
Date when the transaction was posted to the account. |
|
The reading ID associated with the charge. |
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Human-readable title describing the transaction. |
Example
{
"id": "81606063",
"postedDate": "1986-09-08",
"createdAt": "1981-07-19T21:25:27.554946+00:00",
"accountNumber": "A-5CF9DDF3",
"amount": 55,
"amounts": TransactionAmountType,
"balanceCarriedForward": 81,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "organization-cold-sort-company-management",
"billingDocumentIdentifier": "25438031",
"statementId": "33198671",
"isReversed": true,
"hasStatement": true,
"note": "action-or-bar-notice-girl",
"reasonCode": "month-those-ground-little-series",
"consumption": Consumption,
"detail": ChargeDetail
}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": 22408635,
"model": "hand-simply-him-drop-bag",
"powerInKw": "1.0",
"amperage": 34,
"isIntegrationLive": true,
"integrationStatus": "INTERNAL_TESTING"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "never-all-improve-should-entire",
"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": "detail-it-next-democratic-nation",
"display": "natural-serve-fine-strategy-discussion",
"isDeprecated": true,
"isTaxExempt": true,
"isHidden": true,
"group": "hundred-try-stock-leg-various"
}Fields
| Name | Description |
|---|---|
|
The gross amount charged. |
|
The line items for the charge. |
|
The sales tax amount charged. |
Example
{
"grossAmount": 1,
"salesTaxAmount": 1,
"lineItems": [LineItemType]
}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": 80,
"edgeCount": 37
}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": "recent-spring-stuff-agency-author"
}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-07-18",
"periodEnd": "1974-06-10",
"charge": 55
}CheckResultType
GraphQL type for check result.
Fields
| Name | Description |
|---|---|
|
Additional context about the check. |
|
Name of the check. |
|
Status of the check. |
Example
{
"name": "traditional-area-particularly-miss-administration",
"status": "PASSED",
"context": "tend-public-light-perform-through"
}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": "than-go-six-sing-soon",
"id": "37887436",
"typename": "religious-read-article-whole-two",
"accessibilityHidden": true,
"accessibilityLabel": "position-professional-next-movie-business"
}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
}CloseInkLiveChatConversation
The possible errors that can be raised are:
- KT-CT-7616: Not yet implemented.
- KT-CT-7643: The Live Chat was not found.
- KT-CT-7644: Ink Live Chat conversation not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The live chat conversation. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"liveChatConversation": InkLiveChatConversation
}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
}CollateralRequiredType
Represents required collaterals to be applied in a contract.
Fields
| Name | Description |
|---|---|
|
Amount set up as collateral as condition for account creation. |
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Type of interest policy of required collateral. |
|
Whether the term is variable. |
|
Reason for setting up required collateral. |
|
The type of the term. |
Example
{
"type": "animal-ball-school-imagine-sound",
"displayName": "artist-boy-court-certainly-laugh",
"description": "continue-would-degree-clear-room",
"identifier": "58719642",
"isVariable": true,
"amount": 65,
"reason": "serve-agency-and-with-center",
"interestPolicy": "soldier-statement-down-television-certain"
}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-5713: Payment instruction is not usable.
- 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": "2006-05-19"
}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
}Fields
| Name | Description |
|---|---|
|
The description of the collection. |
|
The fields of the collection. |
|
The name of the collection. |
|
The order of the collection. |
Example
{
"name": "appear-year-hear-figure-democratic",
"description": "likely-bank-animal-because-Democrat",
"order": 81,
"fields": [FunnelField]
}CollectionProcessDetailsType
Collection process details type
Fields
| Name | Description |
|---|---|
|
Items associated to the collection process. |
|
The collection process record number. |
|
The type of the collection process (ACCOUNT, LEDGER, or BILLING_DOCUMENT). |
|
What kind of completion happened. |
|
The active status of the collection process. |
|
The completion status of the collection process. |
|
The pause status of the collection process. |
|
Total number of days collection process were on pause. |
|
The identifier of the target object (account number, ledger number, or billing document ID) based on the collection process type. |
Example
{
"collectionProcessRecordNumber": "box-writer-all-imagine-success",
"isPaused": true,
"isComplete": true,
"isActive": true,
"completionType": "kitchen-animal-natural-others-write",
"associatedItems": [CollectionProcessRecordAssociatedItemType],
"pausedDays": 87,
"collectionProcessType": "ACCOUNT",
"targetObjectIdentifier": "43756129"
}CollectionProcessPauseStatusRecord
Collection process pause record
Fields
| Name | Description |
|---|---|
|
Collection process pause name. |
|
Start of pause period. |
|
Reason for pausing. |
|
End of pause period. |
|
Reason for ending pause period. |
Example
{
"name": "figure-serious-approach-Mr-from",
"reason": "meet-include-nation-Mr-because",
"pausedAt": "1994-07-23T01:05:19.589558+00:00",
"resumedAt": "1976-08-05T05:39:00.755027+00:00",
"resumedReason": "realize-thing-policy-center-customer"
}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": "quite-phone-next-second-exist",
"itemReference": "bag-audience-enter-film-late",
"occurredAt": "1997-09-30T08:47:37.507799+00:00",
"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": "46493475",
"billType": "STATEMENT",
"fromDate": "1994-02-12",
"toDate": "1993-09-22",
"temporaryUrl": "successful-hand-seat-quickly-pay",
"issuedDate": "2009-10-13",
"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
}Fields
| Name | Description |
|---|---|
|
|
|
The datetime the agreement was entered. |
|
The datetime the agreement was terminated. |
|
The characteristic values associated with the agreement. |
|
|
|
Whether the agreement is currently active. |
|
Whether the agreement is revoked. |
|
The product associated with the agreement. |
|
The deadline until which the customer is allowed to rescind this agreement. If it is null, rescission is not permitted. |
|
The agreement's supply point. |
|
|
|
|
|
Example
{
"id": "77387289",
"validFrom": "2008-12-02T18:47:59.012924+00:00",
"validTo": "1995-06-12T03:11:55.863148+00:00",
"agreedAt": "2004-12-11T17:55:04.816265+00:00",
"terminatedAt": "2003-12-17T09:48:52.744702+00:00",
"supplyPoint": SupplyPointType,
"product": SupplyProductType,
"isActive": true,
"agreedFrom": "1993-04-09T02:20:22.680279+00:00",
"agreedTo": "1988-05-04T07:21:40.866336+00:00",
"isRevoked": true
}CommonError
A Common 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": "their-class-born-reality-nice",
"field": "through-plant-skin-blood-do"
}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": 90,
"edgeCount": 32
}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": "record-the-bit-suddenly-beyond"
}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": 95,
"edgeCount": 17
}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": "they-career-certain-camera-value"
}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": "black-require-local-different-son",
"actionTaken": "lawyer-near-teach-real-listen",
"status": "office-risk-decade-happy-face",
"createdAt": "1971-08-01T07:10:42.812940+00:00",
"mobile": "people-who-want-sea-commercial",
"email": "shake-notice-project-really-week",
"landline": "question-kind-wear-opportunity-ahead",
"preferredCommunicationMethod": "father-image-individual-involve-common",
"summary": "movie-talk-court-avoid-let"
}Fields
| Name | Description |
|---|---|
|
Complaint Assignee. |
|
Complaint contacts. |
|
Complaint creation date. |
|
|
|
Complaint resolution date. |
|
Complaint subtype. |
|
Complaint type. |
Example
{
"id": "80259997",
"contacts": ComplaintContactConnectionTypeConnection,
"type": "occur-doctor-Republican-hold-away",
"subtype": "billion-home-TV-partner-new",
"creationDate": "1992-01-23",
"resolutionDate": "2022-01-27",
"assigneeId": "41946191"
}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
}CompleteSelectVehicleOrChargePointForSmartFlexOnboarding
Complete the select vehicle or charge point 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
}CompleteStandalonePayment
Completes an initiated standalone payment.
The possible errors that can be raised are:
- KT-CT-3822: Unauthorized.
- KT-CT-3823: Unauthorized.
- KT-CT-3974: Unauthorized.
- KT-CT-3975: Unable to complete standalone payment.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The completed standalone payment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payment": CompleteStandalonePaymentOutput
}CompleteStandalonePaymentOutput
Result of the complete standalone payment operation.
Fields
| Name | Description |
|---|---|
|
The status of the standalone payment. |
Example
{
"status": "CLEARED"
}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
}CompleteUserInputRequiredForSmartFlexOnboarding
Complete the UserInputRequired 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": "house-member-last-explain-effect",
"id": "68636864",
"typename": "most-dream-follow-do-special",
"name": "production-edge-measure-top-budget",
"refreshFrequency": 62,
"screenData": "set-talk-travel-approach-entire",
"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
}Fields
| Name | Description |
|---|---|
|
The code of the consent type. |
|
The value to update the consent to. |
Example
{
"code": "hot-condition-total-free-enough",
"value": "fish-fear-the-message-through"
}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": "last-maybe-former-lose-me",
"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": "us-government-appear-identify-must",
"description": "professional-live-budget-page-least",
"name": "section-special-more-election-describe",
"defaultValue": "ACCEPTED"
}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": 88,
"edgeCount": 86
}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": "quite-security-must-audience-camera"
}Fields
| Name | Description |
|---|---|
|
End date of the consumption period. |
|
Amount of energy or resource consumed. |
|
Start date of the consumption period. |
|
Supply charge amount in minor currency units. |
|
|
|
Cost for the consumption usage in minor currency units. |
Example
{
"startDate": "1973-11-13",
"endDate": "1995-09-16",
"quantity": "1.0",
"unit": "kWh",
"usageCost": 94,
"supplyCharge": 50
}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": 46,
"edgeCount": 54
}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": "admit-weight-all-share-only"
}Fields
| Name | Description |
|---|---|
|
Charges grouped per displayed period. |
|
Name of the market the charges are for. |
Example
{
"marketName": "day-current-account-five-trade",
"charges": ChargesBreakdownConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
The price per unit including tax. |
|
The step end for the consumption tier for the charge. |
|
The step start for the consumption tier for the charge. |
Example
{
"pricePerUnitIncTax": "1.0",
"stepStart": 62,
"stepEnd": 8,
"band": "box-focus-agreement-spend-whatever"
}Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per kWh without tax. |
|
Price per kWh including tax. |
|
Region of operation. |
|
Time of use label for the rate. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "pretty-support-better-traditional-thank",
"regionOfOperation": "before-though-main-meeting-group",
"band": "total-marriage-world-song-front",
"validFrom": "1982-04-04T14:44:12.099809+00:00",
"validTo": "2016-03-09T11:44:30.757990+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 90,
"pricePerUnitIncTax": "1.0",
"timeOfUse": "note-worry-figure-show-offer"
}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": "88947620",
"title": "campaign-home-property-worker-treatment",
"party": ContractParty,
"subject": [AccountType],
"status": "REVOKED",
"validFrom": "1984-06-21T15:59:57.095245+00:00",
"validTo": "2017-09-02T17:40:34.409160+00:00",
"signedAt": "2006-06-20T15:23:46.317817+00:00",
"cancelledAt": "1985-10-25T11:30:37.785756+00:00",
"lifecycle": ContractVersion,
"terms": TermInterface
}Fields
| Name | Description |
|---|---|
|
The unit of the contract capacity. |
|
The value of the contract capacity. |
Example
{
"value": "1.0",
"unit": "KW"
}ContractCreationContext
Represents a version of a contract with its effective date.
Fields
| Name | Description |
|---|---|
|
The confirmed validity period for the associated contract. |
|
The requested validity period for the associated contract. |
Example
{
"requestedValidityPeriod": ValidityPeriod,
"confirmedValidityPeriod": ValidityPeriod
}ContractCreationJourneyType
Represents a Contract Creation Journey.
Fields
| Name | Description |
|---|---|
|
The context data for the contract creation journey. |
|
The details of the associated contract. |
|
The type of the contract journey. |
|
The number of the contract journey. |
|
The order reference associated with the contract journey. |
|
The date and time when the contract journey was requested. |
|
The status of the contract journey. |
Example
{
"number": "develop-close-growth-involve-thus",
"status": "IN_PROGRESS",
"contractDetails": ContractDetails,
"journeyType": "CONTRACT_CREATION",
"requestedAt": "1975-04-22T04:00:55.913470+00:00",
"orderReference": "get-think-top-important-truth",
"context": ContractCreationContext
}ContractDetails
Details of a contract excluding terms.
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. |
|
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": "40334033",
"title": "doctor-president-sometimes-positive-also",
"party": ContractParty,
"subject": [AccountType],
"status": "REVOKED",
"validFrom": "1985-05-23T15:41:31.930376+00:00",
"validTo": "1987-10-19T10:10:09.593074+00:00",
"signedAt": "2012-02-09T07:19:09.808551+00:00",
"cancelledAt": "2004-11-29T10:41:08.825511+00:00",
"lifecycle": ContractVersion
}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": "memory-human-book-total-involve",
"displayName": "hour-go-low-program-level",
"description": "risk-pressure-mention-size-somebody",
"identifier": "85357201",
"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": "this-will-brother-carry-recent"
}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": 26,
"effectiveFrom": "2009-07-09T21:56:18.649533+00:00"
}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 periods for the contracted volume configuration. |
|
The type of the term. |
Example
{
"type": "however-several-reason-exist-program",
"displayName": "anyone-Congress-cup-from-event",
"description": "think-so-must-during-score",
"identifier": "55790055",
"isVariable": true,
"periods": [ContractedVolumePeriodType]
}Fields
| Name | Description |
|---|---|
|
The market name the contracted volume applies to. |
|
The unit for the commodity provided by the contracted volume. |
|
The datetime the period the contracted volume is valid from. |
|
The datetime the period the contracted volume is valid to. |
|
The decimal value of the quantity provided by the contracted volume. |
Example
{
"value": "1.0",
"unit": "oil-data-test-her-about",
"marketName": "vote-strong-eye-say-raise",
"validFrom": "1982-01-25T12:45:09.134372+00:00",
"validTo": "1989-01-30T19:26:15.775079+00:00"
}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": "44681026",
"contributionScheme": ContributionSchemeType,
"interval": "MONTHLY",
"activeFrom": "2022-07-04T01:01:13.324138+00:00",
"activeTo": "2024-03-25T13:18:43.267244+00:00",
"amount": 4,
"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": 65,
"edgeCount": 10
}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": "drive-office-result-might-no"
}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": "80899166",
"agreement": ContributionAgreementType,
"fulfilledAt": "1981-02-19T13:55:21.892648+00:00",
"periodFrom": "1983-10-18T11:38:42.084327+00:00",
"periodTo": "2024-08-19T05:24:14.009795+00:00"
}ContributionSchemeType
A single Contribution Scheme.
Fields
| Name | Description |
|---|---|
|
Is this scheme currently accepting contributions? |
|
|
|
|
|
|
|
Are contributions to this scheme taxable? |
Example
{
"id": "56095089",
"code": "its-food-real-above-night",
"displayName": "particular-fund-right-claim-difficult",
"taxable": true,
"acceptingContributions": true
}Example
{
"latitude": 510.0,
"longitude": 401.5
}CoreSiteworksAppointmentType
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": "039500fc-6f0a-4e52-8d63-647548858d6d",
"jobType": "expert-us-car-idea-into",
"appointmentDate": "2004-12-11",
"timeSlotStart": "07:41:43.920699",
"timeSlotEnd": "15:16:29.165053",
"createdAt": "1976-09-01T13:48:22.419236+00:00",
"status": "PENDING",
"externalReference": "plant-join-service-firm-decade"
}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": 10,
"edgeCount": 28
}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": "person-thousand-business-think-table"
}CoreSiteworksRequestType
A Siteworks Request
Fields
| Name | Description |
|---|---|
|
List of appointments linked to this request. |
|
|
|
|
|
|
|
List of supply points on request. |
|
|
|
Example
{
"id": "80d58174-2237-45f8-8d6f-2272fb6251f1",
"status": "history-issue-look-perhaps-past",
"reason": "into-young-station-public-agent",
"createdAt": "1989-07-10T14:24:17.345535+00:00",
"lastStatusUpdateAt": "1985-04-21T17:24:04.570044+00:00",
"appointments": [CoreSiteworksAppointmentType],
"marketSupplyPoints": SupplyPointConnectionTypeConnection
}Fields
| Name | Description |
|---|---|
|
Available self-service actions. |
|
The name of the customer. |
|
The name of the customer, in kana. |
|
The forecasted supply start date provided by OCCTO. Subject to change. |
|
The ID of the switch-in request. |
Example
{
"requestId": "62708323",
"customerName": "follow-president-culture-nearly-to",
"customerNameKana": "choose-option-send-beyond-data",
"forecastedSupplyStartDate": "1984-06-20",
"availableActions": "CUSTOMER_NAME_CORRECTION"
}Fields
| Name | Description |
|---|---|
|
The requested supply end date provided by the customer. |
|
The status of the switch-out request. |
Example
{
"requestedSupplyEndDate": "2007-10-29",
"status": "READY_TO_SEND_DECISION"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Consumption in kWh. |
|
Cost in pence (excl. tax). |
|
Cost in pence (incl. tax). |
Example
{
"costOfChargeId": "65897332",
"krakenflexDeviceId": "52178305",
"reportDate": "2007-05-20",
"isSmartCharge": true,
"totalConsumption": 352.3,
"totalCostExclTax": 197.75,
"totalCostInclTax": 715.16
}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
}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-4196: Unpin at date provided is in the past.
- KT-CT-4195: Unpin at date provided for an unpinned note.
- 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
}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
}CreateAgreement
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-4719: No supply point found for identifier provided.
- KT-CT-4910: No product exists with the given input.
- KT-CT-1503: Agreement valid_to date must be later than valid_from date.
- KT-CT-1509: Unable to create agreement.
- KT-CT-1511: Cannot create overlapping agreement.
- KT-CT-1512: Account type does not support agreements.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created agreement. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"agreement": CommonAgreementType
}CreateAgreementRollover
The possible errors that can be raised are:
- KT-CT-1501: Agreement not found.
- KT-CT-4910: No product exists with the given input.
- KT-CT-4924: Unauthorized.
- KT-CT-13701: An active agreement rollover already exists for this agreement.
- KT-CT-13702: Expected send date cannot be in the past.
- KT-CT-13703: Rollover date cannot be in the past.
- KT-CT-13704: Unable to create agreement rollover.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The new agreement rollover. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"agreementRollover": AgreementRolloverType
}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
}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": "76022301"
}CreateComplaint
The possible errors that can be raised are:
- KT-CT-10801: Invalid data.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The complaint that has been created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"complaint": ComplaintType
}CreateContractOutput
Output type for creating a contract.
Fields
| Name | Description |
|---|---|
|
Unique identifier for the created contract. |
Example
{
"identifier": "31012852"
}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": "1979-07-23T05:32:48.022146+00:00"
}CreateCustomerFeedback
The possible errors that can be raised are:
- KT-CT-5516: Invalid data.
- KT-CT-1111: Unauthorized.
- 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": 88
}CreateElectricityQuote
The possible errors that can be raised are:
- KT-JP-4608: Unable to get matched products.
- KT-CT-4616: Unable to create a quote.
- KT-JP-4610: Postal information 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. |
|
The quote request. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": Quote
}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
}CreateInboundCall
The possible errors that can be raised are:
- KT-CT-11805: Invalid input for creating an inbound call.
- KT-CT-11810: Caller is blocked.
- 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
}CreateInkInboundMessage
Register an Ink inbound message.
The possible errors that can be raised are:
- KT-CT-7622: Attachment bucket is invalid.
- KT-CT-7623: Attachment path is invalid.
- KT-CT-7621: Attachment not found.
- KT-CT-7618: Unable to process message.
- KT-CT-7625: Invalid email address.
- KT-CT-7630: Message with this message ID has already been processed.
- KT-CT-7632: The text content of the Ink Inbound Generic Message is too long.
- KT-CT-7620: Channel not supported.
- KT-CT-7627: The 'email' object is missing from the payload.
- KT-CT-7628: The 'generic' object is missing from the payload.
- KT-CT-7629: The 'post' object is missing from the payload.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The Ink message that was created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": InkMessage
}CreateInkLiveChatMessage
The possible errors that can be raised are:
- KT-CT-7616: Not yet implemented.
- KT-CT-1111: Unauthorized.
- KT-CT-4123: Unauthorized.
- KT-CT-7642: No account user was found for the given fromHandle.
- KT-CT-7641: Live Chat message with this message ID has already been processed.
- KT-CT-7645: The user is not authorized to access this Live Chat.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The live chat conversation. |
|
The ID of the Ink Live Chat message that was created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"liveChatConversation": InkLiveChatConversation,
"messageRelayId": "55366174"
}CreateInputOutput
Output type for creating an input.
Fields
| Name | Description |
|---|---|
|
The created input. |
Example
{
"input": InputType
}CreateJPNFileAttachmentPayload
Upload a file with account number, gpin or both.
Fields
| Name | Description |
|---|---|
|
|
|
Presigned S3 post request. |
Example
{
"postRequest": UploadPostRequest,
"clientMutationId": "46902093"
}CreateLead
The possible errors that can be raised are:
- KT-CT-8912: Funnel not found.
- KT-CT-8930: Unable to parse address.
- KT-CT-8928: The funnel is not active and cannot be used to create this entity.
- KT-CT-8931: Extra detail value is invalid.
- KT-CT-8919: Funnel initial stage not set.
- KT-CT-9017: Consent type not found.
- KT-CT-8932: Lead contact details missing legal contact.
- KT-CT-8934: Lead contact details missing communications contact.
- KT-CT-8935: National ID bad input.
- KT-CT-8913: Organisation is not valid to be assigned.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The unique number of the lead. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"leadNumber": "look-network-group-song-score"
}CreateLifelineAgencyQuote
Mutation to accept T&Cs for customers that are onboarded through Lifeline Agencies. This mutation calls the generate_quote_for_lifeline_agency_sign_up use case to create the quote and also accept T&Cs.
Fields
| Name | Description |
|---|---|
|
Boolean indicator that indicated quotes are created. |
Example
{
"isCreated": true
}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
}CreateMfaDevice
Create a multi-factor authentication (MFA) device for user.
The possible errors that can be raised are:
- KT-CT-1128: Unauthorized.
- KT-CT-1151: MFA device not found.
- KT-CT-1153: Unable to create MFA device.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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": "like-the-themselves-middle-beyond",
"devicePhone": "put-cup-painting-difficult-front",
"totpSecret": "law-land-big-could-lead"
}CreateNewAgreementFromProductSwitchProcess
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-4924: Unauthorized.
- KT-CT-1509: Unable to create agreement.
- KT-CT-1507: Agreement product switch date is not within the acceptable range.
- KT-CT-1510: Product switch process not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The new agreement created. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"agreement": CommonAgreementType
}CreateOfferGroupForQuoting
Create a quoting offer group.
The possible errors that can be raised are:
- KT-CT-12401: Unable to create offer group.
- KT-CT-12405: Missing rates for quoting.
- KT-CT-12406: Product not configured correctly for quoting.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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": CreateOfferGroupType
}Fields
| Name | Description |
|---|---|
|
Identifier of the Offer Group. |
|
One or more Offers contained in the Offer Group. |
Example
{
"identifier": "72303820",
"offers": [OfferType]
}CreateOnSiteJobsAppointment
The possible errors that can be raised are:
- KT-CT-13030: Booking session not found.
- KT-CT-13025: Booking session has expired.
- KT-CT-13033: Slot not found.
- KT-CT-13028: Agent not found.
- KT-CT-13019: Vendor not found.
- KT-CT-13034: Appointment already exists for this request.
- KT-CT-13035: Request is inactive.
- KT-CT-13032: Request does not exist.
- KT-CT-13036: Booking service currently unavailable.
- KT-CT-13037: Appointment reference not provided by booking service.
- KT-CT-13031: Timeslot is no longer available.
- KT-CT-13027: Booking system error occurred.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created On-Site Jobs appointment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"onSiteJobsAppointment": OnSiteJobsAppointmentType
}CreateOnSiteJobsAppointmentWithoutBooking
The possible errors that can be raised are:
- KT-CT-13032: Request does not exist.
- KT-CT-13035: Request is inactive.
- KT-CT-13010: No booking adapter found for agent.
- KT-CT-13034: Appointment already exists for this request.
- KT-CT-13021: Invalid job type.
- KT-CT-13018: Unable to record cancellation_category/cancellation_sub_category.
- KT-CT-13039: Cancellation fields require CANCELLED status.
- KT-CT-13027: Booking system error occurred.
- KT-CT-13050: Cannot provide both supply_point_identifier_to_market_name_mapping and supply_point_internal_id when creating assets.
- KT-CT-13051: Supply point not found when creating assets.
- KT-CT-13052: Multiple supply points found when creating assets.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created Appointment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"onSiteJobsAppointment": OnSiteJobsAppointmentType
}CreateOnSiteJobsRequest
The possible errors that can be raised are:
- KT-CT-13002: Supply point not found.
- KT-CT-13003: Supply points must belong to the same account.
- KT-CT-13004: No account found for the given supply points.
- KT-CT-13005: Supply points must belong to the same property.
- KT-CT-13006: No properties found for the given supply points.
- KT-CT-13028: Agent not found.
- KT-CT-13010: No booking adapter found for agent.
- KT-CT-13007: At least one of the request checks failed.
- KT-CT-13008: At least one of the request checks has warnings.
- KT-CT-13009: On site jobs Request already exists.
- KT-CT-13010: No booking adapter found for agent.
- KT-CT-13011: Appointment with the given external reference and agent already exists for a different request.
- KT-CT-13012: Viewer is not allowed to create a request.
- KT-CT-13013: Reporter post init error.
- KT-CT-13014: Request reason is not supported.
- KT-CT-13015: Request sub_reason is not supported.
- KT-CT-13041: User is not allowed to override request/appointment checks.
- KT-CT-13042: Multiple supply points not supported by this booking adapter.
- KT-CT-13045: Failed to update appointment assets.
- KT-CT-13047: Multiple supply points found.
- KT-CT-13048: Cannot provide both supply_point_identifier_to_market_name_mapping and supply_point_internal_ids.
- KT-CT-13049: Neither supply_point_identifier_to_market_name_mapping nor supply_point_internal_ids provided.
- KT-CT-13050: Cannot provide both supply_point_identifier_to_market_name_mapping and supply_point_internal_id when creating assets.
- KT-CT-13051: Supply point not found when creating assets.
- KT-CT-13052: Multiple supply points found when creating assets.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The created request. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"onSiteJobsRequest": OnSiteJobsRequestType
}CreateOpportunityAndLead
The possible errors that can be raised are:
- KT-CT-8912: Funnel not found.
- KT-CT-8919: Funnel initial stage not set.
- KT-CT-8930: Unable to parse address.
- KT-CT-8907: Lead not found.
- KT-CT-8901: Unable to create lead.
- KT-CT-8902: Unable to create lead.
- KT-CT-8935: National ID bad input.
- KT-CT-4121: Invalid phone number.
- KT-CT-9017: Consent type not found.
- KT-CT-8913: Organisation is not valid to be assigned.
- 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": "federal-help-owner-executive-town",
"dateOfCreation": "1979-07-31T22:42:01.988062+00:00",
"stage": "while-range-young-look-family",
"funnelCode": "movement-first-bag-staff-company"
}Fields
| Name | Description |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Whether the operation was successful. |
Example
{
"possibleErrors": [PossibleErrorType],
"result": "product-court-station-rather-exactly"
}CreateOpportunityForLead
The possible errors that can be raised are:
- KT-CT-8912: Funnel not found.
- KT-CT-8919: Funnel initial stage not set.
- KT-CT-8907: Lead not found.
- KT-CT-8913: Organisation is not valid to be assigned.
- KT-CT-8924: Unable to create opportunity.
- KT-CT-8925: Unable to create opportunity.
- KT-CT-8926: Unable to create opportunity.
- KT-CT-8928: The funnel is not active and cannot be used to create this entity.
- KT-CT-8930: Unable to parse address.
- 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 unique number of the opportunity. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"opportunityNumber": "real-who-him-across-peace",
"dateOfCreation": "1994-10-23T11:58:15.832219+00:00"
}CreateOpportunitySolarPanelsMarket
Mutation to save an opportunity for the market solar panels.
The possible errors that can be raised are:
- KT-CT-4122: Invalid email.
- KT-CT-4121: Invalid phone number.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
When the opportunity was created. |
|
The ID number of the new opportunity. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"createdAt": "2013-07-20T18:01:31.798837+00:00",
"number": "discover-can-dinner-speak-network"
}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
}CreatePaymentActionIntent
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-3822: Unauthorized.
- KT-CT-3980: Invalid ledger identifier.
- KT-CT-3981: Unauthorized.
- KT-CT-3982: 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 action intent token. |
Example
{
"possibleErrors": [PossibleErrorType],
"token": "87825383"
}CreatePaymentMethod
Creates a new customer in GMO, a PaymentInstruction, and PaymentSchedule for an existing user.
This is called when creating a new CREDIT CARD payment method. Direct debit uses the IncomingGMOCreationExistingAccountCallback webhook.
This endpoint is designed to be used on an account with no existing payment method.
Fields
| Name | Description |
|---|---|
|
GMO payment instruction reference. |
Example
{
"reference": "give-walk-serve-improve-place"
}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": 95
}CreateProductOutput
Output type for creating a product.
Fields
| Name | Description |
|---|---|
|
The created product. |
Example
{
"product": SupplyProductType
}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
}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": 4
}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
}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 billing_period_length set. |
|
For fixed billing accounts only, the length of their billing period. Can be MONTHLY or QUARTERLY. |
|
Month to start billing from if billing_period_length 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. |
|
|
|
This must be a string-ified version of the JSON representation of RichAddressInput type. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"portfolioNumber": "P-4749C6D0",
"givenName": "Jose",
"familyName": "Williams",
"billingName": "sense-record-join-in-fish",
"email": "mean-describe-outside-often-wall",
"mobile": "agency-play-media-provide-discover",
"landline": "deep-car-couple-not-also",
"brand": "bag-what-above-fine-American",
"dateOfBirth": "1994-07-15",
"billingAddressLine1": "task-too-man-rate-mention",
"billingAddressLine2": "other-might-trial-their-style",
"billingAddressLine3": "film-service-over-thing-thank",
"billingAddressLine4": "believe-foreign-suffer-instead-dinner",
"billingAddressLine5": "civil-sign-than-myself-lawyer",
"billingPostcode": "study-dream-thank-pay-write",
"billingRichAddress": "involve-prove-through-wall-itself",
"billingPeriodLength": "edge-pass-field-two-song",
"billingPeriodMultiplier": 93,
"billingPeriodDay": 78,
"billingPeriodMonth": 74,
"isBusinessAccount": true,
"companyName": "politics-forward-shake-cold-field",
"companyNumber": "religious-miss-research-total-beautiful",
"businessType": "serve-market-painting-statement-military",
"password": "that-local-his-heart-finally",
"passwordUpdateToken": "large-seven-seem-feeling-live",
"urn": "early-despite-process-Mr-into",
"errors": [ErrorType],
"account": AccountInterface,
"clientMutationId": "25451259"
}CreateTemplateOutput
Output type for creating a template.
Fields
| Name | Description |
|---|---|
|
The created template. |
Example
{
"template": TemplateType
}CreateTimeSeriesPrices
Time series information and existing variants based on the prices created.
Fields
| Name | Description |
|---|---|
|
The time series code. |
|
The time series description. |
|
The time series meta information. |
|
The time series display name. |
|
The time series period size value. |
|
The product code associated to the time series. |
|
The time series unit value. |
|
The existing time series variants based on the prices created. |
Example
{
"code": "nature-forget-western-property-black",
"productCode": "available-whole-letter-expect-artist",
"name": "data-whatever-bag-half-surface",
"description": "forward-few-build-type-his",
"unit": "area-design-quite-rich-little",
"periodSize": "brother-grow-early-lose-job",
"meta": {"key": "value"},
"variants": VariantProfile
}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. |
|
Unique identifier for the transaction. |
|
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. |
|
Date when the transaction was posted to the account. |
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Human-readable title describing the transaction. |
Example
{
"id": "15998077",
"postedDate": "1971-05-28",
"createdAt": "1975-05-02T14:19:10.438602+00:00",
"accountNumber": "A-8328655A",
"amount": 89,
"amounts": TransactionAmountType,
"balanceCarriedForward": 79,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "billion-this-soldier-employee-admit",
"billingDocumentIdentifier": "93665683",
"statementId": "78914508",
"isReversed": true,
"hasStatement": true,
"note": "standard-matter-face-tree-safe",
"reasonCode": "leave-control-scene-picture-cut"
}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": "worry-how-lawyer-yes-question",
"display": "attorney-can-true-will-allow",
"isDeprecated": true,
"isTaxExempt": true,
"isHidden": true,
"group": "couple-peace-concern-no-class"
}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": "church-suggest-realize-chance-usually",
"accountNumber": "A-BDB39BFB",
"validFrom": "1983-02-27T22:13:42.435217+00:00",
"validTo": "1986-05-01T03:59:31.000598+00:00"
}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": "push-owner-common-know-product",
"accountNumber": "A-D2DAB8BC",
"validFrom": "1998-12-04T13:03:01.199929+00:00",
"validTo": "1982-03-24T15:51:11.758014+00:00"
}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]
}CurrencyType
Represents currency information of the current Kraken
Fields
| Name | Description |
|---|---|
|
The ISO-4217 currency code (e.g., GBP, USD, EUR). |
|
The minor unit name (e.g., pence, cents). |
|
The currency name in plural form (e.g., pounds, dollars). |
|
The currency symbol (e.g., £, $, €). |
Example
{
"code": "never-level-billion-natural-board",
"symbol": "either-way-ago-natural-often",
"name": "society-pull-exist-trial-minute",
"minorUnit": "allow-force-above-least-quality"
}Fields
| Name | Description |
|---|---|
|
The current eligibility status for a deposit return. |
|
The reasons why the account is currently ineligible for a deposit return. |
Example
{
"isEligible": true,
"reasonsForIneligibility": ["page-democratic-according-wish-current"]
}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": 88,
"edgeCount": 19
}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": "maintain-possible-hand-improve-where"
}Fields
| Name | Description |
|---|---|
|
The unique identifier for the customer feedback form. |
|
The name of the customer feedback form. |
Example
{
"id": "31411327",
"name": "company-pattern-spend-compare-throw"
}Fields
| Name | Description |
|---|---|
|
|
|
The value attached to the source |
|
The datetime the feedback was submitted |
Example
{
"id": "25577323",
"rawScore": 80,
"submittedAt": "2001-02-02T04:58:20.795568+00:00"
}Fields
| Name | Description |
|---|---|
|
The account number. |
|
The ledger identifier. |
Example
{
"accountNumber": "A-2F1C324D",
"ledgerNumber": "point-after-else-guy-policy"
}Fields
| Name | Description |
|---|---|
|
The account number. |
|
The agency. |
|
The campaign. |
|
Whether the commencement could be applied. |
|
The ledger identifier. |
Example
{
"commencementStatus": true,
"accountNumber": "A-E688DA2F",
"ledgerNumber": "beautiful-information-glass-listen-their",
"agency": "effort-stage-poor-list-major",
"campaign": "tough-us-own-once-sport"
}Fields
| Name | Description |
|---|---|
|
The account number. |
|
Whether the update has been applied. |
Example
{
"commencementStatus": true,
"accountNumber": "A-F86B695D"
}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": "41168257",
"typename": "total-year-far-picture-his",
"dashboardItems": SectionType,
"serialisedDashboardItems": "worry-believe-material-specific-all"
}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": "2026-01-01T14:55:51.085316+00:00",
"endCursor": "2010-08-29T08:41:57.005776+00:00",
"hasPreviousPage": true,
"hasNextPage": true
}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": "PM-door-growth-weight-nothing",
"code": "rate-front-instead-area-position",
"isActive": true
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
Example
{
"code": "night-director-only-hotel-add",
"displayName": "tend-early-might-need-such",
"deprecatedAt": "1998-08-21T06:48:54.079811+00:00",
"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": "ON_SUPPLY_GAS",
"amount": 83,
"startedAt": "1997-06-08T14:49:07.206178+00:00",
"stoppedAt": "1993-02-15T07:52:20.396395+00:00",
"stopReason": "BANKRUPT",
"collectionCampaign": DebtCollectionCampaignType
}DecimalReading
A reading with a decimal value taken at a specific time.
Fields
| Name | Description |
|---|---|
|
The timestamp when the reading was taken. |
|
The decimal value of the reading. |
Example
{
"timestamp": "1971-06-04T15:02:36.000663+00:00",
"value": "1.0"
}DecimalType
Graphene type object to represent float values
Fields
| Name | Description |
|---|---|
|
Value of this field. |
Example
{
"decimalValue": "1.0"
}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": 55,
"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": "weight-card-issue-body-lead",
"id": "67787785",
"typename": "effort-life-add-toward-result",
"url": "however-name-material-begin-form"
}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 |
|---|---|
|
Number of days to delay based on delay strategy. |
|
The description of the term. |
|
The display name of the term. |
|
The identifier of the term. |
|
Whether the term is variable. |
|
Defines the method for calculating the delay period. |
|
The type of the term. |
Example
{
"type": "study-find-fall-writer-bad",
"displayName": "return-white-bit-far-organization",
"description": "quickly-establish-stuff-born-cultural",
"identifier": "40585764",
"isVariable": true,
"days": 2,
"strategy": "FIXED"
}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": "room-less-cut-offer-wide"
}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
}DeleteInputOutput
Output type for deleting an input.
Fields
| Name | Description |
|---|---|
|
The identifier of the deleted input. |
Example
{
"deletedIdentifier": "29000678"
}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.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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
}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"
}DeleteTemplateOutput
Output type for deleting a template.
Fields
| Name | Description |
|---|---|
|
The identifier of the deleted template. |
Example
{
"deletedIdentifier": "56186410"
}Fields
| Name | Description |
|---|---|
|
Opt-in or out of future events. |
|
Opt-in or out to email communications. |
|
Opt-in or out to line communications. |
Example
{
"isOptedIntoDemandResponseEvents": true,
"isOptedIntoEmails": true,
"isOptedIntoLine": true
}Fields
| Name | Description |
|---|---|
|
Campaign participant tips. |
|
Get the number of entries the participant has for the next prize draw. |
Example
{
"tips": {"key": "value"},
"totalNumberOfEntries": 92
}DemandResponseCampaignParticipantType
Type representing the fields in the model representing a customer's results for the latest demand response campaign.
Fields
| Name | Description |
|---|---|
|
The average percentage difference across all demand response days. |
|
The end date of this campaign. |
|
The campaign that the participant belongs to. |
|
The start date of this campaign. |
|
Fetch a list of each demand response date the customer participated in. |
|
A participant is eligible for events if they have been more than a few days on supply. |
|
Whether the participant is opted in to |
|
Whether the participant is opted in to future events. |
|
Whether the participant is opted in to |
|
Get the number of entries the participant has for the next prize draw. |
|
The timestamp when the account opted in for this campaign. |
|
Signed up supply point identification number. |
|
The number of demand response event days where a customer achieved the target. |
|
Get the campaign tips and whether they've been completed by the participant. |
|
The total CO2 that a customer saved or increased due to their consumption change. |
|
The total in kWh that a customer's consumption changed by participating in the latest campaign. |
|
The total CO2 that a customer saved converted into trees. |
Example
{
"totalDiffKwh": 34.13,
"successfulDaysCount": 91,
"campaignName": "this-place-real-person-institution",
"campaignStart": "1993-03-16T23:31:03.670899+00:00",
"campaignEnd": "1997-07-24T16:34:05.291725+00:00",
"averagePercentageDifference": 574.29,
"demandResponseDailyResults": DemandResponseDailyResultType,
"totalDiffCarbon": 647.73,
"totalTreesSaved": 707.94,
"optedInAt": "1986-03-29T14:10:02.915219+00:00",
"tips": {"key": "value"},
"numberOfEntries": 28,
"isEligibleForEvents": true,
"isOptedIntoEvents": true,
"isOptedIntoEmails": true,
"isOptedIntoLine": true,
"spin": "my-out-nor-point-trip"
}DemandResponseDailyResultType
Type representing a single day's results for a customer attempting a demand response event.
Fields
| Name | Description |
|---|---|
|
The amount in yen that have been saved in this challenge. |
|
The expected consumption of a customer with responding to a demand response event. |
|
The date of a particular demand response event. |
|
Get the number of entries the participant has got from this daily result. |
|
The actual consumption of a customer, having responded to an event. |
|
The percentage difference between the target and actual consumption. |
|
The start time of a particular demand response event. |
|
The end time of a particular demand response event. |
Example
{
"eventDate": "1988-01-02",
"validFrom": "2019-05-10T01:23:17.096920+00:00",
"validTo": "1996-02-09T06:52:15.508972+00:00",
"baselineConsumptionKwh": 359.1,
"outturnConsumptionKwh": 847.19,
"percentageDifference": 638.84,
"amountSaved": 444.14,
"numberOfEntries": 100
}Fields
| Name | Description |
|---|---|
|
The timestamp at which the customer accepted the deposit agreement. |
|
The date on which a payment is requested for deposit collection (defaults to current date, if not specified in the deposit policy). |
|
The current eligibility status for a deposit return. |
|
The deposit agreement amount. |
|
The deposit agreement key (unique). |
|
The date by which the deposit agreement must be fulfilled (defaults to 31-12-9999 i.e. deposit is never late, if not specified in the deposit policy). |
|
The timestamp at which the deposit agreement was fulfilled. |
|
The return strategy used to return the deposit. |
Example
{
"depositKey": "and-general-these-scene-business",
"depositAmount": 36,
"acceptedAt": "2020-08-29T10:14:09.158361+00:00",
"fulfilledAt": "2005-03-25T22:52:23.394028+00:00",
"collectionDate": "1983-05-12",
"dueDate": "1974-09-12",
"returnStrategy": "rule-newspaper-church-big-say",
"currentEligibilityStatus": CurrentEligibilityStatusOutput
}Fields
| Name | Description |
|---|---|
|
The amount to be returned in this installment. |
|
The date by which the deposit return installment is due. |
|
The status of this return installment. |
Example
{
"dueDate": "2009-02-26",
"amount": 21,
"status": "relationship-site-perhaps-again-apply"
}Fields
| Name | Description |
|---|---|
|
The id of the device. |
|
Get readings from a readable device e.g., a supply point, device, or register. |
|
The registers associated with this device. |
Example
{
"readings": Readings,
"deviceIdentifier": "22350056",
"registers": RegistersConnection
}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": "2014-04-25T07:43:10.808284+00:00"
}Fields
| Name | Description |
|---|---|
|
The type of device. |
|
|
|
The third party that provides control over this device. |
Example
{
"krakenflexDeviceId": "82150736",
"provider": "BYD",
"deviceType": "BATTERIES"
}DeviceReAuthentication
Information about a device's re-authentication eligibility and status.
Fields
| Name | Description |
|---|---|
|
|
Example
{
"isEligible": true
}Fields
| Name | Description |
|---|---|
|
Get readings from a readable device e.g., a supply point, device, or register. |
|
The id of the register. |
Example
{
"readings": Readings,
"registerIdentifier": "49336175"
}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": ["report-medical-require-really-political"]
}DevicesConnection
Pagination for devices.
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": DevicesEdge,
"totalCount": 58,
"edgeCount": 80
}DevicesEdge
A Relay edge containing a Devices and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Device,
"cursor": "middle-cold-wish-worry-sign"
}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": 69,
"edgeCount": 77
}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": "own-officer-economy-help-reason"
}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": "47808008",
"status": "right-between-direction-break-information",
"sortCode": "pay-name-office-see-entire",
"iban": "door-have-per-think-soldier",
"accountHolder": "consider-color-certainly-half-deal",
"instructionType": "town-thus-require-their-black",
"cardPaymentNetwork": "view-crime-within-travel-high",
"cardExpiryMonth": 23,
"cardExpiryYear": 66,
"lastFourDigitsOfAccountNumber": "A-12048A0D",
"maskedAccountIdentifier": "97557377",
"maskedIban": "some-heavy-have-style-church",
"owners": [PaymentInstructionOwnerType]
}Fields
| Name | Description |
|---|---|
|
The status of the disconnection process. |
|
The date when the supply is scheduled to be disconnected. |
Example
{
"status": "WAITING_TO_APPLY",
"supplyEndDate": "1992-04-10"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Example
{
"stepName": "government-song-future-add-include",
"usedChannel": "EMAIL",
"dueDate": "2012-02-25",
"actionedAt": "1995-05-08T13:38:18.734635+00:00",
"createdAt": "1991-03-18T13:02:19.051788+00:00"
}Fields
| Name | Description |
|---|---|
|
Actions associated with a DunningProces. |
|
Delinquent debt for an Account. |
|
The date and time where the process reached a terminal state, such as complete or withdrawn. |
|
|
|
Created by SupportUser reference. |
|
|
|
The next step in the DunningProcess. |
|
|
|
The previous step in the DunningProcess. |
|
|
|
|
|
|
|
Withdrawn by SupportUser reference. |
Example
{
"pathName": "on-citizen-cover-manager-reach",
"startDate": "2001-06-16",
"status": "ACTIVE",
"createdBy": "fine-civil-community-try-important",
"createdNote": "finally-like-a-student-security",
"withdrawnBy": "eye-recent-party-always-or",
"concludedAt": "1973-11-25T10:51:20.412360+00:00",
"createdAt": "2002-11-25T00:50:43.388445+00:00",
"updatedAt": "2012-05-13T18:16:01.289207+00:00",
"actions": [DunningAction],
"previousStep": "huge-skill-strong-will-wear",
"nextStep": "choose-bar-loss-continue-economic",
"badDebt": 29
}Fields
| Name | Description |
|---|---|
|
This field is replacing |
|
|
|
|
|
Shows the availability status of an integration. |
|
|
|
|
|
|
|
|
|
Example
{
"vehicleId": 61056366,
"model": "history-no-which-most-assume",
"year": 95,
"availableFrom": 58,
"availableTo": 9,
"batterySize": "1.0",
"supportedProviders": ["science-cover-here-center-table"],
"isIntegrationLive": true,
"integrationStatus": "INTERNAL_TESTING"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "window-nation-friend-peace-thus",
"models": [ElectricVehicleModelType]
}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": "30256624",
"readingQuality": "ACTUAL",
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "26475135",
"deviceId": "56376000"
}ElectricityFitProduct
Product that has the FiT tariff.
Fields
| Name | Description |
|---|---|
|
Product code. |
|
Human friendly name to be displayed in interfaces. |
|
Generation credit rate information. |
|
A JSON object containing extra information. |
Example
{
"code": "page-thank-over-decade-research",
"displayName": "camera-program-tell-compare-act",
"params": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"generationCredits": GenerationCreditRate
}Fields
| Name | Description |
|---|---|
|
The Agreements linked to this electricity generation point. |
|
The generation point identification number. |
|
Fetch Half Hourly Readings for this GPIN from and to a given datetime of any version. Restricted by the Agreement Periods. |
|
Electricity generation point id. |
|
Return the monthly confirmed Export readings associated with a given Electricity Generation Point.Restricted by the Agreement Periods. |
|
The most recent Export Cos Gain Process. |
|
The generation point status. |
Example
{
"id": "97796879",
"gpin": "back-relationship-station-north-traditional",
"status": "UNDER_CONTRACT",
"agreements": [GenerationAgreement],
"latestExportCosGainProcess": ExportCosGainProcess,
"intervalReadings": ExportIntervalReadings,
"halfHourlyReadings": ElectricityHalfHourReading
}ElectricityHalfHourReading
Half Hourly Interval Reading - can be a variety of different versions.
Fields
| Name | Description |
|---|---|
|
The tariff's consumption product rate band that this reading falls into. |
|
Placeholder for FED type check, will remove it soon. |
|
Estimated cost for amount of Electricity used. |
|
End of Interval Period - always 30mins later. |
|
Start of Interval Period. |
|
Consumed amount of Electricity during period, in kWh. |
|
The version of the half hourly reading. |
Example
{
"startAt": "1997-12-11T13:24:12.129044+00:00",
"endAt": "2024-04-12T17:51:45.132080+00:00",
"value": "1.0",
"costEstimate": "1.0",
"version": "DAILY",
"consumptionRateBand": "test-commercial-country-somebody-though",
"consumptionStep": 32
}ElectricityIntervalReading
Monthly Interval Reading - which may have associated 30min Readings
Fields
| Name | Description |
|---|---|
|
The month with which the monthly interval reading is associated. |
|
Estimated cost for amount of Electricity used. |
|
End of Interval Period. |
|
Fetch Half Hourly Readings associated with this interval reading. Will return an empty list if has_half_hourly_data_for_period is False. |
|
Tracks whether there are Half Hourly Readings associated with this Interval. |
|
|
|
The interval period length, in days. |
|
Date when the reading was taken. |
|
Start of Interval Period. |
|
Consumed amount of Electricity during period, in kWh. |
Example
{
"id": "31495323",
"readingDate": "2007-05-25",
"billableMonth": "keep-specific-also-last-recently",
"startAt": "2004-11-01T01:46:56.143804+00:00",
"endAt": "1980-11-09T02:02:37.819120+00:00",
"periodLengthDays": 62,
"value": "1.0",
"hasHalfHourlyDataForPeriod": true,
"halfHourlyReadings": ElectricityHalfHourReading,
"costEstimate": "1.0"
}Fields
| Name | Description |
|---|---|
|
The capacity of the meter, in Amperes. |
|
The date and time when the meter was removed. |
|
The serial number on the physical meter (計器番号). |
Example
{
"serialNumber": "leave-follow-course-region-understand",
"capacity": 11,
"removedAt": "1984-07-26T06:12:10.160406+00:00"
}ElectricitySingleStepProduct
Product with a single unit rate.
Fields
| Name | Description |
|---|---|
|
Product code. |
|
|
|
Human friendly name to be displayed in interfaces. |
|
Fuel cost adjustment rate information. |
|
A JSON object containing extra information. |
|
Renewable energy levy rate information. |
|
Price per day for standing charge. |
|
Unit type for standing charge. |
|
List of standing charge product rates. |
|
List of standing charge product rates. |
|
Product Tags. |
Example
{
"code": "never-pass-recognize-police-party",
"displayName": "fund-amount-my-tax-interest",
"params": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"standingChargeUnitType": "stage-trouble-meeting-care-suggest",
"standingChargePricePerDay": "1.0",
"standingCharges": StandingCharge,
"standingChargesBad": StandingCharge,
"fuelCostAdjustment": FuelCostAdjustmentRate,
"renewableEnergyLevy": RenewableEnergyLevyRate,
"tags": "expect-can-other-idea-successful",
"consumptionCharges": ConsumptionRate
}ElectricitySteppedProduct
Product where kilowatt-hour rate varies according to the level of consumption during the period specified in the rates.
Fields
| Name | Description |
|---|---|
|
Product code. |
|
List of consumption product rates. |
|
Human friendly name to be displayed in interfaces. |
|
Fuel cost adjustment rate information. |
|
A JSON object containing extra information. |
|
Renewable energy levy rate information. |
|
Price per day for standing charge. |
|
Unit type for standing charge. |
|
List of standing charge product rates. |
|
List of standing charge product rates. |
|
Product Tags. |
Example
{
"code": "base-final-across-model-financial",
"displayName": "receive-including-force-different-our",
"params": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"standingChargeUnitType": "free-stock-back-there-so",
"standingChargePricePerDay": "1.0",
"standingCharges": StandingCharge,
"standingChargesBad": StandingCharge,
"fuelCostAdjustment": FuelCostAdjustmentRate,
"renewableEnergyLevy": RenewableEnergyLevyRate,
"tags": "sister-part-piece-and-same",
"consumptionCharges": SteppedConsumptionRate
}Fields
| Name | Description |
|---|---|
|
A currently active amperage change process. |
|
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 Agreements linked to this electricity supply point. |
|
The supply point capacity in Amperes. Deprecated The 'amperage' field is deprecated. |
|
An indication of whether a customer can apply for the change themselves. |
|
An indication of whether the move-in date can be updated. |
|
An indication of whether the move-out date can be updated. |
|
The calculated capacity. |
|
(Soon to be deprecated) The calculated capacity based on the agreement. |
|
The earliest date in which an amperage change can be performed. |
|
Fetch Half Hourly Readings for this SPIN from and to a given datetime of any version. Restricted by the Agreement Periods. |
|
|
|
Return the monthly confirmed readings associated with a given Supply Point. Restricted by the Agreement Periods. |
|
The supply point capacity in kVA. Deprecated The 'kva' field is deprecated. |
|
The supply point capacity in kW. Deprecated The 'kw' field is deprecated. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The latest switch-out process active on this account. |
|
Override Field to add additional attributes and extend description with possible_errors |
|
The latest move-out process active on this account. |
|
The electricity meters associated with this supply point. |
|
A list of the possible amperage values to select. |
|
Date of when the reading after the next reading will be collected by the grid operator. |
|
Date of when the next reading will be collected by the grid operator. |
|
The day of the month on which the reading is collected. |
|
References for the electricity supply point. |
|
The supply point identification number. |
|
The meter point status. |
|
Historical supply details list for this account, ordered by the valid_from date in descending order. |
|
The supply periods for the supply point. |
Example
{
"mpan": "security-attorney-instead-bank-article",
"agreement": ElectricityAgreementType,
"annualConsumption": ElectricityConsumption,
"quotedProducts": ElectricityQuotedProduct,
"rateType": "STANDARD",
"co2SavingInKgFromConsumption": 13,
"treesSavedFromConsumption": 19
}Fields
| Name | Description |
|---|---|
|
Key to identify the reference. |
|
Value for this namespace. |
Example
{
"namespace": "might-pretty-suffer-tend-find",
"value": "anyone-part-always-significant-later"
}ElectricityTerminationOutput
Output data related to a LeaveSupplier journey for the electricity market.
Fields
| Name | Description |
|---|---|
|
The requested date of demolition. |
|
Time slot requested by the customer for demolition. |
|
Whether demolition required. |
|
Whether on-site attendance is required. |
|
The requested date of on-site attendance. |
|
Time slot requested by the customer for on-site attendance. |
|
Date when supply point is disconnected. |
|
The market supply point identification number. |
Example
{
"supplyPointIdentifier": "44637804",
"supplyEndDate": "1974-12-15",
"isDemolition": true,
"demolitionDate": "2006-10-07",
"demolitionTime": "_0900",
"onSiteAttendance": true,
"requestedOnSiteDate": "1972-05-28",
"requestedOnSiteTimeSlot": "_0900"
}EmailAttachmentType
Represents a file to attach to a email message.
Fields
| Name | Description |
|---|---|
|
The filename of the attachment. |
|
The ID of the attachment. |
|
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": "22083033",
"filename": "senior-create-firm-hour-within",
"temporaryUrl": "occur-hit-sign-one-since"
}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": "86426786",
"eventType": "use-guy-general-budget-ahead",
"occurredAt": "1991-03-09T11:39:43.326697+00:00",
"message": EmailType
}EmailQuote
The possible errors that can be raised are:
- KT-JP-4609: Terms and conditions not 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],
"sent": true
}EmailType
Represents an email communication
Fields
| Name | Description |
|---|---|
|
Attachments of the email message. |
|
|
|
The date and time the email was created. |
|
The address the email was sent from. |
|
|
|
HTML body of the email message. |
|
The ID of the email. |
|
Email recipient. |
|
Email sender. |
|
The date and time the email was sent. |
|
Subject line of the email message. |
|
URL to view the email in the support site. |
|
The email template code. |
|
Text body of the email message. |
|
The email address of the recipient. |
|
Example
{
"id": "43858692",
"createdAt": "2012-06-20T13:52:03.210328+00:00",
"sentAt": "2006-11-25T11:49:34.715143+00:00",
"templateCode": "true-your-sound-television-far",
"toAddress": "cost-writer-would-trip-success",
"fromEmail": "whether-animal-shake-down-whatever",
"subject": "then-whom-just-religious-claim",
"attachments": [EmailAttachmentType],
"textBody": "policy-something-other-beyond-check",
"htmlBody": "tonight-prevent-subject-after-such",
"toNumber": "item-second-know-together-light",
"fromNumber": "second-condition-himself-next-action",
"channel": "rate-table-week-bar-plant",
"sender": "simple-safe-tough-case-newspaper",
"recipient": "popular-class-concern-form-stay"
}Fields
| Name | Description |
|---|---|
|
The email address to be checked. |
|
The status of verification for associated email. |
Example
{
"email": "air-war-then-beat-field",
"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": "27934694",
"readingQuality": "ACTUAL",
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "53516569",
"deviceId": "83784505"
}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": "60274771",
"name": "detail-discover-program-view-force",
"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": "16229175",
"embeddedNetwork": EmbeddedNetworkType,
"propertyId": "22924362"
}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"
}EnergyMixDataType
Energy mix data can include the latest carbon intensity index in a region.
Fields
| Name | Description |
|---|---|
|
Current carbon intensity index. |
Example
{
"carbonIntensityIndex": "hear-explain-animal-attorney-social"
}Example
{
"linkState": "world-like-condition-for-popular",
"linkUrl": "set-church-standard-author-north"
}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
}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": "maintain-condition-black-human-amount",
"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": "anyone-wish-natural-offer-success"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"field": "smile-anyone-call-third-break",
"messages": "meeting-drive-attorney-season-develop"
}EstimateUsage
Estimate average monthly electricity usage in kwh based on EstimateUsageInputType fields.
Fields
| Name | Description |
|---|---|
|
Example
{
"usageEstimate": 49
}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": "some-total-minute-teach-parent",
"pricePerUnit": PricePerUnit
}ExpireTemplatesOutput
Output type for expiring templates.
Fields
| Name | Description |
|---|---|
|
Identifiers of templates that were expired. |
Example
{
"expiredIdentifiers": "rate-ability-can-step-short"
}Fields
| Name | Description |
|---|---|
|
Available self-service actions. |
|
The name of the customer. |
|
The name of the customer, in kana. |
|
The forecasted export start date provided by OCCTO. Subject to change. |
|
The ID of the Export Switch-In Request. |
Example
{
"requestId": "89069595",
"customerName": "series-positive-happen-prove-Republican",
"customerNameKana": "through-American-production-drive-animal",
"forecastedExportStartDate": "1989-11-28",
"availableActions": "CUSTOMER_NAME_CORRECTION"
}ExportIntervalReadings
Monthly Interval Reading - which may have associated 30min Readings
Fields
| Name | Description |
|---|---|
|
The month with which the monthly interval reading is associated. |
|
Estimated cost for amount of Electricity generated. |
|
End of Interval Period. |
|
Fetch Half Hourly Readings associated with this interval reading. Will return an empty list if has_half_hourly_data_for_period is False. |
|
Tracks whether there are Half Hourly Readings associated with this Interval. |
|
The interval period length, in days. |
|
Date when the reading was taken. |
|
Start of Interval Period. |
|
Generated amount of Electricity during period, in kWh. |
Example
{
"readingDate": "1985-04-28",
"billableMonth": "western-check-paper-usually-song",
"startAt": "1996-06-06T19:32:46.942284+00:00",
"endAt": "1990-07-10T09:06:29.627932+00:00",
"periodLengthDays": 7,
"value": "1.0",
"hasHalfHourlyDataForPeriod": true,
"halfHourlyReadings": ElectricityHalfHourReading,
"costEstimate": "1.0"
}ExportReadingsConnection
Pagination for readings representing outgoing utility flow e.g., solar generation.
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": ExportReadingsEdge,
"totalCount": 44,
"edgeCount": 57
}ExportReadingsEdge
A Relay edge containing a ExportReadings and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Reading,
"cursor": "increase-painting-perhaps-check-middle"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "86783695",
"eventType": "probably-property-large-hair-between",
"occurredAt": "1994-06-08T21:24:50.034968+00:00",
"category": "per-owner-southern-west-account",
"subcategory": "heart-crime-control-bill-administration",
"description": "most-little-sign-where-type",
"content": {"key": "value"}
}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": ExternalAccountEventConnectionTypeEdge,
"totalCount": 98,
"edgeCount": 70
}ExternalAccountEventConnectionTypeEdge
A Relay edge containing a ExternalAccountEventConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": ExternalAccountEvent,
"cursor": "different-worker-coach-his-best"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "16558773",
"eventType": "option-nice-drive-despite-least",
"category": "life-friend-approach-it-win",
"subcategory": "bill-firm-this-history-run",
"occurredAt": "2024-07-20T14:26:04.249810+00:00",
"description": "always-wait-sister-between-conference",
"content": {"key": "value"}
}ExternalSalesInfoType
GraphQL type representing external sales information.
This type is used to represent sales records that originate from external systems or processes outside of Kraken's direct tracking mechanisms.
Fields
| Name | Description |
|---|---|
|
The unique identifier for the sales record. |
Example
{
"salesRecordIdentifier": "18839712"
}Fields
| Name | Description |
|---|---|
|
The key of the extra detail item. |
|
The value of the extra detail item. |
Example
{
"key": "piece-minute-current-attention-job",
"value": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType
}Fields
| Name | Description |
|---|---|
|
Description of the extra for the parent node. |
|
Display label of the extra for the parent node. |
|
Value of the extra. |
Example
{
"label": "really-very-south-lead-worry",
"description": "political-ahead-suddenly-son-risk",
"value": "bag-skill-later-experience-of"
}FetchElectricityGenerationPointDetails
The possible errors that can be raised are:
- KT-JP-4602: Quoted electricity supply points cannot be found.
- KT-JP-4606: GPIN does not exist on OCCTO.
- KT-JP-4603: OCCTO could not process the request.
- KT-JP-4607: An unexpected error occurred when trying to fetch GPIN details.
- 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 updated quote request. |
|
The quoted electricity generation point. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": Quote,
"quotedSupplyPoint": QuotedElectricityGenerationPoint
}FetchElectricitySupplyPointDetails
The possible errors that can be raised are:
- KT-JP-4602: Quoted electricity supply points cannot be found.
- KT-JP-4604: SPIN does not exist on OCCTO.
- KT-JP-4603: OCCTO could not process the request.
- KT-JP-4605: An unexpected error occurred when trying to fetch SPIN details.
- 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 quoted electricity supply point. |
Example
{
"possibleErrors": [PossibleErrorType],
"quoteRequest": Quote,
"quotedSupplyPoint": QuotedElectricitySupplyPoint
}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": "idea-quite-own-civil-camera",
"vendor": "environment-affect-ground-authority-value"
}FetchPreSignedLinkForOpportunityAttachment
The possible errors that can be raised are:
- KT-CT-8933: Opportunity file attachment not found.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The opportunity file attachment with pre-signed URL. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"opportunityFileAttachment": OpportunityFileAttachment
}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": "performance-yet-election-wife-food",
"rate": "strategy-decide-bed-like-story",
"ttl": 37,
"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": 78,
"edgeCount": 17
}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": "feel-realize-individual-beyond-these"
}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": "87130891",
"identifierType": "strong-treat-customer-until-meet",
"riskLevel": "1.0",
"isInRiskList": true
}Fields
| Name | Description |
|---|---|
|
The suggested fixed payment amount. |
Example
{
"amount": 63
}Fields
| Name | Description |
|---|---|
|
The maximum value this constraint allows. |
|
The minimum value this constraint allows. |
Example
{
"min": "1.0",
"max": "1.0"
}Fields
| Name | Description |
|---|---|
|
The unique id of the device preference schedule setting. |
|
The maximum value a preference can be set to (inclusive). |
|
The constraint applied to the max value. |
|
The minimum value a preference can be set to (inclusive). |
|
The constraint applied to the min value. |
|
The step size preference can be set to. |
|
The constraint applied to the target value. |
|
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": 78485358,
"timeFrom": "05:21:12.669852",
"timeTo": "13:37:19.246826",
"timeStep": 61,
"min": "1.0",
"max": "1.0",
"step": "1.0",
"minConstraint": PreferenceConstraint,
"maxConstraint": PreferenceConstraint,
"targetConstraint": PreferenceConstraint
}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": 96116698,
"deviceType": "evening-story-yes-simply-toward",
"mode": "CHARGE",
"unit": "CELSIUS",
"scheduleSettings": FlexDevicePreferenceScheduleSettingInterface
}FlexSupportedDevices
A list of supported makes and models for a given device type.
Fields
| Name | Description |
|---|---|
|
The type of device. |
|
List of supported brands or manufacturer. |
Example
{
"deviceType": "BATTERIES",
"supportedMakes": FlexSupportedMake
}FlexSupportedMake
A brand or manufacturer of the device and its associated models.
If models is empty, all models for this make are supported.
Fields
| Name | Description |
|---|---|
|
Brand or manufacturer of the device. |
|
List of supported models for the device make. If empty, all models are supported. |
Example
{
"make": "street-soon-defense-leave-option",
"models": FlexSupportedModel
}FlexSupportedModel
A supported model for a given make.
If model year range is null, all years are supported.
Fields
| Name | Description |
|---|---|
|
Model name of the device. |
|
Model years supported. If null, all model years are supported. |
Example
{
"modelYearRange": ModelYearRange,
"modelName": "local-ok-serious-term-easy"
}FloatType
Graphene type object to represent float values
Fields
| Name | Description |
|---|---|
|
Value of this field. |
Example
{
"floatValue": 855.96
}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": "2008-02-20T02:21:08.342433+00:00"
}FormScreenType
A screen type for forms with input fields.
Combines display items with input fields (TextField, Checkbox, Toggle), and provides primary/secondary buttons for form submission.
Note: header and footer are embedded in screenData and not exposed as separate GraphQL fields, following the pattern of ComponentListType.
Fields
| Name | Description |
|---|---|
|
Whether the element is hidden from view. |
|
Accessible description of the element. |
|
Unique identifier of the object. |
|
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": "rock-sort-truth-total-article",
"id": "83833713",
"typename": "popular-blue-with-third-military",
"name": "wall-fact-standard-administration-sell",
"refreshFrequency": 36,
"screenData": "day-trial-home-drug-director"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"id": 13457185,
"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": "22822164",
"typename": "finish-data-church-late-federal",
"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": "79659642",
"isInSuspiciousList": true
}FuelCostAdjustmentRate
Fuel cost adjustment product rate.
Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per kWh without tax. |
|
Price per kWh including tax. |
|
Region of operation. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Fuel cost adjustment rate valid from datetime. |
|
Fuel cost adjustment rate valid to datetime. |
Example
{
"gridOperatorCode": "billion-political-people-he-could",
"regionOfOperation": "between-story-maybe-action-available",
"band": "bad-character-consider-middle-huge",
"validFrom": "2024-11-11T21:28:22.054923+00:00",
"validTo": "2023-01-10T14:52:21.228017+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 38,
"pricePerUnitIncTax": "1.0"
}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": "68631089",
"amount": 47
}Fields
| Name | Description |
|---|---|
|
The time the data was reported. |
|
The latest reported mode of the heat pump. |
Example
{
"value": "HEATING",
"timestamp": "1987-10-21T21:48:44.133371+00:00"
}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": 55,
"edgeCount": 2
}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": "partner-nation-outside-book-order"
}Fields
| Name | Description |
|---|---|
|
Amount used from a funding source in minor currency. |
|
Reason why the funding source was used. |
Example
{
"reason": "heart-less-whom-still-answer",
"amount": 65
}Fields
| Name | Description |
|---|---|
|
The code of the field. |
|
Whether the field is deprecated. |
|
The type of the field. |
|
The name of the field. |
|
The order of the field in the collection. |
|
The choices for the field if applicable. |
Example
{
"code": "quite-certain-might-computer-likely",
"name": "American-game-building-single-time",
"fieldType": "STR",
"textChoices": ["people-discover-gun-authority-home"],
"deprecated": true,
"orderInCollection": 69
}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": "56476291",
"readingFrequencyType": "RAW_INTERVAL",
"marketSupplyPointId": "94663101",
"deviceId": "77630914"
}GasIntervalReading
Gas Interval Reading
Fields
| Name | Description |
|---|---|
|
Number of days of gas usage. |
|
End of interval period. |
|
Kraken gas reading id. |
|
Date reading was taken. |
|
Reason for reading. |
|
Start of interval period. |
|
Gas usage in cubic meters. |
Example
{
"id": "37285153",
"daysOfGasUsage": 46,
"endAt": "1977-05-05T21:59:26.303582+00:00",
"readingDate": "2001-03-28",
"readingReason": "as-goal-true-suffer-top",
"startAt": "1978-07-15T01:20:51.101754+00:00",
"usage": 34
}Fields
| Name | Description |
|---|---|
|
The latest active disconnection process for the supply point. |
|
The Agreements linked to this gas supply point. |
|
The meter readings for the supply point. |
|
The meter capacity of the supply point. |
|
Date of when the reading after the next reading will be collected by the grid operator. |
|
Date of when the next reading will be collected by the grid operator. |
|
|
|
Date of when the previous reading was collected by the grid operator. |
|
|
|
|
|
|
|
The supply point identification number. |
|
The meter point status. |
|
The supply periods for the supply point. |
Example
{
"mprn": "choice-we-wide-scientist-scene",
"agreement": GasAgreementType,
"annualConsumption": GasConsumption,
"quotedProducts": GasQuotedProduct,
"rateType": "successful-case-once-sea-left"
}GasTerminationOutput
Output data related to a LeaveSupplier journey for the gas market.
Fields
| Name | Description |
|---|---|
|
Attendant name. |
|
Attendant phone number. |
|
Attendant phone number type. |
|
The relationship of the on-site attendant to the Account holder. |
|
Memo. |
|
Whether on-site attendance is required. |
|
Whether customer phone contact is required for on-site attendance. |
|
Hour requested by the customer for on-site attendance. |
|
Time slot requested by the customer for on-site attendance. |
|
Date when supply point is disconnected. |
|
The market supply point identification number. |
Example
{
"supplyPointIdentifier": "20043058",
"supplyEndDate": "1977-02-14",
"onSiteAttendance": true,
"attendantName": "car-law-so-of-threat",
"attendantType": "FAMILY",
"requestedOnSiteTimeSlot": "AM",
"requestedOnSiteHour": "_0000",
"phoneContactRequired": true,
"attendantPhoneNumber": "hospital-agreement-ahead-century-story",
"attendantPhoneNumberType": "HOME",
"memo": "whose-man-someone-few-cut"
}GasTieredProduct
Product for the gas market.
Fields
| Name | Description |
|---|---|
|
Product code. |
|
List of consumption product rates. |
|
Human friendly name to be displayed in interfaces. |
|
A JSON object containing extra information. |
|
Unit type for standing charge. |
|
List of standing charge product rates. |
Example
{
"code": "special-detail-cause-there-specific",
"displayName": "doctor-leg-travel-lead-coach",
"params": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"standingChargeUnitType": "tell-price-tough-them-whether",
"standingCharges": TieredStandingCharge,
"consumptionCharges": TieredConsumptionRate
}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
}GenerateCreditCardToken
Generate a credit card token in GMO, which can be used for storing credit card details against it, using GMO's JavaScript SDK.
Fields
| Name | Description |
|---|---|
|
GMO credit card token. |
Example
{
"creditCardToken": "away-sure-become-per-memory"
}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": "data-fear-condition-example-picture",
"key": "technology-character-week-provide-easy",
"fields": {"key": "value"}
}GenerateLeadsFileAttachmentsPreSignedUrl
Generate a pre-signed URL for uploading a leads attachment file.
Fields
| Name | Description |
|---|---|
|
Input fields required to generate a presigned S3 post for leads file attachment. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"leadsFileAttachmentPreSignedUrl": LeadsFileAttachmentPresignedPostType
}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": "movie-behavior-part-west-record",
"tokenExpiryDatetime": "1982-05-20T04:35:12.338094+00:00",
"scope": "SUBMIT_METER_READINGS"
}Fields
| Name | Description |
|---|---|
|
The product for the generation agreement. |
|
Agreement valid-from datetime. |
|
Agreement valid-to datetime. |
Example
{
"product": Product,
"validFrom": "2003-07-25T19:52:58.093316+00:00",
"validTo": "1984-07-16T00:03:41.682203+00:00"
}Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per kWh without tax. |
|
Price per kWh including tax. |
|
Region of operation. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "appear-hour-mouth-tax-stay",
"regionOfOperation": "world-gas-six-community-still",
"band": "total-article-eight-senior-as",
"validFrom": "2020-01-14T09:59:22.999394+00:00",
"validTo": "2004-10-15T11:41:48.521041+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 11,
"pricePerUnitIncTax": "1.0"
}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": "career-scene-role-big-business",
"refreshFrequency": 9,
"screenData": "play-affect-feel-eight-stand"
}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": "walk-until-serious-game-soon"
}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": "lot-real-but-audience-direction"
}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": "magazine-scientist-history-likely-ahead"
}Fields
| Name | Description |
|---|---|
|
Currency. |
|
Gross amount. |
|
Net amount. |
|
Grant type. |
Example
{
"type": "mean-economy-shoulder-couple-even",
"netAmount": 658.23,
"grossAmount": 633.68,
"currency": "return-cut-performance-room-discussion"
}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": 26315711,
"marketName": "help-chance-guy-later-note",
"productType": GoodsProductType,
"code": "outside-pretty-think-per-hospital",
"internalName": "particularly-above-boy-behavior-itself",
"customerName": "run-until-ago-sound-property",
"notes": "capital-partner-author-few-property",
"description": "suffer-own-seek-support-history",
"availableFrom": "2013-12-06",
"availableTo": "2016-05-22",
"pricePerUnit": 861.44,
"grossPricePerUnit": 385.82,
"currency": "skill-send-mother-seek-before"
}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": 18,
"edgeCount": 97
}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": "quality-free-pull-moment-exactly"
}Example
{
"code": "top-show-value-program-word",
"internalName": "well-public-sport-discussion-able"
}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": "series-peace-result-involve-play",
"ledgerId": "56257590",
"ledgerNumber": "view-myself-carry-dinner-whole",
"goodsSaleItems": [GoodsSaleItem],
"goodsGrants": [GoodsGrant],
"marketName": "key-list-Democrat-individual-impact",
"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": "65168581",
"code": "yes-half-easy-building-artist",
"totalNetAmount": 62,
"quotedAt": "1985-03-27T12:16:31.467935+00:00",
"goodsQuotedProducts": [GoodsQuotedProduct],
"hasQuoteExpired": true
}Fields
| Name | Description |
|---|---|
|
The ID of the quote share. |
Example
{
"id": "88998510"
}Fields
| Name | Description |
|---|---|
|
Currency. |
|
Net amount. |
|
Number of units. |
|
Price per unit. |
|
Product code. |
Example
{
"product": "system-year-could-company-pick",
"numberOfUnits": 61,
"pricePerUnit": 87,
"netAmount": 100,
"currency": "run-long-college-receive-feeling"
}Fields
| Name | Description |
|---|---|
|
Currency. |
|
Gross amount. |
|
Net amount. |
|
Number of units. |
|
Price per unit. |
|
Product code. |
Example
{
"product": "movement-institution-lawyer-effect-rock",
"numberOfUnits": 47,
"pricePerUnit": 234.51,
"netAmount": 13.16,
"grossAmount": 755.7,
"currency": "live-stand-table-form-see"
}GrantUserAccessToBusiness
The possible errors that can be raised are:
- KT-CT-5463: Unauthorized.
- KT-CT-11107: Unauthorized.
- KT-CT-13501: 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]
}GroupType
Represents a group of components presented as a choice.
Fields
| Name | Description |
|---|---|
|
Customer-facing description of the group. |
|
Customer-facing name for the group. |
|
Unique identifier of the group. |
|
Internal name for the group. |
|
Maximum number of components that can be selected from this group. |
|
Minimum number of components that must be selected from this group. |
|
Nested offering components within this group. |
|
Product components within this group. |
Example
{
"identifier": "35121275",
"internalName": "society-half-ball-already-face",
"customerName": "tax-respond-dark-toward-world",
"customerDescription": "set-true-four-morning-authority",
"minCardinality": 84,
"maxCardinality": 51,
"productComponents": [ProductComponentType],
"offeringComponents": [OfferingComponentType]
}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": "worker-certainly-road-building-trip",
"displayName": "plan-why-him-show-room",
"description": "member-condition-especially-dog-response",
"identifier": "73850919",
"isVariable": true,
"guaranteeOfOriginPercentage": "ZERO"
}HardshipAgreementType
Represents a Hardship Agreement for a particular Account.
Fields
| Name | Description |
|---|---|
|
These are internal notes detailing the hardship. |
|
|
|
|
|
|
|
|
|
Example
{
"id": "30847155",
"hardshipType": "DEATH_IN_FAMILY",
"hardshipDetails": "throw-clearly-certainly-or-establish",
"hardshipEntryReason": "SELF_IDENTIFIED",
"paymentPlanDetails": "letter-child-year-fall-special",
"startDate": "1975-04-21"
}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": "61359193",
"deviceType": "BATTERIES",
"provider": "BYD",
"params": HeatPumpParamsType
}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
}Example
{
"heatPumpId": "73080552",
"model": "pull-if-fund-together-court",
"powerInKw": "1.0",
"isDeprecated": true
}Fields
| Name | Description |
|---|---|
|
The make (manufacturer) of the device. |
Example
{
"make": "ago-case-expert-coach-effect"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"make": "set-yet-herself-matter-although",
"models": [HeatPumpVariantModelsType]
}Fields
| Name | Description |
|---|---|
|
Whether a statement is currently held. |
|
Reason for statement being held. |
Example
{
"isHeld": true,
"reason": "notice-protect-change-place-than"
}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": "state-see-event-card-still",
"horizontalAlignment": "START",
"accessibilityHidden": true,
"accessibilityLabel": "similar-least-political-ready-kitchen",
"id": "67393376",
"typename": "feel-project-remain-daughter-coach"
}ImportReadingsConnection
Pagination for readings representing incoming utility flow e.g., usage or consumption..
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": ImportReadingsEdge,
"totalCount": 31,
"edgeCount": 16
}ImportReadingsEdge
A Relay edge containing a ImportReadings and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Reading,
"cursor": "hour-admit-officer-practice-your"
}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": 32,
"recent": 48
}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": "29762938",
"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": "toward-nature-later-camera-look",
"escalationStartAt": "1986-07-04T19:42:48.119050+00:00"
}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": "A-8EB9FA84"
}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": "establish-own-new-large-investment"
}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": "game-paper-size-maybe-experience",
"url": "food-stand-thought-success-different"
}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": "society-recently-support-us-garden",
"switchDate": "1991-08-08"
}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": "produce-compare-recent-such-cover",
"secretToken": "sense-population-teach-brother-beautiful"
}InitiateSwitchIn
Creates a domestic account and initiates a switch-in for that account.
The possible errors that can be raised are:
- KT-JP-3902: Payment instruction creation using the same card number on the same day is not allowed.
- KT-JP-3903: Unable to create payment customer.
- KT-JP-3904: Unable to change card with token.
- KT-JP-4103: Please set a password for the user before creating a new one using the same information.
- KT-JP-4104: Unable to create account for user.
- KT-JP-4105: Unable to reactivate account.
- KT-JP-4106: Unable to create account due to schedule conflict.
- KT-JP-4504: Please fill in correct SPIN which is registered in OCCTO.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Account number for the resolved account. |
|
Indicates if the user has a usable password and can log in immediately. |
|
Hashed account application ID. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Token for the resolved user. |
|
ID of the resolved user. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountNumber": "A-8244965D",
"token": "determine-industry-rise-choice-hospital",
"userId": "79009069",
"hasUsablePassword": true,
"hashedAccountApplicationId": "73461549"
}Fields
| Name | Description |
|---|---|
|
The icon code point. |
|
The ID of the object |
|
The ink bucket name. |
Example
{
"id": "58973258",
"name": "room-western-right-nature-suddenly",
"icon": "head-describe-many-stand-marriage"
}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": "front-thank-act-rather-yet",
"displayName": "remember-plan-really-under-everyone"
}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": "37389031",
"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": "necessary-field-world-money-short"
}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": ["catch-attention-happy-summer-reveal"],
"fromHandle": "behind-answer-particular-project-her",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "1984-01-28T00:07:39.670480+00:00",
"subject": "share-mission-rich-one-college",
"displayContent": "help-student-music-case-space",
"attachments": InkMessageAttachment,
"cc": "building-camera-wonder-apply-second",
"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": "28711037",
"direction": "INBOUND",
"fromHandle": "democratic-color-consumer-education-really",
"toHandle": "save-let-walk-perform-partner",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "1986-05-05T22:15:14.354188+00:00",
"displayContent": "choose-look-discussion-risk-amount"
}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": "hour-exist-hotel-tough-make",
"toHandle": "dinner-degree-score-though-discussion",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "1983-01-18T01:13:01.002067+00:00",
"lineMessage": LineMessage,
"isChannelLine": true,
"attachments": InkMessageAttachment,
"tags": InkTag
}InkLiveChatConversation
Ink live chat
Fields
| Name | Description |
|---|---|
|
The relay ID of the live chat conversation. |
Example
{
"relayId": "87467285"
}InkLiveChatMessage
This type wraps around the Message type for a Live Chat message.
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": "35012549",
"direction": "INBOUND",
"fromHandle": "main-campaign-speak-right-myself",
"toHandle": "page-military-common-fast-memory",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2007-09-23T01:30:00.021760+00:00",
"displayContent": "stop-inside-interesting-future-seem"
}Fields
| Name | Description |
|---|---|
|
The url for fetching the attachment. |
|
The filename. |
|
The size in bytes. |
Example
{
"filename": "expect-to-up-experience-method",
"fetchUrl": "raise-around-surface-step-may",
"sizeInBytes": 62
}Fields
| Name | Description |
|---|---|
|
The type of the account linked to the conversation of the message. |
|
The list of accounts related to the message. |
|
The list of the buckets the message is in. |
|
The id of the conversation the message belongs to. |
|
The hour at which the message arrived in Ink. |
|
The number of hours the customer has been waiting for a response to their previous message. |
|
Whether the conversation that the message belongs to is assigned to a user bucket. |
|
Whether the message is the first one sent by the contact. |
|
Whether the message starts a new thread in its conversation. |
|
The operation team that handles the message. |
|
The codes of the auto replies that have been sent to the contact in the last 6 months. |
|
The body of the latest comms SMS message sent to the customer, if the message is an sms. |
|
The week day at which the message arrived in Ink. |
Example
{
"accounts": "avoid-religious-measure-ground-or",
"accountType": "she-recognize-as-enjoy-tree",
"buckets": ["question-care-but-community-education"],
"conversationId": 27898583,
"hourOccurredAt": 75,
"hoursWaiting": 78,
"isAssignedToUserBucket": true,
"isFirstFromContact": true,
"isNewThread": true,
"opsTeam": "student-nature-arrive-some-wish",
"recentlyReceivedAutoReplies": "next-east-environment-six-free",
"replyToCommsSms": "pull-north-risk-up-operation",
"weekDayOccurredAt": 63
}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": "1987-03-13T09:07:32.220653+00:00",
"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": "38121191",
"content": "better-follow-some-most-show",
"isPinned": true,
"occurredAt": "1975-05-10T20:54:25.707913+00:00"
}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": "finish-time-attack-prepare-community",
"toHandle": "stage-author-agree-condition-attorney",
"displayContent": "plant-story-year-in-themselves",
"rawPlainTextContent": "community-then-resource-light-control",
"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": "heavy-building-visit-game-she",
"toHandle": "national-skin-quite-pick-network",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "1977-04-26T12:30:23.157244+00:00",
"displayContent": "democratic-scientist-me-here-remember",
"isChannelSms": true,
"tags": InkTag
}Fields
| Name | Description |
|---|---|
|
|
|
The entries in the storyline. |
|
When the storyline was generated. |
|
The ID of the object |
|
|
|
|
|
|
|
Example
{
"id": "69828857",
"topic": "yourself-always-wall-show-idea",
"summary": "here-leg-shake-design-enough",
"generatedAt": "1985-02-03T11:32:49.746788+00:00",
"neuralinkRequestId": "50e87e7d-0c54-4b45-81be-38f6b3962391",
"createdAt": "2010-09-24T10:20:58.146293+00:00",
"updatedAt": "2017-09-14T16:49:54.212335+00:00",
"entries": InkStorylineEntry
}Fields
| Name | Description |
|---|---|
|
The content of the storyline entry. |
|
The optional related object ID of the entry. |
|
The type of the storyline entry. |
|
The ID of the object |
|
Whether this entry is identified as the root cause of the issue. |
|
The time the storyline entry occurred. |
|
Optional URL related to the storyline entry. |
Example
{
"id": "64261397",
"entryType": "middle-popular-artist-nothing-science",
"occurredAt": "2017-07-08T17:43:57.584791+00:00",
"content": "blue-scene-certain-sea-able",
"url": "of-everything-ability-wall-big",
"contentId": 17092727
}Example
{
"id": "92533170",
"name": "surface-help-music-rate-image"
}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": "common-worry-reason-close-marriage",
"toHandle": "during-song-teacher-garden-leader",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "1972-08-29T01:26:55.938768+00:00",
"vendorId": "45880728",
"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": "generation-market-culture-investment-Congress",
"toHandle": "than-subject-against-laugh-network",
"delivery": InkMessageDelivery,
"contactChannelIdentity": InkContactChannelIdentity,
"occurredAt": "2008-08-19T16:58:22.699336+00:00",
"vendorId": "44709631",
"whatsappContent": WhatsAppTextMessage,
"isChannelWhatsapp": true,
"tags": InkTag
}InputFieldErrorType
Represents a validation error for a specific input field.
Fields
| Name | Description |
|---|---|
|
The error message to display for this field. |
|
The key of the input field with the error. |
|
The value that was submitted for the field. |
Example
{
"inputFieldKey": "cut-game-kind-final-religious",
"inputFieldValue": "institution-democratic-arrive-popular-very",
"errorMessage": "six-cold-image-seem-which"
}InputType
Represents an input in the product catalog.
Fields
| Name | Description |
|---|---|
|
List of bands for the input. |
|
Description of the input. |
|
Unique identifier of the input. |
|
Whether the input can be edited by users. |
|
Whether the input is external (imported from another domain). |
|
Display label for the input. |
|
Market the input belongs to. If null, the input is available for all markets. |
|
Section the input belongs to. |
|
Unit of the input. |
Example
{
"identifier": "37649324",
"label": "a-guy-number-also-mean",
"description": "miss-term-stock-difficult-positive",
"section": "CHARACTERISTICS",
"marketName": "because-civil-relationship-indicate-between",
"bands": "free-administration-plant-art-fine",
"unit": "rise-nor-economy-somebody-throw",
"isEditable": true,
"isExternal": true
}InstigateContractVariationOutput
Output type for instigating a contract variation.
Fields
| Name | Description |
|---|---|
|
The contract with the varied terms. |
Example
{
"contract": Contract
}Fields
| Name | Description |
|---|---|
|
The product characteristic. |
|
The integer value of the characteristic. |
|
A string representation of a characteristic value, for convenience. |
Example
{
"integerValue": 50
}IntegerType
Graphene type object to represent integer values
Fields
| Name | Description |
|---|---|
|
Value of this field. |
Example
{
"integerValue": 87
}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 |
Example
{
"type": "LINE",
"status": "ACTIVE"
}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": "Congress-he-carry-movement-lose",
"metaData": MeasurementsMetadataOutput,
"value": "1.0",
"unit": "poor-school-hot-safe-small",
"readAt": "1985-05-05T10:33:17.093818+00:00",
"startAt": "1995-11-09T08:03:13.804960+00:00",
"endAt": "1988-12-16T12:47:01.082611+00:00",
"durationInSeconds": 89,
"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": 29043691
}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]
}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": 86,
"edgeCount": 37
}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": "cut-reveal-run-occur-how"
}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. |
|
Unique identifier for the invoice billing document. |
|
The invoiced amount of the billing document. |
|
The unique billing document's reference that can be used for identifying it externally. |
|
The date due for payment for the invoice. |
|
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": 68769045,
"firstIssued": "2021-04-24T16:06:18.880241+00:00",
"pdfUrl": "last-fine-organization-single-citizen",
"annulledBy": AnnulmentBillingDocumentType,
"number": "color-avoid-modern-sort-recently",
"invoicedAmount": 20,
"totalCharges": InvoiceTotalType,
"totalCredits": InvoiceTotalType,
"transactions": BillTransactionConnectionTypeConnection,
"documentDebtPosition": BillingDocumentPositionType,
"paymentDueDate": "2020-03-10",
"billingFrom": "2020-08-05T10:09:06.469881+00:00",
"billingTo": "2010-08-31T22:24:52.472699+00:00"
}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": 99,
"taxTotal": 64,
"grossTotal": 73
}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": "23211864",
"billType": "STATEMENT",
"fromDate": "2010-04-14",
"toDate": "2019-12-14",
"temporaryUrl": "generation-cell-admit-agreement-market",
"issuedDate": "2002-07-10",
"attachments": BillingAttachmentConnectionTypeConnection,
"identifier": "90623906",
"grossAmount": 21,
"isAnnulled": true,
"totalCharges": InvoiceTotalType,
"totalCredits": InvoiceTotalType,
"totalPayments": 64,
"transactions": BillTransactionConnectionTypeConnection,
"representations": BillRepresentationConnectionTypeConnection
}ItemProfileType
Represents the characteristics and configuration of an ordered item.
Fields
| Name | Description |
|---|---|
|
The characteristic values for this item profile. |
Example
{
"characteristics": {"key": "value"}
}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": 85,
"edgeCount": 16
}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": "thousand-similar-from-prepare-goal"
}JoinSupplierProcessDataType
Data associated with a JoinSupplier process.
Fields
| Name | Description |
|---|---|
|
Affiliate link for the join supplier journey. |
|
Detailed reason for joining the supplier. |
|
The note associated with this join supplier process data. |
|
Reason for joining the supplier. |
|
When the journey was requested. |
|
Sales channel. |
|
Sales subchannel. |
|
Reference to the stored payment method details. |
|
The supply point context data. |
Example
{
"requestedAt": "1998-05-30T14:52:49.973740+00:00",
"salesChannel": "a-long-stop-tough-thank",
"salesSubchannel": "single-move-start-music-writer",
"affiliateLink": AffiliateLinkType,
"supplyPointContexts": SupplyPointContextDataInterface,
"note": "fire-eye-guess-woman-without"
}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": "31741726",
"status": "PENDING",
"supplyPoints": SupplyPointConnectionTypeConnection,
"number": "fact-young-rock-word-her",
"currentProcessData": JoinSupplierProcessDataType
}Fields
| Name | Description |
|---|---|
|
The konbini payment expiration time. |
|
The konbini payment voucher email is sent to this email address. |
|
The konbini payment voucher url. |
Example
{
"receiptEmail": "stock-result-enjoy-science-interest",
"expireAt": "2019-05-12T07:45:13.784095+00:00",
"voucherUrl": "spend-voice-security-trouble-charge"
}Fields
| Name | Description |
|---|---|
|
Stripe Konbini Payment reference. |
Example
{
"reference": "walk-sport-laugh-institution-place"
}Fields
| Name | Description |
|---|---|
|
The unique identifier for the sales record. |
|
The opportunity code associated with the sales record. |
Example
{
"identifier": "36335915",
"opportunityNumber": "successful-place-relationship-ask-truth"
}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": "13023332",
"provider": "BYD",
"vehicleMake": "letter-financial-near-event-modern",
"vehicleModel": "deal-language-discussion-would-language",
"vehicleBatterySizeInKwh": "1.0",
"chargePointMake": "interview-fast-value-exactly-art",
"chargePointModel": "deep-event-trouble-you-know",
"chargePointPowerInKw": "1.0",
"status": "forget-imagine-minute-ability-control",
"suspended": true,
"hasToken": true,
"createdAt": "1970-05-20T05:16:00.433299+00:00",
"stateOfChargeLimit": StateOfChargeLimit,
"testDispatchFailureReason": "NONE"
}Fields
| Name | Description |
|---|---|
|
The name of the affiliate organisation associated with the sales record. |
|
The unique identifier for the sales record. |
|
The sales channel associated with the sales record. |
Example
{
"identifier": "19539823",
"salesChannel": "century-claim-line-per-few",
"affiliateOrganisationName": "however-training-budget-open-bring"
}KrakenVersionType
Information about what version of Kraken is being executed by this service.
Fields
| Name | Description |
|---|---|
|
The git commit SHA that is being executed. |
|
Whether this version is pinned to a specific version. |
|
The version number that is being executed. |
Example
{
"number": "well-author-east-nature-past",
"SHA": "fire-similar-partner-opportunity-treat",
"isPinned": true
}LabelValueType
A label-value pair for dropdown options.
Fields
| Name | Description |
|---|---|
|
Display label (may be null for dimensionless units). |
|
Value identifier. |
Example
{
"label": "along-degree-glass-cause-artist",
"value": "media-down-culture-employee-suggest"
}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. |
|
The interest policy to use for late payment fee calculations. |
|
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": "player-more-gas-nor-day",
"displayName": "share-cover-mission-before-why",
"description": "range-business-reduce-pull-size",
"identifier": "49157779",
"isVariable": true,
"flatFeeAmount": "1.0",
"percentageFee": "1.0",
"percentageIntervalDays": "1.0",
"interestPolicyName": "story-entire-our-body-doctor"
}Fields
| Name | Description |
|---|---|
|
THe payment deadline for the most recent 'Scheduled' Konbini payment. |
|
The payment voucher URL of the most recent 'Scheduled' Konbini payment. |
Example
{
"url": "appear-piece-represent-shake-kind",
"paymentDate": "1991-12-17"
}Fields
| Name | Description |
|---|---|
|
Affiliate organization assigned to this lead. |
|
The username of the user the lead is assigned to. |
|
List of consents for the lead. |
|
The contacts for the lead. |
|
The type of the lead. |
|
National Identifier of the lead. |
|
Lead number. |
|
List of opportunities for the lead. |
|
The sales channel that this lead was captured by. |
|
The sales funnel this lead is in. |
|
The current stage of the sales funnel that this lead is in. |
Example
{
"number": "agree-research-parent-trip-ago",
"nationalId": "74333907",
"leadType": "citizen-protect-win-to-compare",
"salesFunnel": SalesFunnel,
"stage": SalesFunnelStage,
"salesChannel": SalesChannelType,
"assignedToOrganization": AffiliateOrganisationType,
"assignedToUsername": "central-star-state-glass-speech",
"consents": [ConsentOutput],
"opportunities": [OpportunityOutput],
"contacts": [LeadContactDetailsType]
}Fields
| Name | Description |
|---|---|
|
List of block list hits found. |
|
Indicates if the block list validation passed. |
Example
{
"valid": true,
"blockListHits": ["PM-where-pull-suffer-note"]
}Fields
| Name | Description |
|---|---|
|
The email address of the contact. |
|
The family name of the contact. |
|
The given name of the contact. |
|
The phone number of the contact. |
|
The roles of the contact. |
Example
{
"givenName": "Kathy",
"familyName": "Cruz",
"email": "through-five-street-hair-answer",
"phoneNumber": "them-movement-environment-movie-bank",
"roles": "LEGAL_CONTACT"
}Fields
| Name | Description |
|---|---|
|
The ID of the lead. Deprecated The 'leadId' field is deprecated. |
|
The number of the lead. |
Example
{
"leadId": "56040271",
"number": "card-key-international-onto-she"
}Fields
| Name | Description |
|---|---|
|
Lead's linked account number. |
|
Team assigned to this lead. |
|
User assigned to this lead. |
|
Lead billing address. |
|
Lead billing name. |
|
Lead billing rich address. |
|
Lead brand. |
|
List of consents for the lead. |
|
Lead legal contact email. |
|
Extra details about the lead as key/value pairs. |
|
Extra details about the lead. Deprecated The 'extraDetails' field is deprecated. |
|
Lead legal family name. |
|
The lead funnel this lead is in. |
|
Lead legal given name. |
|
Lead ID. |
|
The type of the lead. |
|
National Identifier of the lead. |
|
Lead number. |
|
Lead legal contact phone number. |
|
Lead sales channel. |
|
Current stage in a funnel. |
Example
{
"leadId": "22568854",
"givenName": "John",
"familyName": "Kennedy",
"billingName": "theory-heart-reflect-throw-eat",
"billingAddress": AddressOutput,
"billingRichAddress": RichAddressType,
"email": "old-indeed-prevent-animal-against",
"phoneNumber": "effort-store-growth-important-their",
"number": "maybe-like-structure-peace-response",
"stage": "reality-some-behind-personal-owner",
"extraDetails": {"key": "value"},
"extraDetailItems": [ExtraDetail],
"brand": "happen-behind-factor-gas-religious",
"salesChannel": "adult-test-against-ability-north",
"assignedToTeam": "news-article-myself-race-eat",
"assignedToUser": "same-PM-anything-myself-member",
"nationalId": "53554940",
"leadType": "out-weight-risk-after-hope",
"consents": [ConsentOutput],
"accountNumber": "A-C2D2B5FE"
}Fields
| Name | Description |
|---|---|
|
Number of nodes in the edge. |
|
Contains the nodes in this connection. |
|
Pagination data for this connection. |
|
Total number of nodes. |
LeadsEdge
A Relay edge containing a Leads and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": Lead,
"cursor": "protect-soon-answer-sound-rate"
}LeadsFileAttachmentPresignedPostType
Metadata returned when generating a pre-signed post URL for a leads file attachment.
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": "wall-interest-onto-cultural-key",
"bucket": "across-campaign-probably-ok-man",
"preSignedUrl": "benefit-after-thus-beyond-all",
"fields": {"key": "value"}
}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": 20,
"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": "news-natural-standard-staff-bed"
}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": "60861550",
"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": "simply-send-light-party-draw"
}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": "32868685",
"leaveSupplierProcessId": "62881280",
"message": "few-positive-by-dog-stop"
}Fields
| Name | Description |
|---|---|
|
A list of Electricity leave supplier details. |
|
A list of Gas leave supplier details. |
Example
{
"electricitySupplyPointData": [ElectricityTerminationOutput],
"gasSupplyPointData": [GasTerminationOutput]
}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": 44,
"edgeCount": 9
}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": "suggest-list-box-join-sit"
}LeaveSupplierProcessData
Represents data associated with a Leave Supplier process.
Fields
| Name | Description |
|---|---|
|
Detailed reason for leaving the supplier. |
|
The address where final payment bill is sent. |
|
The future billing address for the customers account. |
|
The market data associated with the process. |
|
Additional market-agnostic parameters for the leave supplier process. |
|
Reason for leaving the supplier. |
|
The time at which the process was initiated. |
|
The requested supply end date. |
|
Whether the exit fee is to be waived. |
Example
{
"reason": "CONSUMER_REQUEST",
"detailedReason": "MOVING",
"params": {"key": "value"},
"finalBillPayerAddress": RichAddressType,
"requestedAt": "1994-02-13T10:52:52.818670+00:00",
"requestedSupplyEndDate": "1990-04-18",
"marketData": LeaveSupplierMarketOutputType,
"waiveExitFee": true,
"futureBillingAddress": RichAddressType
}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. |
|
Data associated with the Leave Supplier process. |
|
The status of the process. |
|
The supply points associated with the process. |
Example
{
"id": "40025910",
"status": "PENDING",
"number": "tonight-develop-same-heart-learn",
"supplyPoints": SupplyPointConnectionTypeConnection
}LeaveSupplierUpdated
Leave supplier was successfully updated.
Fields
| Name | Description |
|---|---|
|
The message to display to the user on leave supplier update. |
Example
{
"message": "main-cultural-bag-TV-serve"
}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 method at a point in time. The possible errors that can be raised are:
|
|
The customer's preferred payment methods. |
|
Payments with non-concluded re-presentation. |
|
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. |
|
The usable payment instructions for this ledger. |
Example
{
"id": "96708514",
"name": "market-remember-black-area-impact",
"number": "role-crime-here-must-level",
"ledgerType": "break-day-attorney-behind-often",
"balance": 23,
"amountOwedByCustomer": 7,
"affectsAccountBalance": true,
"statements": StatementBillingDocumentConnectionTypeConnection,
"invoices": InvoiceBillingDocumentConnectionTypeConnection,
"transactions": TransactionConnectionTypeConnection,
"repaymentRequests": RepaymentRequestConnectionTypeConnection,
"refundRequests": RefundRequestConnectionTypeConnection,
"acceptsPayments": true,
"paymentAdequacy": PaymentAdequacyDetailsType,
"creditTransferPermissionsData": CreditTransferPermissionsDataType,
"paymentPreferences": PaymentPreferenceConnectionTypeConnection,
"paymentPreferenceAtTime": PaymentPreferenceUnion,
"debtLedger": LedgerType,
"agreements": AgreementConnection,
"usablePaymentInstructions": PaymentInstructionConnectionTypeConnection,
"supportsStatements": true,
"supportsInvoices": true,
"currentDirectDebitInstructionInvalidatedWithVendor": true,
"paymentsWithNonConcludedRePresentation": PaymentWithNonConcludedRePresentationConnectionTypeConnection
}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
}LifecycleType
Represents the lifecycle of an offering.
Fields
| Name | Description |
|---|---|
|
DateTime when the offering was activated. |
|
Unique lifecycle code. |
|
Maximum version number reached. |
|
Identifier of the previous version of this offering. |
|
Current status of the offering. |
|
Current version of the offering. |
Example
{
"code": "card-determine-note-together-night",
"version": 37,
"maxVersion": 91,
"previousOffering": "37636044",
"status": "DRAFT",
"activatedAt": "1986-02-01T12:09:03.110640+00:00"
}Fields
| Name | Description |
|---|---|
|
Lifeline Agency Application status. |
Example
{
"status": "AWAITING_CUSTOMER_DATA_VALIDATION"
}Fields
| Name | Description |
|---|---|
|
The address of the LLA Branch. |
|
The business start time of the LLA Branch. |
|
The business end time of the LLA Branch. |
|
The name of the LLA Branch. |
|
The name of the LLA Branch representative. |
|
The phone number of the LLA Branch representative. |
|
The weekend business start time of the LLA Branch. |
|
The weekend business end time of the LLA Branch. |
Example
{
"name": "energy-provide-capital-notice-happen",
"address": "price-mission-must-weight-week",
"representativeName": "check-always-during-act-Mr",
"representativePhoneNumber": "hold-source-human-create-back",
"businessHoursFrom": "08:21:25.987108",
"businessHoursTo": "14:59:11.923828",
"weekendBusinessHoursFrom": "20:18:36.353042",
"weekendBusinessHoursTo": "07:59:17.370847"
}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": "owner-involve-others-win-structure",
"field": "human-able-house-sport-all"
}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": 32,
"length": 24,
"productId": "33410612",
"emojiId": "47723226"
}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 |
Example
{
"type": "LINE",
"status": "ACTIVE",
"displayName": "include-himself-usually-five-then"
}LineItemConnectionTypeConnection
Paginator of LineItemType.
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": LineItemConnectionTypeEdge,
"totalCount": 82,
"edgeCount": 50
}LineItemConnectionTypeEdge
A Relay edge containing a LineItemConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": LineItemType,
"cursor": "different-we-mouth-ability-office"
}Fields
| Name | Description |
|---|---|
|
The unit of the contracted capacity, e.g. 'kVA', 'kW', or 'A'. |
|
The value of the contracted capacity, e.g. '30'. |
|
The currency of the charge. |
|
The electricity supply point of the charge. |
|
The gas supply point of the charge. |
|
The gross amount charged. |
|
The net amount charged. |
|
The supplied quantity. |
|
The end of the period the charge covers. |
|
The start of the period the charge covers. |
|
The product code of the charge. |
|
The type of charge. Based on Product Rates registered in the support site. Will resolve to JPN_{MARKET}_{RATE_NAME}, for example JPN_ELECTRICITY_CONSUMPTION_STEPPED_03_01. |
Example
{
"startAt": "1980-05-09T00:26:03.897618+00:00",
"endAt": "1973-10-22T17:50:54.128062+00:00",
"netAmount": "1.0",
"numberOfUnits": "1.0",
"itemType": "dog-necessary-many-section-spring",
"settlementUnit": "daughter-base-capital-today-soon"
}LineLinkRedirectResponse
Link Successful. Complete link process with LINE.
Fields
| Name | Description |
|---|---|
|
Example
{
"redirectUrl": "model-project-report-hard-law"
}Fields
| Name | Description |
|---|---|
|
Keywords describing the sticker. |
|
Sticker package id. |
|
Sticker resource type. |
|
Sticker id. |
|
Text used to customize some stickers. |
Example
{
"packageId": "57013205",
"stickerId": "73304161",
"resourceType": "writer-respond-place-push-this",
"keywords": "speak-finish-again-past-idea",
"text": "charge-nation-from-since-a"
}Fields
| Name | Description |
|---|---|
|
The display content. |
|
The emojis in the message. |
Example
{
"displayContent": "street-operation-in-possible-sing",
"emojis": [LineEmoji]
}Fields
| Name | Description |
|---|---|
|
Example
{
"message": "accept-water-better-board-cost"
}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": "including-wonder-effort-push-energy",
"id": "34674070",
"typename": "they-stand-happy-floor-put",
"url": "official-serve-child-radio-memory"
}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": 85,
"consumption": ConsumptionBreakdownConnectionTypeConnection,
"averageMonthlyCharge": 85,
"existingMonthlyAmount": 47,
"balanceAdjustment": 76,
"currentBalance": 38,
"targetBalance": 61,
"reviewedOn": "1986-07-13"
}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": "39124841",
"scheme": "sit-product-others-deal-statement",
"number": "without-treatment-then-poor-always",
"status": "break-hand-child-design-enjoy"
}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": "86837319",
"ledgerType": "however-general-his-by-hold",
"value": "late-rich-enter-always-number",
"balanceBroughtForward": "cultural-less-much-discuss-strong",
"balanceCarriedForward": "no-will-trade-third-special",
"reasonCode": "think-build-center-almost-meet",
"idempotencyKey": "4d4f8ce2-cf89-4c5d-bd99-7946d5378391",
"postedAt": "2012-12-13T18:09:36.719201+00:00",
"accountNumber": "A-027D847E"
}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": "minute-performance-particular-democratic-stop"
}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": "1993-12-16T20:39:20.511100+00:00",
"requestedAt": "2009-03-12T02:05:57.439966+00:00",
"code": "father-trip-weight-wrong-nor",
"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": 47,
"edgeCount": 63
}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": "either-song-show-go-really"
}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": "12331375",
"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": 12,
"edgeCount": 49
}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": "guy-letter-home-without-wait"
}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": "science-read-itself-behind-north",
"id": "68934276",
"identifier": "33723814",
"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": "campaign-prevent-cover-within-as",
"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": 72,
"reasonToRecommendAmount": "MAX_AVAILABLE_AMOUNT",
"recommendedBalance": 78
}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": 8,
"edgeCount": 24
}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": "past-election-after-forget-situation"
}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": "themselves-government-none-cut-pressure",
"metaData": MeasurementsMetadataOutput,
"value": "1.0",
"unit": "reflect-common-lawyer-deal-stage",
"readAt": "2008-06-27T03:37:55.508096+00:00"
}Fields
| Name | Description |
|---|---|
|
Extras relating to the parent measurement node. |
|
Statistics relating to the parent measurement node. |
|
The source information relating to the parent measurement node. |
Example
{
"utilityFilters": UtilityFiltersOutput,
"statistics": [StatisticOutput],
"extras": [ExtrasOutput]
}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": "2013-06-29T19:41:35.324720+00:00",
"failedAt": "1978-01-06T12:42:35.346691+00:00"
}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": 74,
"edgeCount": 87
}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": "room-the-especially-administration-near"
}Fields
| Name | Description |
|---|---|
|
The key for the metadata. |
|
The metadata value. |
Example
{
"key": "order-government-stop-research-west",
"value": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
The type of METI credit. Can be either 'electricity' or 'gas'. |
|
The end of the period. |
|
The start of the period. |
|
The amount of the METI credit. |
Example
{
"creditType": "ELECTRICITY",
"startDate": "1987-01-05",
"endDate": "1994-03-07",
"unitPrice": "1.0"
}Fields
| Name | Description |
|---|---|
|
The type of MFA device. |
|
Whether the MFA device is confirmed or not. |
Example
{
"deviceType": "red-happy-bad-finish-agent",
"isConfirmed": true
}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": "culture-great-address-wait-environment",
"displayName": "certainly-although-hundred-without-account",
"description": "cultural-member-everything-certainly-live",
"identifier": "25755277",
"isVariable": true,
"length": 75,
"unitOfTime": "by-point-no-dark-involve"
}ModelYearRange
Range of model years supported for a device model.
If end year is null, all years after start year are supported.
Fields
| Name | Description |
|---|---|
|
Latest year model is supported. If null, all years after start year are supported. |
|
Earliest year model is supported. |
Example
{
"startYear": 53,
"endYear": 54
}Fields
| Name | Description |
|---|---|
|
|
|
The ISO-4217 code for the currency. |
Example
{
"amount": "1.0",
"currency": "position-today-student-must-research"
}Fields
| Name | Description |
|---|---|
|
Earliest possible move-in date. |
Example
{
"earliestMoveInDate": "2003-07-07"
}MoveInDateInvalid
Returned when a supplied move in date is invalid
Fields
| Name | Description |
|---|---|
|
The last day that a customer may request a move in. |
|
The field that for which this error should be associated. |
|
The error message to display to the user. |
|
The first day that a customer may request a move in. |
Example
{
"message": "it-general-special-plan-keep",
"field": "know-but-give-lead-owner",
"startDate": "2013-11-08",
"endDate": "1992-10-20"
}Fields
| Name | Description |
|---|---|
|
The requested move out date provided by the customer. |
Example
{
"requestedMoveInDate": "1982-11-30"
}MoveInSuccess
Returned upon a successful Move In request.
Fields
| Name | Description |
|---|---|
|
Kraken account number. |
|
Indicates if the user has a usable password and can log in immediately. |
|
Hashed account application ID. |
|
Kraken token. |
|
Kraken user id. |
Example
{
"accountNumber": "A-323DF2D4",
"token": "unit-arm-audience-wind-lead",
"userId": "58152276",
"hasUsablePassword": true,
"hashedAccountApplicationId": "71580174"
}MoveOutAndMoveInInitiated
MoveOut was successfully initiated.
Fields
| Name | Description |
|---|---|
|
The account number for the newly created account for the property the customer is moving in to. |
|
Indicates if the user has a usable password and can log in immediately. |
|
The message to display to the user on move out and move in initiation. |
|
Example
{
"accountNumber": "A-D0030F1F",
"token": "so-piece-strong-else-training",
"message": "set-speech-soldier-entire-society",
"hasUsablePassword": true
}MoveOutDateInvalid
Returned when a supplied move out date is outside of the OCCTO accepted range
Fields
| Name | Description |
|---|---|
|
The last day that a customer may request a move out. Always today + 31 days. |
|
The field that for which this error should be associated. |
|
The error message to display to the user. |
|
The first day that a customer may request a move out. Always today. |
Example
{
"message": "stuff-other-several-they-trade",
"field": "leader-require-single-subject-move",
"startDate": "1970-07-27",
"endDate": "1986-10-08"
}MoveOutInitiated
MoveOut was successfully initiated.
Fields
| Name | Description |
|---|---|
|
The message to display to the user on move out initiation. |
Example
{
"message": "situation-herself-into-beautiful-skill"
}Fields
| Name | Description |
|---|---|
|
Whether the move out request can be cancelled. |
|
The requested move out date provided by the customer. |
|
The status of the move out request. |
Example
{
"requestedMoveOutDate": "1990-04-02",
"canBeCancelled": true,
"status": "WAITING_TO_APPLY"
}Fields
| Name | Description |
|---|---|
|
All inferred routing attributes for team, location, and team groups (e.g., ['OPERATIONS_GROUP.TEAM.Team_A', 'OPERATIONS_GROUP.LOCATION.London', 'OPERATIONS_GROUP.GROUP_B']). Recommended for IVR usage. |
|
Location routing information for the selected team. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
The next operations team assigned in round-robin sequence. |
|
All operations team groups that the selected team belongs to. |
Example
{
"possibleErrors": [PossibleErrorType],
"team": Team,
"location": TeamLocation,
"teamGroups": TeamGroup,
"allInferredRoutingAttributes": "professional-then-thousand-agree-decide"
}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": "69780506",
"name": "necessary-simple-military-since-exactly",
"bundleId": "33560990",
"service": "GCM",
"externalProvider": "PINPOINT",
"externalProjectId": "33036635",
"description": "message-six-available-something-through",
"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": "enough-agent-father-shoulder-perhaps",
"username": "none-baby-art-star-professional"
}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
{
"text": "term-color-return-imagine-each",
"createdAt": "2007-06-21T15:28:53.997142+00:00",
"name": "discuss-law-majority-form-painting",
"pdfUrl": "name-prepare-produce-color-major",
"brandCode": "act-fund-hit-like-option",
"markdown": "different-call-wonder-hold-TV",
"html": "less-rock-condition-rest-own",
"version": "player-picture-father-behavior-develop",
"effectiveFrom": "1990-06-19T20:19:01.314162+00:00"
}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": "business-tough-tax-dog-decision",
"payload": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"refreshToken": "heavy-worry-bill-story-course",
"refreshExpiresIn": 24
}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": "apply-section-interview-health-close",
"refreshExpiresIn": 11
}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. |
|
The unique ID of the occupancy period. |
|
Whether the account associated with the occupancy period is an occupier account type. |
|
Number of occupants associated with this occupancy period. |
Example
{
"id": "94825402",
"effectiveFrom": "1978-01-16T09:30:38.268616+00:00",
"effectiveTo": "2005-04-29T05:37:56.242377+00:00",
"isOccupier": true,
"accountNumber": "A-4436F60F"
}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": 89,
"edgeCount": 18
}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": "check-charge-people-recent-left"
}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": "85720881",
"status": "PENDING",
"occupyAt": "1990-09-25T22:35:40.883797+00:00",
"supplyPoints": SupplyPointConnectionTypeConnection
}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": "61101921",
"quote": QuoteType_,
"description": "still-plant-may-bill-plan",
"validFrom": "1997-01-23T10:30:32.640044+00:00",
"validTo": "1986-05-05T05:41:23.948439+00:00",
"acceptedAt": "2004-01-07T02:19:18.070950+00:00",
"rejectedAt": "1995-05-23T11:31:20.655360+00:00",
"createdBy": ActorType
}OfferingComponentType
Represents a nested offering component within an offering.
Fields
| Name | Description |
|---|---|
|
The offering associated with this component. |
|
Unique identifier of the component. |
|
Initial/default quantity for this component. |
|
Maximum quantity of this component that can be selected. |
|
Minimum quantity of this component that can be selected. |
Example
{
"identifier": "47321254",
"minimumQuantity": 75,
"maximumQuantity": 91,
"initialQuantity": 23,
"component": OfferingType
}OfferingType
Represents a product offering in the catalog.
Fields
| Name | Description |
|---|---|
|
Customer-facing description of the offering. |
|
Customer-facing name of the offering. |
|
Groups of components with cardinality constraints. |
|
Unique identifier of the offering. |
|
Internal name used to identify the offering. |
|
Whether this offering is currently active. |
|
Whether this offering can be amended (only DRAFT offerings). |
|
Whether this offering is in draft status. |
|
Whether this offering has expired. |
|
Whether this is the first draft version (version 1, not yet activated). |
|
Whether this is the latest version of the offering. |
|
Whether this offering can be sold stand-alone. |
|
Lifecycle information for this offering. |
|
Nested offering components included in this offering. |
|
Product components included in this offering. |
|
Tags associated with this offering. |
|
Contract term template components included in this offering. |
Example
{
"identifier": "13675617",
"internalName": "while-up-alone-PM-decade",
"customerName": "man-television-why-thought-front",
"customerDescription": "family-may-color-when-finish",
"isSellable": true,
"lifecycle": LifecycleType,
"tags": [TagType],
"productComponents": [ProductComponentType],
"offeringComponents": [OfferingComponentType],
"termTemplateComponents": [TermTemplateComponentType],
"groups": [GroupType],
"isAmendable": true,
"isExpired": true,
"isActive": true,
"isDraft": true,
"isLatestVersion": true,
"isFirstDraft": 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": OnSiteJobsAppointmentActionConnectionTypeEdge,
"totalCount": 43,
"edgeCount": 52
}OnSiteJobsAppointmentActionConnectionTypeEdge
A Relay edge containing a OnSiteJobsAppointmentActionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OnSiteJobsAppointmentActionType,
"cursor": "feeling-always-act-recognize-mention"
}OnSiteJobsAppointmentActionType
An action linked to an On-Site Jobs Appointment.
Fields
| Name | Description |
|---|---|
|
The appointment stage at which this action is triggered. |
|
The name of the workflow. |
|
The current status of the workflow. |
Example
{
"actionTriggerStage": "POST_APPOINTMENT_BOOKING",
"workflowName": "factor-how-system-future-ok",
"workflowStatus": "SKIPPED"
}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": OnSiteJobsAppointmentConnectionTypeEdge,
"totalCount": 71,
"edgeCount": 99
}OnSiteJobsAppointmentConnectionTypeEdge
A Relay edge containing a OnSiteJobsAppointmentConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OnSiteJobsAppointmentType,
"cursor": "care-Mrs-miss-certain-half"
}Fields
| Name | Description |
|---|---|
|
Indicates whether all available appointment slots have been fetched. This is only relevant for booking adapters that support async timeslot fetching. For sync, it will always be True. If false, empty list of slots will be returned. |
|
List of available appointment slots. |
Example
{
"slots": OnSiteJobsAppointmentSlotType,
"isComplete": true
}Fields
| Name | Description |
|---|---|
|
The end datetime of the appointment slot. |
|
The unique identifier for this appointment slot. |
|
The start datetime of the appointment slot. |
Example
{
"startDatetime": "2021-04-05T15:25:59.798359+00:00",
"endDatetime": "2025-12-30T18:22:22.377130+00:00",
"slotId": "74dc9051-6c6d-4041-8de4-97548f8de3c2"
}Fields
| Name | Description |
|---|---|
|
The agent assigned to the appointment. |
|
A list of actions triggered by this appointment, across stages. |
|
A list of assets attached to this request. |
|
|
The cancellation category for this appointment. |
|
|
|
|
|
The communication strategy for this appointment. |
|
|
|
|
|
|
|
|
|
|
|
|
|
The work category for this appointment. |
|
|
|
The current status of the appointment. |
Example
{
"id": "d7fc9f08-73c3-43c9-bf8e-8de3f6f462b5",
"externalJobType": "natural-job-whatever-base-source",
"startAt": "1970-10-12T12:37:01.169995+00:00",
"endAt": "1982-08-24T16:31:04.810283+00:00",
"externalReference": "very-force-news-standard-meeting",
"jobDetails": {"key": "value"},
"jobNotes": {"key": "value"},
"comments": "story-voice-sea-score-check",
"cancellationSubCategory": "money-appear-attack-much-mention",
"krakenWorkCategory": "EXCHANGE",
"agent": "GENERIC_AGENT",
"status": "PENDING",
"commsStrategy": "SEND_ALL",
"cancellationCategory": "CANCELLED_BY_CUSTOMER",
"appointmentActions": OnSiteJobsAppointmentActionConnectionTypeConnection,
"assets": OnSiteJobsAssetConnectionTypeConnection
}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": OnSiteJobsAssetConnectionTypeEdge,
"totalCount": 45,
"edgeCount": 77
}OnSiteJobsAssetConnectionTypeEdge
A Relay edge containing a OnSiteJobsAssetConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OnSiteJobsAssetType,
"cursor": "decade-some-chance-then-let"
}OnSiteJobsAssetType
An On-Site Jobs Asset
Fields
| Name | Description |
|---|---|
|
|
|
|
|
The fuel type of the asset. |
|
The kind of the asset. |
|
The status of the asset. |
|
The internal identifier of the supply point associated with the asset. Deprecated The 'supplyPointIdentifier' field is deprecated. |
|
Example
{
"externalIdentifier": "10556255",
"additionalDetails": {"key": "value"},
"supplyPointInternalIdentifier": 52835443,
"supplyPointIdentifier": "98799195",
"status": "EXISTING",
"kind": "METER",
"fuelType": "ELECTRICITY"
}OnSiteJobsCheckResultsType
Check results for creating On-Site Jobs requests and appointments.
Fields
| Name | Description |
|---|---|
|
Results of appointment checks. |
|
Whether an appointment can be created (overall appointment check is PASS/WARNING). |
|
Whether a request can be created (overall request check is PASS/WARNING). |
|
Whether any of the appointment checks have warnings. |
|
Whether any of the request checks have warnings. |
|
Results of request checks. |
Example
{
"requestCheckResults": [CheckResultType],
"appointmentCheckResults": [CheckResultType],
"canCreateRequest": true,
"canCreateAppointment": true,
"hasRequestWarnings": true,
"hasAppointmentWarnings": true
}OnSiteJobsJobTypeType
Represents a job type available for on-site jobs requests.
Fields
| Name | Description |
|---|---|
|
The unique identifier for the job type. |
|
The human-readable name of the job type. |
Example
{
"id": "61361793",
"name": "industry-resource-keep-you-more"
}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": OnSiteJobsRequestActionConnectionTypeEdge,
"totalCount": 97,
"edgeCount": 78
}OnSiteJobsRequestActionConnectionTypeEdge
A Relay edge containing a OnSiteJobsRequestActionConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OnSiteJobsRequestActionType,
"cursor": "visit-would-nothing-choose-trip"
}OnSiteJobsRequestActionType
An action linked to an On Site Jobs Request.
Fields
| Name | Description |
|---|---|
|
The request stage at which this action is triggered. |
|
The name of the workflow. |
|
The current status of the workflow. |
Example
{
"actionTriggerStage": "POST_REQUEST_COMPLETION",
"workflowName": "important-so-take-onto-lose",
"workflowStatus": "SKIPPED"
}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": OnSiteJobsRequestConnectionTypeEdge,
"totalCount": 36,
"edgeCount": 55
}OnSiteJobsRequestConnectionTypeEdge
A Relay edge containing a OnSiteJobsRequestConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OnSiteJobsRequestType,
"cursor": "also-arm-bad-author-or"
}OnSiteJobsRequestType
An On Site Jobs Request
Fields
| Name | Description |
|---|---|
|
Request account. |
|
|
|
A list of appointments associated to this request. |
|
A list of assets attached to this request. |
|
|
|
|
The ID of the support user who created the request. |
|
|
|
|
|
|
|
List of supply points on request. |
|
The overall priority status of all actions linked to the request and its appointments. |
|
Request property. |
|
|
|
A list of actions attached directly to this request. |
|
Request status. |
|
Example
{
"id": "4a25d6d2-1874-428f-a76b-ad4050029fe8",
"reason": "experience-discussion-above-well-treatment",
"subReason": "beat-myself-finish-cause-benefit",
"isEmergency": true,
"externalReference": "as-method-record-crime-now",
"agent": "cause-age-computer-after-will",
"comment": "himself-house-heart-moment-part",
"account": "class-people-fine-happen-American",
"marketSupplyPoints": SupplyPointConnectionTypeConnection,
"property": PropertyType,
"status": "APPROVAL_PENDING",
"overallActionsStatus": "SKIPPED",
"requestActions": OnSiteJobsRequestActionConnectionTypeConnection,
"assets": OnSiteJobsAssetConnectionTypeConnection,
"appointments": OnSiteJobsAppointmentConnectionTypeConnection,
"createdBy": 49
}Fields
| Name | Description |
|---|---|
|
Example
{
"token": "never-per-although-born-debate"
}Fields
| Name | Description |
|---|---|
|
ID for the Operations Team. |
|
Name for the Operations Team. |
Example
{
"id": "92002671",
"name": "reach-pick-bed-mind-mean"
}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": OpportunitiesEdge,
"totalCount": 47,
"edgeCount": 95
}OpportunitiesEdge
A Relay edge containing a Opportunities and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": OpportunityOutput,
"cursor": "throughout-site-every-social-provide"
}Fields
| Name | Description |
|---|---|
|
Attachment category. |
|
Attachment filename. |
|
Attachment ID. |
Example
{
"id": "59983351",
"category": "LEAD_FILE",
"filename": "also-wait-according-generation-heavy"
}Fields
| Name | Description |
|---|---|
|
The date and time the file attachment will expire. |
|
Presigned URL for the file attachment. |
Example
{
"presignedUrl": "play-take-another-section-federal",
"expiresAt": "2024-05-27T14:08:31.883148+00:00"
}Fields
| Name | Description |
|---|---|
|
The opportunity address. |
|
The opportunity sales channel. |
|
The opportunity email_address. |
|
The opportunity name. |
|
The opportunity number. |
|
The opportunity phone_number. |
Example
{
"number": "person-friend-Congress-arm-opportunity",
"name": "their-same-choice-fish-baby",
"emailAddress": "then-spend-travel-while-late",
"phoneNumber": "black-record-body-so-card",
"channel": "for-instead-operation-able-central",
"address": "white-deal-me-nothing-human"
}Fields
| Name | Description |
|---|---|
|
Team assigned to this opportunity. |
|
User assigned to this opportunity. |
|
Attachments for the opportunity. |
|
List of consents for the opportunity. |
|
Lead legal contact email. |
|
Extra details about the opportunity as key/value pairs. |
|
Extra details about the opportunity. Deprecated The 'extraDetails' field is deprecated. |
|
The sales funnel this opportunity is in. |
|
Lead number. |
|
Lead type. |
|
Lead legal name. |
|
Notes for the opportunity. |
|
Opportunity number. |
|
Offer group ID. |
|
Opportunity address. |
|
Opportunity ID. Deprecated The 'opportunityId' field is deprecated. |
|
Opportunity rich address. |
|
Lead legal contact phone number. |
|
The product offering of the opportunity. |
|
Product offering ID. |
|
Sales channel. |
|
Current stage in a funnel. |
Example
{
"opportunityId": "23116629",
"leadNumber": "particularly-eight-glass-offer-whom",
"leadType": "upon-respond-loss-include-tonight",
"name": "whole-news-crime-yet-door",
"email": "than-husband-concern-never-seat",
"phoneNumber": "point-certainly-near-test-sometimes",
"number": "difference-every-begin-need-whom",
"funnel": SalesFunnel,
"stage": "region-eat-side-court-who",
"extraDetails": {"key": "value"},
"extraDetailItems": [ExtraDetail],
"opportunityAddress": AddressOutput,
"opportunityRichAddress": RichAddressType,
"salesChannel": "administration-charge-place-court-son",
"assignedToTeam": "board-these-political-example-outside",
"assignedToUser": "level-movie-on-painting-serve",
"productOfferingId": "55910082",
"productOffering": OfferingType,
"offerGroupId": "51575920",
"consents": [ConsentOutput],
"notes": "set-black-camera-return-relationship",
"attachments": [OpportunityAttachment]
}Fields
| Name | Description |
|---|---|
|
The market for the Product. |
|
The characteristics of the product. |
|
The code of the Product. |
|
The UUID for the Product. |
|
The UUID for the Product Offering. |
Example
{
"productOfferingIdentifier": "98754408",
"productIdentifier": "49319163",
"productCode": "method-different-price-computer-paper",
"productCharacteristics": {"key": "value"},
"market": "three-improve-loss-send-top"
}OrderDetailsType
Represents the details of an Order.
Fields
| Name | Description |
|---|---|
|
The order details. The possible errors that can be raised are:
|
|
The resources associated with the order. The possible errors that can be raised are:
|
|
The current status of the order. The possible errors that can be raised are:
|
Example
{
"order": OrderType,
"status": "PENDING",
"resources": [OrderResource]
}OrderItemType
Represents an item being ordered.
Fields
| Name | Description |
|---|---|
|
The code identifying the item. |
|
Market-specific data for the item. |
|
The profile containing characteristics of the item. |
Example
{
"profile": ItemProfileType,
"marketData": {"key": "value"},
"code": "in-two-personal-expect-small"
}OrderLineDateRangeType
Represents a period defined by specific start and end dates.
Fields
| Name | Description |
|---|---|
|
The end date and time of the period. Null indicates an infinite/rolling period. |
|
The start date and time of the period. |
Example
{
"start": "1982-03-01T08:01:55.465952+00:00",
"end": "1972-12-08T21:39:13.332254+00:00"
}OrderLineDurationType
Represents a period defined by duration in seconds.
Fields
| Name | Description |
|---|---|
|
The duration in seconds. |
Example
{
"duration": 599.4
}OrderLineType
Represents a line item in an order.
Fields
| Name | Description |
|---|---|
|
The item being ordered. |
|
The period for which this order line is valid. Can be a range or a duration. |
|
The target customer for this order line. |
|
The terms applicable to this order line. |
Example
{
"item": OrderItemType,
"period": OrderLinePeriodType,
"target": AccountType,
"terms": TermInterface
}OrderResource
Represents a resource associated with an order.
Fields
| Name | Description |
|---|---|
|
The unique identifier of the resource. |
|
The type of the resource. |
Example
{
"resourceType": "performance-never-force-major-may",
"resourceIdentifier": "58973460"
}OrderType
Represents an order in the system.
Fields
| Name | Description |
|---|---|
|
The customer who placed the order. |
|
Unique identifier for the order. |
|
The order lines in this order. |
|
The date and time when the order was placed. |
|
The sales record associated with this order, if any. |
|
The source offering that generated this order. |
|
The terms applicable to this order. |
Example
{
"identifier": "72245834",
"customer": OrderCustomerType,
"lines": [OrderLineType],
"orderedAt": "2021-10-18T19:29:14.848474+00:00",
"terms": TermInterface,
"sale": SalesRecordType,
"source": "school-ok-require-company-career"
}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": "25274383",
"account": AccountType,
"metadata": CallMetadataItemType
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
Example
{
"type": "SALE",
"category": "SUCCESS",
"reason": "join-follow-vote-little-cold"
}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": "environment-house-impact-local-real",
"endCursor": "government-real-major-film-those"
}PauseCollectionProcess
Manually pause a collection process.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-11214: Invalid pause length for collection process.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Collection process pause output. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessPaused": PauseCollectionProcessOutput
}Fields
| Name | Description |
|---|---|
|
Pause records on the collection process. |
Example
{
"pauseRecords": [CollectionProcessPauseStatusRecord]
}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. |
|
Unique identifier for the transaction. |
|
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. |
|
Date when the transaction was posted to the account. |
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Human-readable title describing the transaction. |
Example
{
"id": "32398375",
"postedDate": "1996-06-03",
"createdAt": "2023-09-05T14:32:52.391462+00:00",
"accountNumber": "A-1DD6F320",
"amount": 11,
"amounts": TransactionAmountType,
"balanceCarriedForward": 13,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "here-first-be-although-while",
"billingDocumentIdentifier": "83926970",
"statementId": "20900017",
"isReversed": true,
"hasStatement": true,
"note": "in-bill-fine-seem-better",
"reasonCode": "join-future-way-surface-quality",
"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 |
|---|---|
|
Fingerprint. |
|
Returns True if the fingerprint exists, Fasle otherwise. |
|
Returns True if the fingerprint is risk-listed, Fasle otherwise. |
Example
{
"fingerprint": "notice-skin-concern-group-through",
"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": 59,
"edgeCount": 10
}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": "company-dinner-course-ability-star"
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
The payment method used for the forecasted payment. |
|
Example
{
"paymentNumber": 66,
"date": "2006-07-14",
"amount": 29,
"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": 43,
"edgeCount": 45
}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": "local-argue-wait-Congress-somebody"
}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
Direct Debit Instructions
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Payment instruction type. |
|
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": "21031697",
"status": "report-science-improve-hotel-accept",
"sortCode": "wall-miss-TV-church-world",
"iban": "law-find-away-family-determine",
"accountHolder": "top-action-body-something-scene",
"instructionType": "may-whether-learn-take-woman",
"cardPaymentNetwork": "resource-skill-economy-military-short",
"cardExpiryMonth": 12,
"cardExpiryYear": 35,
"supplementaryLedger": SupplementaryLedgerType,
"bankCode": "beat-morning-second-as-play",
"accountType": "task-poor-main-and-appear",
"validFrom": "2017-09-23T11:25:03.782069+00:00",
"vendor": "range-treat-purpose-score-side",
"cardNumber": "you-seven-city-threat-wait",
"cardType": "say-think-key-and-manage",
"maskedAccountIdentifier": "94135993",
"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": 17,
"edgeCount": 32
}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": "worry-young-center-young-hot"
}PaymentPlanPaymentType
An object that represents a planned payment for a payment plan.
Example
{
"payableDate": "1971-09-03",
"amount": 31,
"paymentType": "view-community-along-news-thank"
}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": "23566771",
"account": AccountType,
"initialScheduleType": "simply-generation-card-memory-grow",
"strategyName": "Democrat-significant-coach-Mr-knowledge",
"status": "employee-about-should-see-state",
"offeredAt": "1985-04-26T12:57:11.184282+00:00",
"offerExpiresAt": "2025-07-16T14:27:58.582202+00:00",
"acceptedAt": "2003-06-15T08:37:39.103257+00:00",
"updatedAt": "2021-03-18T23:48:46.222272+00:00",
"payments": PaymentPlanPaymentType,
"nextPayment": PaymentPlanPaymentType,
"strategyDisplayName": "bar-defense-girl-the-hear",
"ledgerNumber": "market-language-career-finish-hospital"
}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": 13,
"edgeCount": 94
}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": "within-respond-increase-entire-wear"
}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": 41,
"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": "give-age-civil-not-camera"
}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": "2022-10-07",
"paymentStatus": "much-new-interest-training-fight",
"totalAmount": 23,
"customerAmount": 97,
"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": 34,
"edgeCount": 8
}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": "first-health-president-race-for"
}Fields
| Name | Description |
|---|---|
|
The create schedules payment amount. |
|
The created schedules payment day. |
Example
{
"paymentDay": 38,
"paymentAmount": 80
}Fields
| Name | Description |
|---|---|
|
The arguments of the delay configuration. |
|
The code of the delay configuration. |
Example
{
"code": "these-race-born-staff-wish",
"args": {"key": "value"}
}Fields
| Name | Description |
|---|---|
|
A human-readable description of the value. |
|
Direction of payment day. |
Example
{
"direction": "OF_MONTH",
"description": "listen-win-against-fund-big"
}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. |
|
|
|
If the payment schedule is exempt from payment adequacy. |
|
|
|
|
|
The ledger number of the 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. |
|
The cause for requesting payment on a schedule. |
|
|
|
Example
{
"id": "85875137",
"supplementaryLedger": SupplementaryLedgerType,
"validFrom": "2018-04-28",
"validTo": "1988-12-04",
"reason": "GENERAL_ACCOUNT_PAYMENT",
"paymentHolidayReason": "cold-cold-many-let-tree",
"paymentDay": 80,
"paymentFrequency": "Weekly",
"paymentFrequencyMultiplier": 5,
"paymentAmount": 45,
"paymentAdequacyAdjustment": 45,
"paymentAdequacyAdjustmentExpiryDate": "2011-07-14",
"isVariablePaymentAmount": true,
"totalDebtAmount": 44,
"isPaymentHoliday": true,
"scheduleType": "BACS_TRANSFER",
"paymentDayDetails": PaymentSchedulePaymentDayDetailsType,
"delayConfiguration": PaymentScheduleDelayConfigurationType,
"isExemptFromPaymentAdequacy": true,
"ledgerNumber": "always-bill-specific-imagine-specific"
}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": PaymentWithNonConcludedRePresentationConnectionTypeEdge,
"totalCount": 92,
"edgeCount": 81
}PaymentWithNonConcludedRePresentationConnectionTypeEdge
A Relay edge containing a PaymentWithNonConcludedRePresentationConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": PaymentWithNonConcludedRePresentationType,
"cursor": "decide-cut-and-area-walk"
}Fields
| Name | Description |
|---|---|
|
The amount expected for this payment in minor currency units. |
|
The date this payment is scheduled to be debited. |
Example
{
"amountPayable": 77,
"payableDate": "1983-03-29"
}PayoutReferralForAccount
The possible errors that can be raised are:
- KT-CT-6712: Invalid reference.
- KT-CT-6723: Unauthorized.
- KT-CT-6730: Referral cannot be paid out.
- KT-CT-6731: The account is unrelated to the referral.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The result of the payout. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"payoutResult": PayoutReferralForAccountResultType
}PayoutReferralForAccountResultType
The result of the payout of a referral for an account.
Fields
| Name | Description |
|---|---|
|
The amount of the account credit paid out to the referring account. |
Example
{
"accountCreditAmount": 92
}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. |
|
Whether the account is paying by direct debit or not. |
|
The type of the term. |
Example
{
"type": "music-history-middle-set-between",
"displayName": "discuss-family-partner-surface-institution",
"description": "question-animal-rock-top-forward",
"identifier": "27228881",
"isVariable": true,
"paysByDirectDebit": 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
}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.
- 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],
"krakenflexDevice": KrakenFlexDeviceType
}Example
{
"start": "1989-01-08T03:34:03.662621+00:00",
"end": "2002-12-03T02:39:11.922831+00:00"
}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. |
|
List of dates when a printed copy of this bill was requested. |
|
|
|
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": "59945724",
"billType": "STATEMENT",
"fromDate": "1988-03-03",
"toDate": "1996-07-21",
"temporaryUrl": "simply-point-education-look-thus",
"issuedDate": "1980-03-31",
"attachments": BillingAttachmentConnectionTypeConnection,
"identifier": "38026874",
"totalCharges": StatementTotalType,
"totalCredits": StatementTotalType,
"isAnnulled": true,
"transactions": BillTransactionConnectionTypeConnection,
"closingBalance": 89,
"documentDebtPosition": BillingDocumentPositionType,
"representations": BillRepresentationConnectionTypeConnection,
"printedCopyRequests": ["1979-06-19"]
}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": "charge-physical-main-to-stop",
"buttonAction": ActionType,
"id": "76362740",
"typename": "exactly-conference-whether-owner-almost"
}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": 24,
"remainingPoints": 48,
"usedPoints": 29,
"ttl": 72,
"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": "38494952",
"typename": "ahead-must-mother-option-direction",
"points": 75
}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": 69,
"edgeCount": 6
}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": "world-before-late-drop-work"
}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": "12635001",
"number": "capital-soon-country-establish-wait",
"createdAt": "1995-08-05T10:43:14.298583+00:00",
"updatedAt": "2023-06-16T18:10:17.062935+00:00",
"billingName": "president-health-marriage-for-sell",
"collectiveBilling": true,
"operationsTeam": OperationsTeamType,
"leadAccountNumber": "A-1E77708F",
"brand": "a-control-always-process-blue",
"name": "chance-for-expect-none-city",
"depth": 98,
"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": "66651021",
"user": AccountUserType,
"role": ADMIN,
"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": "approach-PM-capital-grow-wait",
"code": "hospital-wrong-yeah-official-society",
"type": "house-little-dinner-hotel-drug",
"description": "poor-out-peace-industry-travel"
}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": "course-next-fill-none-quite",
"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
}Fields
| Name | Description |
|---|---|
|
Area. |
|
City. |
|
Postcode. |
|
Prefecture. |
Example
{
"postcode": "employee-democratic-glass-we-serve",
"prefecture": "see-project-growth-win-way",
"city": "turn-evidence-Mr-quickly-ability",
"area": "already-team-under-decide-real"
}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": "79555460",
"billType": "STATEMENT",
"fromDate": "1999-04-19",
"toDate": "2018-01-08",
"temporaryUrl": "before-almost-international-officer-thought",
"issuedDate": "1995-11-15",
"attachments": BillingAttachmentConnectionTypeConnection,
"identifier": "24106821",
"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": "later-determine-type-first-much",
"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": "side-statement-brother-eye-their",
"status": "prove-dog-trial-across-five",
"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. |
|
The user number of the newly created or existing account user. |
Example
{
"isNewAccount": true,
"accountNumber": "A-1DD39C9D",
"isNewUser": true,
"userId": "97450355",
"userNumber": "fear-very-consumer-too-sit"
}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": "70724443",
"filename": "conference-including-surface-suddenly-time",
"s3Bucket": "attorney-analysis-pay-call-marriage",
"s3Key": "budget-field-involve-eye-report",
"temporaryUrl": "throughout-write-require-central-west"
}PrintBatchType
Represents print batch details
Fields
| Name | Description |
|---|---|
|
|
|
Messages in a print batch. |
|
The status of the print batch. |
Example
{
"id": "97512578",
"status": "OPEN",
"messages": PrintMessageTypeConnection
}Fields
| Name | Description |
|---|---|
|
|
|
The ID of the object |
|
Print message of the print event. |
|
Example
{
"id": "56632380",
"eventType": "however-few-few-college-shoulder",
"occurredAt": "1991-05-14T02:16:21.099639+00:00",
"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": "20597374",
"templateCode": "write-old-memory-contain-I",
"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": 77,
"edgeCount": 72
}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": "language-law-man-fill-lot"
}ProcessOrderOutput
Output type for the result of processing an order.
Fields
| Name | Description |
|---|---|
|
The unique identifier of the processed order. |
|
The resources associated with the processed order. |
|
The status of the order processing. |
Example
{
"status": "PENDING",
"identifier": "26034447",
"resources": [OrderResource]
}ProductComponentType
Represents a product component within an offering.
Fields
| Name | Description |
|---|---|
|
The product associated with this component. |
|
Unique identifier of the component. |
|
Initial/default quantity for this component. |
|
Maximum quantity of this component that can be selected. |
|
Minimum quantity of this component that can be selected. |
Example
{
"identifier": "47206928",
"minimumQuantity": 40,
"maximumQuantity": 3,
"initialQuantity": 44,
"component": CatalogProductType
}ProductEligibleStatus
Flags for the user to switch to the product with FCA rate.
Fields
| Name | Description |
|---|---|
|
Check if the product reaches to the maximum number of active agreements. |
|
Check if the user is from allowed areas and has the campaign registered to account. |
|
Check if the user has switched to the product with FCA rate. |
Example
{
"isUserEligible": true,
"isCampaignAvailable": true,
"isUserOptedIn": true
}Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per unit. |
|
Region of operation. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "fly-race-can-finally-onto",
"regionOfOperation": "seven-any-enjoy-clearly-early",
"band": "reality-fast-decide-that-place",
"validFrom": "1980-03-13T22:07:40.541625+00:00",
"validTo": "2003-09-08T12:54:03.644089+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 96
}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": "good-southern-for-marriage-task",
"displayName": "data-forget-heavy-claim-majority",
"description": "including-foot-set-focus-character",
"identifier": "71132127",
"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": "individual-natural-number-wrong-generation",
"rateBand": "recent-resource-speak-special-agree",
"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": "1994-02-13T13:52:04.435682+00:00"
}Fields
| Name | Description |
|---|---|
|
Check if the product reaches to the maximum number of active agreements. |
|
Check if the user is from allowed areas and has the campaign registered to account. |
|
Check if the user has switched to the product with FCA rate. |
Example
{
"isUserEligible": true,
"isCampaignAvailable": true,
"isUserOptedIn": true
}PromotionAssignmentPeriodType
Represents a period with a start and optional end date for promotion assignment.
Fields
| Name | Description |
|---|---|
|
The end date and time of the assignment period. |
|
The start date and time of the assignment period. |
Example
{
"start": "2010-06-05T13:30:59.488471+00:00",
"end": "1983-03-31T22:03:16.044771+00:00"
}PromotionAssignmentScheduleType
Represents a schedule for promotion assignment within a contract.
Fields
| Name | Description |
|---|---|
|
The period during which this promotion assignment is active. |
|
A mapping from discount codes to lists of targets. Each target is represented as {'target_type': {'domain': ..., 'type': ...}, 'identifier': ...}. |
|
The promotion code for this schedule. |
Example
{
"promotionCode": "run-play-care-treatment-tough",
"assignmentPeriod": PromotionAssignmentPeriodType,
"discountTargets": {"key": "value"}
}PromotionAssignmentTermType
Represents a promotion assignment term in 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. |
|
A list of promotion assignment schedules associated with the contract. |
|
The type of the term. |
Example
{
"type": "prepare-challenge-simple-almost-chair",
"displayName": "serious-use-during-law-sometimes",
"description": "realize-help-candidate-challenge-without",
"identifier": "46050584",
"isVariable": true,
"schedules": [PromotionAssignmentScheduleType]
}Fields
| Name | Description |
|---|---|
|
The address of the property, formatted into a single string. |
|
Coordinates for the property, useful for displaying the property on a map. |
|
All the electricity generation points at this property. |
|
All the electricity supply points at this property. |
|
The embedded network this property belongs to, if any. |
|
All the gas supply points at this property. |
|
|
|
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. |
|
The postcode of the property. |
|
Property rich address. |
|
List of address lines. |
Example
{
"id": "60412400",
"address": "better-nearly-move-let-particular",
"richAddress": PropertyRichAddressType,
"splitAddress": ["employee-just-six-wife-little"],
"label": "large-we-pressure-its-several",
"occupancyPeriods": [OccupancyPeriodType],
"coordinates": CoordinatesType,
"embeddedNetwork": EmbeddedNetworkType,
"measurements": MeasurementConnection,
"postcode": "section-herself-ready-success-last",
"electricitySupplyPoints": [ElectricitySupplyPoint],
"electricityGenerationPoints": [ElectricityGenerationPoint],
"gasSupplyPoints": [GasSupplyPoint]
}Fields
| Name | Description |
|---|---|
|
Top-level administrative subdivision, e.g. US state, AU state/territory, NZ, region, IT region, JP prefecture.
|
|
The entire formatted address represented as a single string, as it would be written on an envelope. The formatting of this field may vary according to the country of the address (which may not match this Kraken installation's home country). It may also change if we update our address-formatting code or if our understanding of the correct formatting for a given country changes. Avoid parsing individual components of an address out of this field's value; use the other fields on this type instead. |
|
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": "teach-forget-necessary-other-different",
"organization": "race-add-door-hand-apply",
"streetAddress": "act-people-buy-writer-provide",
"structuredStreetAddress": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"dependentLocality": "last-moment-figure-life-choose",
"locality": "suggest-with-arrive-house-within",
"administrativeArea": "herself-picture-green-to-mention",
"postalCode": "story-of-institution-education-wish",
"sortingCode": "allow-information-apply-hear-agree",
"country": "mind-quite-anyone-Democrat-gun",
"deliveryPointIdentifier": "21487265",
"asString": "interest-who-able-rock-laugh"
}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. |
|
Coordinates for the property, useful for displaying the property on a map. |
|
The embedded network this property belongs to, if any. |
|
|
|
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. |
|
List of address lines. |
Example
{
"id": "53166524",
"address": "forward-worker-modern-pass-arrive",
"richAddress": PropertyRichAddressType,
"splitAddress": ["necessary-early-shake-federal-control"],
"label": "every-moment-same-glass-degree",
"occupancyPeriods": [OccupancyPeriodType],
"coordinates": CoordinatesType,
"embeddedNetwork": EmbeddedNetworkType,
"measurements": MeasurementConnection,
"postcode": "air-though-food-plant-particular",
"electricityMalos": [MaLo],
"gasMalos": [MaLo]
}Fields
| Name | Description |
|---|---|
|
OAuth 2.0 URI for the provider. |
Example
{
"oauthUri": "despite-himself-range-society-bag"
}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": "hold-investment-describe-write-so",
"virtualKeyUri": "cost-couple-newspaper-month-alone"
}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": 48,
"edgeCount": 61
}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": "involve-worker-foreign-college-some"
}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": "87964432",
"title": "practice-generation-yard-cause-wish",
"amount": 95,
"date": "1975-03-18"
}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. |
Example
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-9908: Invalid recipient information.
- KT-CT-9909: Invalid recipient information.
- KT-CT-9910: Invalid input field combination.
- 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
}Fields
| Name | Description |
|---|---|
|
The voucher purchase created from the mutation. |
Example
{
"voucherPurchase": VoucherPurchaseType
}PushNotificationBindingType
Represents a pairing of a single app installation to an account user.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example
{
"id": "16013824",
"messages": PrintMessageTypeConnection,
"user": AccountUserType,
"token": "game-short-oil-popular-close",
"application": NotifiableApplicationType,
"registeredAt": "1973-05-26T17:44:54.288871+00:00",
"expiresAt": "2005-09-11T20:22:19.178030+00:00"
}QuantityType
Graphene type object to represent Quantity(magnitude, unit)
Fields
| Name | Description |
|---|---|
|
The numeric value of this field. |
|
Unit of this field. |
Example
{
"magnitude": 518.72,
"unit": "less-phone-part-hot-region"
}Fields
| Name | Description |
|---|---|
|
The complexity of the query. |
Example
{
"complexityValue": 71
}Quote
DEPRECATED - A set of products return to a prospective customer for quote supply points.
Fields
| Name | Description |
|---|---|
|
The quote code that identifies the quote. |
|
Quote-related params that are permitted to be fetched with the quote-code alone. |
|
Quoted generation points. |
|
Quoted supply points. |
Example
{
"params": QuoteRequestParams,
"code": "outside-go-heart-surface-near",
"quotedSupplyPoints": QuotedSupplyPoint,
"quotedGenerationPoints": [QuotedSupplyPoint]
}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. |
|
S3 URLs for terms and conditions linked to this quote component. |
Example
{
"identifier": "80082191",
"productComponentIdentifier": "69881691",
"costs": [QuoteCostType],
"quotingParamsInputData": [QuotingParamType],
"createdAt": "1984-06-18T15:17:40.907240+00:00",
"termsAndConditionsS3Urls": [TermsAndConditionsS3UrlType]
}Fields
| Name | Description |
|---|---|
|
Name of the cost field. |
|
Value of the cost field. |
Example
{
"key": "fund-drug-yourself-bed-offer",
"value": QuoteCostUnionType
}QuoteRequestParams
Quote-related params that are permitted to be fetched with the quote-code alone.
Fields
| Name | Description |
|---|---|
|
The subdomain of the affiliate link. |
|
An optional audio recording id. |
|
The friend referral code. |
|
The bespoke referral scheme code. |
Example
{
"affiliateLinkSubdomain": "produce-by-stage-yourself-card",
"referralSchemeCode": "simple-benefit-education-charge-agency",
"referralCode": "through-score-site-law-western",
"audioRecordingId": "67564831"
}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": "50392639",
"createdAt": "1978-11-07T04:19:53.187587+00:00",
"productOfferingIdentifier": "88189782",
"quoteComponents": [QuoteComponentType],
"createdBy": ActorType
}QuotedElectricityGenerationPoint
DEPRECATED - A single quoted generation point for a customers quote request.
Fields
| Name | Description |
|---|---|
|
Annual estimated electricity generation. |
|
Whether we can connect the generation point or not, according to our business logic. |
|
Grid operator code. |
|
Whether the property of the generation point has multiple generation points. |
|
ID of the quoted generation point. |
|
Postal area for the quote. |
|
Quoted products. |
|
If we cannot connect a generation point, this list of rejection reasons will show what errors fired. |
Example
{
"id": 35712514,
"quotedProducts": QuotedElectricityProduct,
"postalArea": PostalArea,
"gridOperatorCode": "drop-include-probably-though-such",
"annualEstimatedGeneration": ["yet-month-I-doctor-national"],
"canSupply": true,
"hasMultipleSpins": true,
"rejectionReasons": "INVALID_GRID_OPERATOR"
}QuotedElectricityProduct
DEPRECATED - Customer's quoted product, for the quoted supply point.
Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
The id of the quoted product. |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"id": 45493337,
"product": Product,
"estimatedCosts": QuotedProductEstimatedCosts
}QuotedElectricitySupplyPoint
DEPRECATED - A single quoted supply point for a customers quote request.
Fields
| Name | Description |
|---|---|
|
|
|
|
|
Whether we can supply the supply point or not, according to our business logic. |
|
|
|
Whether the property of the supply point has multiple supply points. |
|
ID of the quoted supply point. |
|
|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
|
|
|
If we cannot supply a supply point, this list of rejection reasons will show what errors fired. |
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"id": 46778960,
"quotedProducts": QuotedElectricityProduct,
"postalArea": PostalArea,
"amperage": 82,
"kva": 13,
"kw": 24,
"gridOperatorCode": "defense-risk-your-child-ball",
"annualEstimatedUsage": "push-increase-everyone-fast-social",
"supplyPointDetails": SupplyPointDetailsRaw,
"canSupply": true,
"hasMultipleSpins": true,
"rejectionReasons": "INVALID_GRID_OPERATOR"
}Fields
| Name | Description |
|---|---|
|
Quoting components of this quote. |
|
Product offering identifier. |
|
Product component data including its quoting parameters. |
Example
{
"offeringIdentifier": "47008732",
"productComponents": [QuotedProductComponentType],
"offeringComponents": [QuotedOfferingParamsType]
}Fields
| Name | Description |
|---|---|
|
Product code. |
|
Quoting parameter definitions for this product. |
Example
{
"productCode": "69696339",
"quotingParams": [QuotingParamType]
}Fields
| Name | Description |
|---|---|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
|
|
|
Example
{
"quotedMonth": QuotedProductEstimatedCostsQuotedMonth,
"monthlyBreakdown": 75,
"standingChargePricePerDay": "1.0",
"standingChargeUnitType": "conference-positive-nice-bring-describe"
}Example
{
"cost": "although-trouble-who-TV-but",
"month": "country-section-a-ahead-hair",
"usageAmount": "rise-human-watch-benefit-statement"
}Fields
| Name | Description |
|---|---|
|
Choices of the quoting parameter if present. |
|
Name of the quoting parameter. |
|
Source of the quoting parameter. |
|
Type of the quoting parameter. |
|
Value of the quoting parameter. |
Example
{
"name": "speech-both-special-fact-the",
"type": "research-window-over-Mrs-exist",
"choices": ["open-find-floor-heart-yeah"],
"source": "forget-add-form-me-up",
"value": "fine-east-foot-whose-car"
}RateBuilderNodeType
Contains available units and categories for rate configuration.
Fields
| Name | Description |
|---|---|
|
Available category options. |
|
Available unit options. |
Example
{
"units": [LabelValueType],
"categories": [LabelValueType]
}RateGroupEligibilityConfigurationType
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. |
|
A list of rate group eligibility schedules associated with the contract. |
|
A list of time series specification eligibility schedules associated with the contract. |
|
The type of the term. |
Example
{
"type": "always-majority-drug-strong-back",
"displayName": "challenge-play-officer-can-ready",
"description": "prepare-central-role-deal-type",
"identifier": "25399295",
"isVariable": true,
"schedules": [RateGroupEligibilityScheduleType],
"timeSeriesSpecificationSchedules": [TimeSeriesSpecificationEligibilityScheduleType]
}RateGroupEligibilityPeriodType
Represents a period with a start and optional end date.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The end date and time of the period. |
|
The start date and time of the period. |
Example
{
"start": "2010-11-21T01:16:21.060434+00:00",
"end": "2018-07-24T05:14:36.523714+00:00"
}RateGroupEligibilityScheduleType
Represents a schedule for rate group eligibility within a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The period during which this eligibility is effective. |
|
Indicates if the rate group is eligible. |
|
The product code associated with the rate group. |
|
The rate group code. |
Example
{
"productCode": "no-then-east-mission-computer",
"rateGroupCode": "investment-find-protect-example-little",
"isEligible": true,
"effectivePeriod": RateGroupEligibilityPeriodType
}RateGroupPrices
Rate group prices for a product.
Fields
| Name | Description |
|---|---|
|
The prices for the rate group. |
|
The rate group code. |
Example
{
"rateGroup": "picture-then-tree-need-sit",
"prices": PriceForStream
}ReactivateCollectionProcessRecord
Reactivate a Collection Process Record that was previously activated.
Unlike UpdateCollectionProcessRecordToActive, this mutation does not require or update the external_reference field. Use this when reactivating a collection process that already has an external_reference set from its initial activation.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-11217: Invalid collection process record status for reactivation.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The reactivated collection process record. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessReactivated": ReactivateCollectionProcessRecordOutputType
}ReactivateCollectionProcessRecordOutputType
Output for reactivating a Collection process Record.
Fields
| Name | Description |
|---|---|
|
The number of the collection process record. |
|
The current status of the collection process record. |
Example
{
"number": "happy-speak-them-smile-side",
"status": "PENDING"
}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": "what-imagine-some-wear-large",
"intervalStart": "2014-09-10T08:07:31.671522+00:00",
"intervalEnd": "2004-03-19T11:28:45.306928+00:00",
"source": "would-cell-color-degree-morning",
"quality": "prove-change-mother-recent-remember"
}Fields
| Name | Description |
|---|---|
|
Readings representing outgoing utility flow e.g., solar generation. |
|
Readings representing incoming utility flow e.g., usage or consumption.. |
Example
{
"exportReadings": ExportReadingsConnection,
"importReadings": ImportReadingsConnection
}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": "summer-trip-against-speech-community",
"buttonAction": ActionType,
"id": "88517866",
"typename": "recent-out-during-less-worker",
"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.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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": 90
}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. |
|
Whether the referral claim code is valid and available for use. |
|
Referral scheme claim code belongs to. |
|
Value of claim code. |
Example
{
"id": 74191483,
"value": "concern-open-social-student-blue",
"referralScheme": ReferralSchemeType,
"accountReferral": ReferralType,
"isValid": true,
"createdAt": "2022-06-18T14:49:28.792804+00:00"
}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": 26,
"edgeCount": 47,
"referringUserTotalPaymentAmount": 42
}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": "simple-out-hospital-gas-loss"
}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": "pay-charge-floor-may-resource",
"referralDisplayUrl": "when-may-these-yeah-human",
"referrerRewardAmount": 60,
"referredRewardAmount": 69,
"combinedRewardAmount": 63,
"loyaltyPointsBonus": 14,
"canBeReferred": true,
"code": "family-body-house-minute-explain",
"referrerGivenName": "Crystal",
"referrerFamilyName": "Harvey",
"schemeType": "conference-drive-nation-century-office",
"maxRecurrence": 68,
"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": "43124928",
"ledgerId": 18794023,
"ledgerNumber": "catch-item-stuff-area-strong",
"paymentDate": "1977-08-04",
"schemeType": "REFERRAL_REWARD",
"code": "computer-minute-power-reach-song",
"referredUserName": "those-hospital-hour-offer-must",
"paymentStatus": "question-help-response-friend-certainly",
"referredUserJoinDate": "2009-06-05T00:04:10.289693+00:00",
"referredUserPaymentAmount": 92,
"referringUserPaymentAmount": 64,
"combinedPaymentAmount": 41
}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": "page-indeed-question-prepare-rest",
"expiryDt": "1970-08-03T11:16:46.796819+00:00",
"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. |
|
Unique identifier for the transaction. |
|
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. |
|
Date when the transaction was posted to the account. |
|
Returns the reason. |
|
Returns None if a statement is not linked with the transaction. Deprecated The 'statementId' field is deprecated. |
|
Human-readable title describing the transaction. |
Example
{
"id": "24115544",
"postedDate": "1981-01-22",
"createdAt": "1992-10-21T10:03:01.603615+00:00",
"accountNumber": "A-C505202E",
"amount": 78,
"amounts": TransactionAmountType,
"balanceCarriedForward": 2,
"isCredit": true,
"isAccountCharge": true,
"isAccountPayment": true,
"isHeld": true,
"isIssued": true,
"title": "daughter-article-create-many-box",
"billingDocumentIdentifier": "23211045",
"statementId": "36939596",
"isReversed": true,
"hasStatement": true,
"note": "red-good-street-wish-green",
"reasonCode": "leader-position-head-pass-child"
}Fields
| Name | Description |
|---|---|
|
Refunds Payment reference. |
Example
{
"reference": "decade-coach-least-let-social"
}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-3938: Partial refund not allowed.
- 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": "11307386",
"amount": 99,
"payment": AccountPaymentType,
"reasonCode": "hear-western-option-evening-bring",
"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": 17,
"edgeCount": 89
}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": "new-tax-than-letter-now"
}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": "miss-condition-hair-wall-store",
"viewer": AccountUserType
}Fields
| Name | Description |
|---|---|
|
Campaign name. |
|
Date and time at which the participant was registered. |
Example
{
"campaignName": "respond-forget-writer-game-white",
"registeredAt": "2010-12-29T04:02:20.437876+00:00"
}RegisterLeadFlowStatusEvent
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. |
Example
{
"possibleErrors": [PossibleErrorType]
}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
}RegistersConnection
Pagination for device registers.
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": RegistersEdge,
"totalCount": 26,
"edgeCount": 66
}RegistersEdge
A Relay edge containing a Registers and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": DeviceRegister,
"cursor": "enough-road-because-level-thank"
}Fields
| Name | Description |
|---|---|
|
The id of the user responsible for completing the reminder. |
|
The id of the team responsible for completing the reminder. |
|
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": 71605047,
"reminderTypeName": "environment-write-able-join-yard",
"isKrakenManaged": true,
"content": "among-every-box-scientist-live",
"dueAt": "2016-09-28T03:00:26.848002+00:00",
"assigneeUsername": "everything-pretty-network-special-store",
"assigneeId": "80103418",
"assigneeTeamName": "light-police-affect-sure-including",
"assigneeTeamId": "78347265",
"reopenInkConversation": true,
"createdAt": "2016-02-08T14:29:36.793414+00:00"
}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]
}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]
}RenewableEnergyLevyRate
Renewable energy levy product rate.
Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per unit. |
|
Price per unit including tax. |
|
Region of operation. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "choose-learn-from-TV-eight",
"regionOfOperation": "find-relate-season-general-sing",
"band": "others-church-enjoy-say-baby",
"validFrom": "2017-11-12T22:43:39.108083+00:00",
"validTo": "2024-09-21T13:26:58.048135+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 30,
"pricePerUnitIncTax": "1.0"
}Fields
| Name | Description |
|---|---|
|
The repayment intervention outcome. |
|
The repayment intervention reason. |
Example
{
"outcome": "which-upon-instead-animal-about",
"reason": "how-agree-commercial-strategy-range"
}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": 91,
"edgeCount": 67
}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": "learn-contain-plant-my-no"
}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": "87844940",
"amount": 2,
"reasonCode": "lose-network-music-but-scene",
"method": "BANK_TRANSFER",
"instruction": PaymentInstructionType,
"status": "REQUESTED"
}RequestAmperageChange
Create an amperage change process.
This mutation is used for amperage change requests by organizations.
The possible errors that can be raised are:
- KT-JP-4511: Invalid data.
- KT-CT-4501: Unauthorized.
- KT-JP-4501: Unauthorized.
- KT-JP-4502: Unauthorized.
- KT-JP-4512: Unable to process amperage change request.
- KT-JP-4513: Unable to process amperage change request.
- KT-JP-4520: Unable to process request.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Success message. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": "hotel-where-company-parent-wife"
}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. |
|
The number of the user that requested a password reset email. |
Example
{
"email": "much-offer-thousand-put-information",
"userNumber": "often-history-month-partner-technology"
}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
}Fields
| Name | Description |
|---|---|
|
Whether the account can request a refund. |
|
The reason why a refund cannot be requested. |
Example
{
"canRequestRefund": true,
"reason": "glass-skill-special-key-bill"
}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": "78143174",
"status": "REQUESTED"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"errors": [SerializerFieldErrorsType],
"clientMutationId": "71048116"
}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": "94234239",
"passwordUpdated": true,
"failureReasons": ["water-out-decide-individual-way"],
"failureCodes": ["shake-better-speech-main-condition"]
}ResumeCollectionProcess
Manually resume a collection process.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11201: No Collection Process Records associated with id.
- KT-CT-11215: Unable to resume, collection process is not paused.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Collection process resume output. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessResumed": ResumeCollectionProcessOutput
}Fields
| Name | Description |
|---|---|
|
Pause records on the collection process. |
Example
{
"pauseRecords": [CollectionProcessPauseStatusRecord]
}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
}Fields
| Name | Description |
|---|---|
|
|
|
|
|
|
|
|
|
Override Field to add additional attributes and extend description with possible_errors |
Example
{
"code": "boy-beat-have-religious-yes",
"name": "final-perform-drop-be-husband",
"displayName": "wait-happen-entire-chance-firm",
"displayOrder": 58,
"params": RetailerParams
}Fields
| Name | Description |
|---|---|
|
A list of aliases to use with autocomplete suggestions. |
Example
{
"aliases": "station-drive-in-real-specific"
}RevertProductSwitch
Revert a product switch by revoking an unbilled agreement and restoring the previous one.
Fields
| Name | Description |
|---|---|
|
The restored agreement. |
Example
{
"agreement": Agreement
}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
}RevokeUserAccessFromBusiness
The possible errors that can be raised are:
- KT-CT-5463: Unauthorized.
- KT-CT-11107: Unauthorized.
- KT-CT-13501: 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]
}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": "43764973",
"ledgerId": 81415189,
"ledgerNumber": "leave-however-marriage-from-establish",
"paymentDate": "1985-12-04",
"schemeType": "REFERRAL_REWARD",
"code": "play-similar-under-else-pay",
"rewardAmount": 55,
"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.
If you only need the address in a single string, use the
asString property. If you need the address as a list of
lines, use the asString property, then use
.splitlines() (or your programming language's
equivalent) on the resulting value.
Fields
| Name | Description |
|---|---|
|
Top-level administrative subdivision, e.g. US state, AU state/territory, NZ, region, IT region, JP prefecture.
|
|
The entire formatted address represented as a single string, as it would be written on an envelope. The formatting of this field may vary according to the country of the address (which may not match this Kraken installation's home country). It may also change if we update our address-formatting code or if our understanding of the correct formatting for a given country changes. Avoid parsing individual components of an address out of this field's value; use the other fields on this type instead. |
|
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": "water-seat-become-speak-compare",
"organization": "science-image-car-maybe-three",
"streetAddress": "tree-car-agent-box-right",
"structuredStreetAddress": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"dependentLocality": "line-stock-onto-visit-lawyer",
"locality": "matter-upon-offer-recognize-bring",
"administrativeArea": "quickly-effort-develop-new-recognize",
"postalCode": "star-citizen-around-central-camera",
"sortingCode": "institution-total-become-theory-line",
"country": "art-measure-themselves-international-treatment",
"deliveryPointIdentifier": "58034268",
"asString": "certain-recent-serve-talk-experience"
}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": "56184859"
}RunAgreementRollover
The possible errors that can be raised are:
- KT-CT-13705: Agreement rollover not found.
- KT-CT-13706: Agreement rollover has an invalid status for this operation.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The executed agreement rollover. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"agreementRollover": AgreementRolloverType
}Fields
| Name | Description |
|---|---|
|
|
|
The ID of the object |
|
SMS message of the SMS event. |
|
Example
{
"id": "80183215",
"eventType": "another-would-PM-person-air",
"occurredAt": "1994-03-28T02:57:16.445690+00:00",
"message": SMSMessageType
}SMSMessageType
Represents a SMS communication.
Fields
| Name | Description |
|---|---|
|
The account found. |
|
Attachments of the message. |
|
The ID of the SMS. |
|
SMS recipient. |
|
SMS sender. |
|
The date and time the SMS was sent. |
|
SMS body. |
Example
{
"id": "61495149",
"sentAt": "1993-02-27T13:36:34.887489+00:00",
"account": AccountType,
"sender": "include-work-prepare-structure-use",
"recipient": "style-in-bring-truth-generation",
"textBody": "carry-care-single-room-stand",
"attachments": [AttachmentType]
}SalesChannelType
A sales channel.
Fields
| Name | Description |
|---|---|
|
The sales channel code. |
|
The sales channel description. |
|
The hierarchical name of the sales channel. |
|
The name of the sales channel. |
Example
{
"name": "ever-glass-young-project-plan",
"code": "hundred-raise-back-decade-house",
"description": "entire-could-time-as-and",
"hierarchicalName": "evening-house-song-various-recognize"
}Fields
| Name | Description |
|---|---|
|
The code of this sales funnel. |
|
The collections of this sales funnel. |
|
The type of this sales funnel. |
|
The name of this sales funnel. |
|
The rules of this sales funnel. |
|
The stages of this sales funnel, in order. |
|
The status of this sales funnel. |
|
Fields not associated with a collection. |
Example
{
"code": "building-role-his-type-beautiful",
"name": "explain-guy-certain-for-fish",
"funnelType": "LEAD",
"status": "DRAFT",
"stages": [SalesFunnelStage],
"collections": [Collection],
"uncollectedFields": [FunnelField],
"rules": [SalesFunnelRule]
}Fields
| Name | Description |
|---|---|
|
The code of the funnel. |
|
The product offering of the rule. |
|
The identifier of the product offering of the rule. |
|
The code of the sales channel of the rule. |
Example
{
"funnelCode": "practice-concern-night-end-direction",
"productOfferingIdentifier": "81192786",
"productOffering": OfferingType,
"salesChannel": "simply-low-summer-third-left"
}Fields
| Name | Description |
|---|---|
|
The per-funnel unique code for this stage. |
|
The human-readable name for this stage. |
|
The order of the stage. |
Example
{
"code": "hand-around-position-wonder-sometimes",
"name": "career-explain-voice-move-officer"
}SalesTaxNodeType
Contains available tax rate options.
Fields
| Name | Description |
|---|---|
|
Available tax rate options. |
Example
{
"taxRates": [LabelValueType]
}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": "enough-positive-how-itself-above",
"action": "rather-try-little-figure-forward",
"grossAmount": 1,
"netAmount": 1,
"salesTaxAmount": 1,
"salesTaxRate": "1.0",
"reason": "difference-those-power-own-why",
"ancillaryData": {"key": "value"},
"metadata": {"key": "value"},
"internalNote": "parent-forget-attention-bar-suddenly",
"displayNote": "conference-of-industry-never-try",
"postedAfter": "1979-12-08T09:06:34.516013+00:00"
}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": "95125625",
"typename": "process-I-such-health-hit",
"typeName": "total-federal-describe-either-into",
"screenId": "85125649",
"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": "31416701",
"typename": "democratic-outside-a-effort-whether",
"content": SectionContent,
"order": 34
}Fields
| Name | Description |
|---|---|
|
The segment name. |
Example
{
"name": "our-either-worry-cold-push"
}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": "45623956",
"options": SmartFlexListItemInterface,
"selectedOptionId": "24730652"
}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": "78405382",
"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": "40240560",
"options": SmartFlexListItemInterface,
"selectedOptionId": "39021029"
}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": "49589248",
"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": "76437338",
"options": SmartFlexListItemInterface,
"selectedOptionId": "34581826"
}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": "58781938",
"label": "tend-people-method-pattern-attention"
}SelectFromListForSmartFlexOnboarding
Select from a list of options presented (in a step that inherits from SelectFromList).
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
}SelectHeatPumpMake
Options for selecting a heat pump'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": "12958882",
"options": SmartFlexListItemInterface,
"selectedOptionId": "50995678"
}SelectHeatPumpMakeForSmartFlexOnboarding
Complete the select heat pump 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 (manufacturer) of the heat pump. |
|
A unique identifier for this list item. |
Example
{
"id": "46811682",
"heatPumpMake": HeatPumpVariantType
}SelectHeatPumpVariant
Options for selecting a heat pump'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": "70118836",
"options": SmartFlexListItemInterface,
"selectedOptionId": "47559903"
}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-4646: Attempted to select multiple products for the same quoted supply point.
- 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
}SelectSessionDevice
A type where the user must select a device from a list of session devices.
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": "65803880",
"options": SmartFlexListItemInterface,
"selectedOptionId": "94917580"
}Fields
| Name | Description |
|---|---|
|
A unique identifier for this list item. |
|
A device associated with the onboarding session. |
Example
{
"id": "31215904",
"sessionDevice": SessionDeviceType
}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": "89128527",
"options": SmartFlexListItemInterface,
"selectedOptionId": "46588117"
}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": "41642757",
"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": "50064318",
"options": SmartFlexListItemInterface,
"selectedOptionId": "56093365"
}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": "61465108",
"vehicleMake": ElectricVehicleType
}SelectVehicleOrChargePoint
A step to prompt users to select between their vehicle or charge point.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
Example
{
"id": "22289763",
"selectedIntegration": "ELECTRIC_VEHICLE"
}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": "63283445",
"options": SmartFlexListItemInterface,
"selectedOptionId": "77912944"
}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": "88060166",
"vehicleVariant": ElectricVehicleType
}Fields
| Name | Description |
|---|---|
|
The selected product code. |
|
The selected product display name. |
Example
{
"code": "sport-scene-card-gas-boy",
"displayName": "huge-them-city-buy-business"
}SendFamilySwitchInOffer
Mutation to send family switch in offer to the customer. This mutation calls the process to send family switch in offer to the customer.
The possible errors that can be raised are:
- KT-CT-4123: Unauthorized.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Boolean indicator that indicated family switch in offer is sent. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"hasSent": 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
}Example
{
"message": "city-free-professional-yard-teach",
"code": "ten-hope-seat-accept-usually"
}Fields
| Name | Description |
|---|---|
|
|
|
Example
{
"field": "practice-process-beyond-serve-fight",
"errors": [ErrorTypeUnion]
}Fields
| Name | Description |
|---|---|
|
A unique session device identifier. |
|
The make (manufacturer) of the device. |
|
The model of the device. |
|
The name of the device. |
Example
{
"id": "83397570",
"name": "until-education-compare-choose-film",
"make": "stay-recent-but-commercial-light",
"model": "industry-smile-investment-arrive-stand"
}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.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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": "44694727"
}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": "thousand-it-court-space-idea"
}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]
}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
}SetUpDirectDebitInstructionForBusiness
The possible errors that can be raised are:
- KT-CT-3940: Invalid data.
- KT-CT-3956: Temporary error occurred.
- KT-CT-11107: Unauthorized.
- KT-CT-3948: Could not set up direct debit instruction.
- 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 |
|---|---|
|
The created direct debit instruction. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"paymentInstruction": DirectDebitInstructionType
}SetUpDirectDebitInstructionFromStoredDetails
The possible errors that can be raised are:
- KT-CT-3956: Temporary error occurred.
- KT-CT-3948: Could not set up direct debit instruction.
- KT-CT-3971: Instruction owners are not valid.
- KT-CT-5415: Account user not found.
- KT-CT-11103: Business not found.
- KT-CT-4123: 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 payment instruction that was created from stored details. |
|
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
}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
}ShowInputFieldErrorsActionType
An action that instructs the app to display validation errors on input fields.
Fields
| Name | Description |
|---|---|
|
List of field-level validation errors to display. |
|
Unique identifier of the object. |
|
Optional ID of the form screen these errors apply to. |
|
The name of the action object's type. |
|
The name of the object's type. |
Example
{
"typeName": "open-right-first-real-result",
"id": "24142896",
"typename": "along-Mr-eight-attention-she",
"screenId": "65060254",
"errors": InputFieldErrorType
}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. |
|
The re-authentication state of this device, if applicable. |
|
Information about the current status of this device. |
|
This contains more detail about the variant of the vehicle model. |
Example
{
"id": "74003790",
"name": "body-call-politics-early-feeling",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "70403220",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "79950153",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"reAuthenticationState": DeviceReAuthenticationInterface,
"chargingSessions": DeviceChargingSessionConnection,
"make": "story-understand-party-subject-remember",
"model": "past-behind-send-court-religious",
"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. |
|
The latest SoC received from the vehicle. It has a value between 0-100. |
|
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",
"stateOfCharge": DecimalReading,
"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": "1984-03-04T00:00:38.327273+00:00",
"end": "2020-02-11T13:58:38.641106+00:00",
"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. |
|
The re-authentication state of this device, if applicable. |
|
Information about the current status of this device. |
Example
{
"id": "46156297",
"name": "dog-suggest-then-stock-raise",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "73804077",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "79816414",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"reAuthenticationState": DeviceReAuthenticationInterface
}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": "that-its-see-hair-education",
"publishedAt": "2013-10-02T15:26:06.901967+00:00"
}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": "16:09:29.083437",
"min": 809.61,
"max": 1.2,
"upperLimit": 956.96
}Fields
| Name | Description |
|---|---|
|
The status of the device's grid export capability. |
|
The status of the device's charging duration cap. |
|
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],
"gridExport": "ENABLED"
}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": "93762377",
"smartFlexDeviceId": "56924162"
}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": "1980-02-04T22:24:44.926836+00:00",
"end": "1989-04-26T00:25:41.548168+00:00",
"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. |
|
The re-authentication state of this device, if applicable. |
|
Information about the current status of this device. |
|
The type of zone that this heat pump device represents. |
Example
{
"id": "27823708",
"name": "edge-team-treatment-health-way",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "55774641",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "62809259",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"reAuthenticationState": DeviceReAuthenticationInterface,
"make": "black-make-small-quite-represent",
"model": "recognize-edge-student-several-challenge",
"powerInKw": "1.000",
"zoneType": "CLIMATE"
}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
}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": "51910315",
"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": "50491782",
"resumable": SmartFlexResumable,
"deviceType": "BATTERIES",
"displayName": "lot-would-would-reduce-build",
"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": ["law-than-back-their-work"]
}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. |
|
The re-authentication state of this device, if applicable. |
|
Information about the current status of this device. |
|
This contains more detail about the variant of the vehicle model. |
Example
{
"id": "24057181",
"name": "history-painting-later-fill-bar",
"deviceType": "BATTERIES",
"provider": "BYD",
"integrationDeviceId": "89039143",
"status": SmartFlexDeviceStatusInterface,
"propertyId": "43073460",
"alerts": SmartFlexDeviceAlertInterface,
"onboardingWizard": SmartFlexOnboardingWizard,
"preferences": SmartFlexDevicePreferencesInterface,
"preferenceSetting": FlexDevicePreferenceSettingInterface,
"reAuthenticationState": DeviceReAuthenticationInterface,
"chargingSessions": DeviceChargingSessionConnection,
"make": "score-identify-rock-concern-wonder",
"model": "chair-like-national-image-follow",
"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": "15:25:52.277297",
"weekdayTargetSoc": 63,
"weekendTargetTime": "20:32:51.976653",
"weekendTargetSoc": 55,
"minimumSoc": 66,
"maximumSoc": 90
}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. |
|
The latest SoC received from the vehicle. It has a value between 0-100. |
|
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",
"stateOfCharge": DecimalReading,
"stateOfChargeLimit": StateOfChargeLimit,
"testDispatchFailureReason": "NONE"
}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": "30767061",
"summary": "according-agent-wife-speech-program",
"internalCode": "two-probably-who-likely-big",
"createdAt": "2021-04-13T12:09:26.376481+00:00"
}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. |
|
Example
{
"isSharingConsentGiven": true,
"records": [SpecialCircumstanceRecordUnion]
}Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per ampere per day without tax. |
|
Price per ampere per day including tax. |
|
Region of operation. |
|
Threshold for tiered standing charge rates. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "indeed-fight-democratic-skill-source",
"regionOfOperation": "black-heavy-explain-able-he",
"band": "industry-teach-let-home-home",
"validFrom": "1989-02-03T15:54:59.772430+00:00",
"validTo": "1971-02-14T05:36:28.625103+00:00",
"unitType": "eat-carry-than-edge-age",
"pricePerUnit": "1.0",
"durationMonths": 4,
"pricePerUnitIncTax": "1.0",
"threshold": "1.0"
}Fields
| Name | Description |
|---|---|
|
The standing charge's label. |
|
Price per unit per day including tax. |
|
The standing charge's unit type. |
Example
{
"pricePerUnitIncTax": "1.0",
"label": "different-consider-act-only-common",
"unitType": "according-who-always-she-stage"
}Fields
| Name | Description |
|---|---|
|
The amperage the standing charge is for. |
|
The kVA that the standing charge is for. |
Example
{
"amperage": [StandingChargeRate],
"kva": [StandingChargeRate]
}StartCollectionProcess
Start a collection process.
The possible errors that can be raised are:
- KT-CT-1111: Unauthorized.
- KT-CT-11208: Invalid billing document identifier for collection process.
- KT-CT-11209: Collection process configuration does not have published version.
- KT-CT-11210: Active collection process for entity already exists.
- KT-CT-11211: Too many active collection processes for config.
- KT-CT-11212: Invalid collection process config code.
- 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 that has been started. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"collectionProcessStarted": StartCollectionProcessOutput
}Fields
| Name | Description |
|---|---|
|
Account number associated to the collection process. |
|
The number of the collection process record. |
Example
{
"number": "eight-light-force-himself-take",
"accountNumber": "A-6BDAFCCC"
}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
}StartOnSiteJobsAppointmentBookingSession
The possible errors that can be raised are:
- KT-CT-13010: No booking adapter found for agent.
- KT-CT-13020: Could not identify agent from property.
- KT-CT-13021: Invalid job type.
- KT-CT-13022: Work category not found for job type.
- KT-CT-13023: Appointment booking checks failed.
- KT-CT-13024: Appointment booking checks returned warnings.
- KT-CT-13032: Request 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 Kraken booking ID for the appointment booking session. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"appointmentBookingSessionId": "df3fb844-3f58-4744-ad88-8841a9025b3a"
}StartReAuthentication
Create a wizard for re-authenticating a device with SmartFlex.
The possible errors that can be raised are:
- KT-CT-4321: Serializer validation error.
- KT-CT-4385: Re-authentication is not supported for this 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 wizard created for re-authenticating the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}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-4385: Re-authentication is not supported for this 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 wizard created for onboarding the device with SmartFlex. |
Example
{
"possibleErrors": [PossibleErrorType],
"wizard": SmartFlexOnboardingWizard
}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": 64,
"timestamp": "right-attorney-often-campaign-no",
"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": 87,
"edgeCount": 64
}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": "central-why-size-race-manager"
}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. |
|
ID for the statement billing document. |
|
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": 58136655,
"identifier": "94376796",
"startAt": "1972-09-15T10:32:06.740941+00:00",
"endAt": "1997-03-03T06:41:03.287415+00:00",
"firstIssuedAt": "2019-06-06T13:11:33.855023+00:00",
"earliestChargeAt": "1994-10-08T17:10:22.296216+00:00",
"latestChargeAt": "1980-09-09T09:24:24.315996+00:00",
"paymentDueDate": "2022-12-23",
"pdfUrl": "affect-happy-whatever-budget-have",
"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": 94,
"taxTotal": 18,
"grossTotal": 86
}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": "88948345",
"billType": "STATEMENT",
"fromDate": "2011-01-03",
"toDate": "2010-12-21",
"temporaryUrl": "and-boy-evidence-somebody-three",
"issuedDate": "1995-06-15",
"attachments": BillingAttachmentConnectionTypeConnection,
"closingBalance": 42,
"openingBalance": 80,
"isExternalBill": true,
"transactions": TransactionConnectionTypeConnection,
"userId": 30313569,
"toAddress": "focus-issue-drop-great-drive",
"paymentDueDate": "2004-07-25",
"consumptionStartDate": "2021-07-17",
"consumptionEndDate": "2024-05-06",
"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": "positive-worry-whole-want-media",
"description": "space-respond-action-tonight-kid",
"costExclTax": EstimatedMoneyType,
"costInclTax": EstimatedMoneyType,
"value": "1.0"
}SteppedConsumptionRate
Unit rate which is valid within a consumption range.
Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per kWh without tax. |
|
Price per kWh including tax. |
|
Region of operation. |
|
The kWh that the unit rate is valid until. |
|
The kWh that the unit rate is valid from. |
|
Time of use label for the rate. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "one-do-there-exist-treatment",
"regionOfOperation": "station-certainly-although-economy-ball",
"band": "music-upon-six-store-nearly",
"validFrom": "1980-03-19T10:13:29.826247+00:00",
"validTo": "2017-12-01T01:50:00.158513+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 94,
"pricePerUnitIncTax": "1.0",
"timeOfUse": "rest-million-event-represent-just",
"stepStart": 17,
"stepEnd": 58
}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]
}StoreBankAccountDetails
Store bank account details in GMO and get a token to be used when creating a Kraken account.
Fields
| Name | Description |
|---|---|
|
Financial institution redirect URL. |
|
Financial institution token. |
Example
{
"financialInstitutionRedirectUrl": "medical-group-trial-run-someone",
"token": "owner-experience-voice-least-spring"
}StoreDirectDebitPaymentMethodDetails
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-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 |
|---|---|
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Example
{
"possibleErrors": [PossibleErrorType],
"storedPaymentMethodDetailsReference": "investment-detail-sign-mention-onto"
}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-3979: Invalid ledger.
- 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
}Fields
| Name | Description |
|---|---|
|
The product characteristic. |
|
The string value of the characteristic. |
|
A string representation of a characteristic value, for convenience. |
Example
{
"stringValue": "garden-door-concern-station-event"
}StringType
Graphene type object to represent string values
Fields
| Name | Description |
|---|---|
|
Value of this field. |
Example
{
"stringValue": "board-several-pick-what-social"
}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-3823: Unauthorized.
- 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": "21609463",
"name": "product-check-whom-suffer-moment",
"ledgerType": "training-raise-serve-bit-minute",
"number": "appear-century-keep-these-into",
"currentBalance": 69,
"paymentAdequacy": PaymentAdequacyDetailsType
}Fields
| Name | Description |
|---|---|
|
Supply details capacity in Amperes. |
|
Supply details capacity in kVA. |
|
Supply details capacity in kW. |
|
Date when supply details came into effect. This can be before the account came on supply. |
Example
{
"amperage": 40,
"kva": 82,
"kw": "1.0",
"validFrom": "1986-04-22"
}SupplyOrServiceCharge
Supporting information for a customer charge resulting from a supply or service agreement
Fields
| Name | Description |
|---|---|
|
Agreements which were charged |
|
The period that was charged. |
Example
{
"period": Period,
"agreements": AgreementConnection
}Fields
| Name | Description |
|---|---|
|
|
|
Should this period be billed? False for accepted erroneous gains. |
|
|
|
Example
{
"supplyStartAt": "1975-03-17T21:04:55.392176+00:00",
"supplyEndAt": "2012-01-05T10:09:14.979316+00:00"
}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": 12,
"edgeCount": 98
}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": "significant-item-officer-international-structure"
}Fields
| Name | Description |
|---|---|
|
Supply point external identifier. |
|
Supply point market name. |
|
Requested supply start date. |
|
The selected product information for this supply point or None if no product is selected. |
Example
{
"externalIdentifier": "98512147",
"marketName": "discussion-from-address-change-leg",
"requestedSupplyStartDate": "1992-03-11",
"selectedProduct": SelectedProductType
}SupplyPointDetailsRaw
Customer's supply point details, raw, as fetched from OCCTO
Fields
| Name | Description |
|---|---|
|
Address of the Supply Point. |
|
Building name of the Supply Point. |
|
Postcode of the Supply Point. |
|
The code describing the electrical service area - e.g. |
|
The next reading date for this meter. |
|
SPIN - Supply Point Identification Number. |
Example
{
"spin": "describe-dark-test-thus-bank",
"readingDateNext": "have-team-old-get-item",
"gridOperatorCode": "us-account-create-especially-camera",
"addressPostcode": "upon-order-prevent-attack-still",
"address": "for-similar-style-machine-half",
"addressBuildingName": "conference-be-happy-not-Congress"
}SupplyPointTaxAdjustmentType
Represents a tax adjustment for a specific supply point.
Fields
| Name | Description |
|---|---|
|
The type of tax adjustment (e.g., EXEMPTION, REDUCTION). |
|
When this adjustment becomes effective. |
|
When this adjustment ends (null if open-ended). |
|
The proportion of usage that qualifies for the adjustment (0-1). |
|
The ID of the supply point. |
|
The tax category for this adjustment. |
|
The tax subcategory for this adjustment. |
Example
{
"supplyPointId": "85021198",
"taxCategory": "wait-ability-new-our-necessary",
"taxSubcategory": "theory-me-share-word-rule",
"qualifyingUsage": "1.0",
"adjustmentType": "friend-national-production-voice-economic",
"effectiveFrom": "1971-02-11T03:40:34.592290+00:00",
"effectiveTo": "1985-02-24T12:07:27.947167+00:00"
}SupplyPointType
Represents a SupplyPoint.
Fields
| Name | Description |
|---|---|
|
Get list of devices under a supply point. |
|
The external identifier of the supply point. |
|
The ID of the supply point. |
|
The market this supply point belongs to. |
|
The supply point's property. |
|
Get readings from a readable device e.g., a supply point, device, or register. |
Example
{
"id": "44021809",
"marketName": "move-walk-might-every-paper",
"externalIdentifier": "69589273",
"readings": Readings,
"property": PropertyType,
"devices": DevicesConnection
}SupplyProductTagType
A product tag.
Example
{
"code": "over-without-anything-choose-style",
"displayName": "to-this-color-first-major"
}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": "11188485",
"code": "truth-good-country-kind-campaign",
"notes": "forward-become-fill-ready-film",
"fullName": "type-computer-least-discover-third",
"displayName": "sense-agent-high-animal-approach",
"description": "television-join-year-sign-response",
"availableFrom": "2009-12-05T09:30:24.860101+00:00",
"availableTo": "1987-06-30T07:35:46.571458+00:00",
"isHidden": true,
"term": 33,
"endsAt": "2015-05-09T09:46:38.810039+00:00",
"brandCode": "chance-phone-beautiful-group-various",
"marketName": "black-play-around-both-art",
"availabilityStatus": "EVERYONE",
"termsContractType": "occur-travel-stop-team-out",
"termsAndConditionsTypes": TermsAndConditionsType,
"params": {"key": "value"},
"tags": SupplyProductTagType
}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
}SwitchInCorrectionPerformed
Switch-in correction was performed.
Fields
| Name | Description |
|---|---|
|
List of actions that were performed. |
Example
{
"performedActions": "CUSTOMER_NAME_CORRECTION"
}SwitchToProductOnNextReadingDate
Terminate the current agreement and create the agreement with the new product on the next reading date.
The possible errors that can be raised are:
- KT-JP-4901: Invalid data.
- KT-JP-4902: Unable to update agreement product.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The new agreement. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"agreement": Agreement
}TagType
Represents a tag used for classifying offerings and products.
Fields
| Name | Description |
|---|---|
|
Unique tag code. |
|
Display name of the tag. |
Example
{
"code": "step-market-medical-drug-forward",
"displayName": "receive-member-economic-box-decide"
}Fields
| Name | Description |
|---|---|
|
The time the data was submitted. |
|
The target temperature in Celsius. |
Example
{
"value": "1.0",
"timestamp": "1983-01-11T19:08:00.693904+00:00"
}Fields
| Name | Description |
|---|---|
|
The tariff's product code. |
|
The tariff's product's human-readable name. |
|
The grid operator code for this specific tariff. |
|
A JSON object containing extra information. |
|
A list of tiers available to the tariff. |
Example
{
"code": "anything-nothing-forget-animal-network",
"displayName": "imagine-food-police-forget-somebody",
"gridOperatorCode": "which-behind-big-drive-cold",
"productParams": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType,
"tiers": TariffTier
}Fields
| Name | Description |
|---|---|
|
A list of consumption charge rates. |
|
The contract capacity pattern of the product. |
|
A list of consumption charge rates. |
Example
{
"contractCapacityPattern": "NON_TIERED",
"consumptionRates": ConsumptionChargeRate,
"standingRates": StandingChargeValues
}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": "audience-road-respond-seem-than"
}TaxAdjustmentConfigurationType
Represents a tax adjustment configuration term in a contract.
This term stores tax adjustment details for supply points associated with the contract.
Fields
| Name | Description |
|---|---|
|
List of supply point tax adjustments. |
|
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": "forward-low-with-listen-now",
"displayName": "already-help-least-better-reach",
"description": "down-rich-positive-house-performance",
"identifier": "96400871",
"isVariable": true,
"adjustments": [SupplyPointTaxAdjustmentType]
}Fields
| Name | Description |
|---|---|
|
The ID of the operations team. |
|
The name of the operations team. |
|
The team reference for routing (e.g., 'OPERATIONS_GROUP.TEAM.TEAM_A'). |
Example
{
"id": "37081915",
"name": "decade-dog-issue-authority-treat",
"ref": "specific-respond-month-outside-figure"
}Fields
| Name | Description |
|---|---|
|
The name of the team group (e.g., 'GROUP_A'). |
|
The team group reference for routing (e.g., 'OPERATIONS_GROUP.GROUP.GROUP_A'). |
Example
{
"name": "better-tend-single-now-past",
"ref": "health-wide-pretty-I-price"
}Fields
| Name | Description |
|---|---|
|
The human-readable location name (e.g., 'London'). |
|
The location reference for routing (e.g., 'OPERATIONS_GROUP.LOCATION.London'). |
Example
{
"ref": "PM-six-middle-yet-turn",
"friendlyName": "behavior-determine-respond-hope-consumer"
}TemplateGroupType
Represents a group of line items within a template.
Fields
| Name | Description |
|---|---|
|
Category of the group (BILL or QUOTE). |
|
Whether this is the default group for its category. |
|
Label of the group. |
|
Line items within this group. |
Example
{
"label": "same-future-under-employee-behavior",
"category": "BILL",
"lineItems": [TemplateLineItemType],
"isDefault": true
}TemplateLineItemType
Represents a line item within a group in a template.
Fields
| Name | Description |
|---|---|
|
Optional description of the line item. |
|
Label of the line item. |
|
Identifier of the node this line item references. |
|
Identifier of the node output this line item references. |
Example
{
"label": "per-themselves-defense-view-red",
"nodeIdentifier": "75039383",
"nodeOutputIdentifier": "76763979",
"description": "realize-responsibility-over-page-see"
}TemplateNodesType
Container for all template node data.
Fields
| Name | Description |
|---|---|
|
Data for the rate builder node. |
|
Data for sales tax node. |
Example
{
"rateBuilder": RateBuilderNodeType,
"salesTax": SalesTaxNodeType
}TemplateType
Represents a template in the product catalog.
Fields
| Name | Description |
|---|---|
|
Unique code for the template. |
|
The currency configuration for this Kraken. |
|
Template canvas data as JSON. |
|
Optional description of the template. |
|
Groups of line items within the template. |
|
Unique identifier of the template. |
|
Whether the template can be amended (only DRAFT templates). |
|
Whether this is the latest version of the template. |
|
Display label for the template. |
|
Market the template belongs to. |
|
Maximum version number reached for this template code. |
|
Current status of the template. |
|
Whether to use bill calculations for quote generation. |
|
Current version of the template. |
Example
{
"identifier": "46893495",
"code": "art-somebody-professional-hot-remain",
"market": "authority-Republican-glass-admit-pressure",
"label": "return-describe-something-glass-mean",
"description": "far-TV-remain-not-however",
"version": 4,
"maxVersion": 84,
"data": {"key": "value"},
"useBillForQuote": true,
"status": "DRAFT",
"groups": [TemplateGroupType],
"isLatestVersion": true,
"isAmendable": true,
"currency": CurrencyType
}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": "94528488",
"summary": "else-lot-big-town-blood",
"internalCode": "end-center-special-region-everyone",
"createdAt": "1986-04-30T10:29:42.948846+00:00",
"expiryDate": "1999-07-14"
}TermTemplateComponentType
Represents a contract term template component within an offering.
Fields
| Name | Description |
|---|---|
|
The contract term template associated with this component. |
|
Unique identifier of the component. |
|
Initial/default quantity for this component. |
|
Maximum quantity of this component that can be selected. |
|
Minimum quantity of this component that can be selected. |
Example
{
"identifier": "47732898",
"minimumQuantity": 45,
"maximumQuantity": 92,
"initialQuantity": 54,
"component": TermTemplateType
}TermTemplateType
Represents a contract term template in the catalog.
Fields
| Name | Description |
|---|---|
|
The description of this contract term template. |
|
The name of this contract term template. |
|
The data associated with this contract term template. |
|
The type of contract term. |
Example
{
"termType": "history-movement-generation-new-although",
"templateData": {"key": "value"},
"name": "include-enjoy-blue-college-drop",
"description": "everybody-human-brother-something-I"
}Fields
| Name | Description |
|---|---|
|
The contract terminated. |
Example
{
"contract": Contract
}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": "1985-05-05T03:14:50.784877+00:00"
}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 market associated with the termination fee. |
|
The type of the term. |
Example
{
"type": "section-picture-industry-main-hotel",
"displayName": "bill-team-past-keep-most",
"description": "forward-when-security-everything-house",
"identifier": "35955853",
"isVariable": true,
"amount": "1.0",
"feeType": TerminationFeeType,
"marketName": "each-beat-my-such-sit"
}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": 63,
"edgeCount": 54
}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": "close-best-similar-across-enough"
}Fields
| Name | Description |
|---|---|
|
The display name of the terms and conditions. |
|
The S3 URL to the terms and conditions file. |
Example
{
"name": "least-own-sing-president-cultural",
"s3Url": "although-single-kind-social-including"
}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": "ten-picture-western-science-receive",
"pdfUrl": "design-seek-report-vote-ball",
"brandCode": "only-two-fly-ability-event",
"markdown": "investment-poor-middle-difference-young",
"html": "close-thousand-feeling-country-attorney",
"version": "understand-low-upon-response-positive",
"effectiveFrom": "2009-06-16T17:55:26.737861+00:00"
}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": "86975896",
"modifyScopesUri": "gun-others-fear-street-note",
"redirectUri": "scientist-environmental-manage-fire-ready"
}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": "93090292",
"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": "44130235",
"key": "manage-crime-serious-hundred-employee",
"uri": "open-television-behavior-move-half"
}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": "49053949",
"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": "establish-couple-somebody-use-culture",
"refusalReasons": "DEVICE_LIVE",
"errorType": "UNABLE_TO_INITIATE_TEST_CHARGE",
"reasons": ["get-mother-teach-paper-enough"],
"descriptions": ["late-audience-tree-someone-buy"]
}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": "beyond-out-away-beat-cup",
"textStyle": "TITLE1",
"textAlignment": "START",
"id": "81027976",
"typename": "heavy-of-final-marriage-single"
}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 |
|---|---|
|
The name of the third party. |
|
Holds information about the permissions of the current viewer. |
Example
{
"name": "modern-tree-improve-while-president",
"permissions": [ThirdPartyPermission]
}ThirdPartyPermission
Holds information about a specific permission.
Fields
| Name | Description |
|---|---|
|
The short name of the permission. |
Example
{
"permission": "before-maintain-entire-computer-brother"
}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": "population-political-guess-including-understand",
"endTime": "bed-father-describe-wind-town",
"daysOfWeek": "hospital-effect-cold-thus-lawyer",
"tariffType": "tree-improve-result-not-professional"
}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": "people-glass-partner-scientist-wrong",
"price": "1.0",
"type": "former-only-send-drop-once"
}Fields
| Name | Description |
|---|---|
|
Tariff intervals of the charging location. |
|
Tariff rates of the charging location. |
Example
{
"tariffs": ThirdPartyTariffType,
"tariffIntervals": ThirdPartyTariffIntervalType
}TieredConsumptionRate
Unit rate which is valid within a consumption range.
Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per kWh without tax. |
|
Price per kWh including tax. |
|
Region of operation. |
|
The m3 that the unit rate is valid until. |
|
The m3 that the unit rate is valid from. |
|
Time of use label for the rate. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "beat-boy-recently-bar-hot",
"regionOfOperation": "least-allow-always-political-laugh",
"band": "wear-toward-write-artist-public",
"validFrom": "1982-07-01T21:23:52.859819+00:00",
"validTo": "2019-09-12T15:53:24.518797+00:00",
"unitType": "DAYS_ON_SUPPLY",
"pricePerUnit": "1.0",
"durationMonths": 48,
"pricePerUnitIncTax": "1.0",
"timeOfUse": "police-bit-where-audience-article",
"tierStart": 80,
"tierEnd": 39
}TieredStandingCharge
Standing charge rate which is valid within a consumption range.
Fields
| Name | Description |
|---|---|
|
The product rate band information. |
|
Duration in months for discount product rates. |
|
Grid operator. |
|
Price per ampere per day without tax. |
|
Price per ampere per day including tax. |
|
Region of operation. |
|
Threshold for tiered standing charge rates. |
|
The m3 that the unit rate is valid until. |
|
The m3 that the unit rate is valid from. |
|
What are we charging for (kWhs consumed, Days on supply, etc). |
|
Rate validity start. |
|
Rate validity end. |
Example
{
"gridOperatorCode": "issue-country-budget-cup-word",
"regionOfOperation": "part-human-among-others-usually",
"band": "edge-level-Congress-decision-very",
"validFrom": "1993-08-31T17:46:50.726404+00:00",
"validTo": "2002-05-06T17:35:09.808087+00:00",
"unitType": "stock-ten-position-six-page",
"pricePerUnit": "1.0",
"durationMonths": 19,
"pricePerUnitIncTax": "1.0",
"threshold": "1.0",
"tierStart": 25,
"tierEnd": 26
}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": "opportunity-practice-pressure-training-attack",
"displayName": "administration-tend-play-shoulder-sea",
"description": "alone-identify-heart-realize-cold",
"identifier": "76565818",
"isVariable": true
}TimeSeriesSpecificationEligibilityScheduleType
Represents a schedule for time series specification eligibility within a contract.
Note: This type is a stub, and will be fleshed out in the future.
Fields
| Name | Description |
|---|---|
|
The period during which this eligibility is effective. |
|
Indicates if the time series specification is eligible. |
|
The product code associated with the time series specification. |
|
The time series specification code. |
Example
{
"productCode": "consider-crime-lay-fact-interesting",
"timeSeriesSpecificationCode": "east-history-here-pick-sing",
"isEligible": true,
"effectivePeriod": RateGroupEligibilityPeriodType
}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": 92,
"tax": 12,
"gross": 40
}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": 36,
"edgeCount": 61
}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": "thought-number-customer-camera-able"
}TransferLeadOpportunities
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 |
|---|---|
|
Number of opportunities transferred. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"opportunitiesTransferred": 3
}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.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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": 46
}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": "35423555",
"triggerTypeCode": "both-cost-vote-law-explain",
"createdAt": "1984-07-23T13:11:24.613465+00:00",
"messages": MessageConnection,
"processingStatus": "UNPROCESSED"
}TriggerPostUploadOperationsJPN
The possible errors that can be raised are:
- KT-JP-7802: File cannot be found with given s3 key.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Have post upload operations been triggered. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"operationsTriggered": true
}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
}UnsupportedCombination
A step that indicates the selected device is not compatible with the users existing devices.
This step cannot be completed and the user must select different device options to continue.
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
Example
{
"id": "12225584"
}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-7814: Received an invalid accountNumber.
- 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
}UpdateAccountConsentData
Updates Account consent data.
Fields
| Name | Description |
|---|---|
|
Example
{
"consentData": "abc123" | 1 | 1.0 | true | ["abc123"] | AccountType
}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
}UpdateAccountReferralStatus
Update the status of an AccountReferral.
Status transitions can only move forward: - Pending -> Paid (allowed) - Pending -> Cancelled (allowed) - Paid -> any (not allowed) - Cancelled -> any (not allowed)
The possible errors that can be raised are:
- KT-CT-6712: Invalid reference.
- KT-CT-6732: Invalid referral status transition.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated account referral instance. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountReferral": ReferralType
}UpdateAccountUser
Updates AccountUser and JPN AccountUserDetails
The possible errors that can be raised are:
- KT-CT-5414: Invalid data.
- KT-JP-5401: Account user details not found.
- KT-JP-5402: 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": AccountUser
}UpdateAccountUserByUserId
Updates AccountUser and JPN AccountUserDetails by id.
==== CAUTION ==== This mutation doesn't have the limitation of only being able to update one field per day. =================
This mutation is only available to organizations with the appropriate permissions.
The possible errors that can be raised are:
- KT-CT-5414: Invalid data.
- KT-JP-5401: Account user details not found.
- KT-JP-5402: 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],
"user": AccountUser
}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": 64.15,
"emailFormat": "air-glass-full-serve-place",
"preferredHoldMusic": "enter-total-box-easy-it",
"errors": [ErrorType],
"commsPreferences": AccountUserCommsPreferences,
"clientMutationId": "33149527"
}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": "Keith",
"familyName": "Martinez",
"pronouns": "more-old-campaign-never-country",
"mobile": "edge-power-risk-society-set",
"email": "early-customer-try-seven-perform",
"dateOfBirth": "2019-10-04",
"landline": "group-beat-little-identify-never",
"errors": [ErrorType],
"clientMutationId": "37264783"
}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 valid_to date must be later than valid_from 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
}UpdateAmperageChangeRequest
Update an amperage change request
This mutation is used by organizations for updating amperage change requests
The possible errors that can be raised are:
- KT-JP-4511: Invalid data.
- KT-CT-4501: Unauthorized.
- KT-JP-4501: Unauthorized.
- KT-JP-4502: Unauthorized.
- KT-JP-4515: Amperage change process not found.
- KT-JP-4517: Unable to update amperage change process.
- KT-JP-4518: No active workflow found.
- KT-JP-4503: Unable to communicate with industry organization.
- KT-JP-4520: Unable to process request.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
Success message. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"message": "night-east-view-feeling-hospital"
}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
}UpdateBankAccountDetails
Update bank account details for an existing customer in GMO.
Fields
| Name | Description |
|---|---|
|
Financial institution redirect URL. |
|
Financial institution token. |
Example
{
"financialInstitutionRedirectUrl": "seat-parent-great-cover-true",
"token": "space-black-job-risk-scientist"
}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-11207: Unsupported external source for collection process.
- KT-CT-11218: External reference cannot be updated once it has been set.
- 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": "indeed-floor-become-responsibility-issue",
"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": "address-either-change-ago-son",
"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
}UpdateCreditCardDetails
Updates the credit card details of an account through GMO.
The possible errors that can be raised are:
- KT-JP-3902: Payment instruction creation using the same card number on the same day is not allowed.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
Credit card number. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"cardNumber": "appear-develop-least-nation-billion"
}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
}UpdateDocumentAccessibilityPreference
Update the document accessibility preference for the input account number to the received documentAccessibilityPreference value.
The possible errors that can be raised are:
- 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 |
|---|---|
|
Account that was changed. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"account": AccountType
}UpdateInputOutput
Output type for updating an input.
Fields
| Name | Description |
|---|---|
|
The updated input. |
Example
{
"input": InputType
}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-8912: Funnel not found.
- KT-CT-8931: Extra detail value is invalid.
- KT-CT-8935: National ID bad input.
- 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"}
}UpdateLeadStage
The possible errors that can be raised are:
- KT-CT-8907: Lead not found.
- 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"}
}UpdateMessageTags
The possible errors that can be raised are:
- KT-CT-7611: The message was not found.
- KT-CT-7614: The Ink tag was 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. |
|
Confirmed tags. |
Example
{
"possibleErrors": [PossibleErrorType],
"tags": InkTag
}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
}UpdateMoveInDate
Updates a move-in date for a supply point.
Fields
| Name | Description |
|---|---|
|
New move-in date in YYYY-MM-DD format. |
|
Supply point information number. |
Example
{
"spin": "serve-available-build-join-card",
"newMoveInDate": "1973-02-24"
}UpdateMoveOutDate
Updates a move-out date for a supply point.
The possible errors that can be raised are:
- KT-JP-4539: Move out date update input data is invalid.
- KT-JP-4501: Unauthorized.
- KT-JP-4536: Move out active process not found.
- KT-JP-4540: Move out date update cannot self-service.
- KT-JP-4101: Unauthorized.
- KT-JP-4541: Not allowed to update move out process.
- KT-JP-4520: Unable to process request.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
New move-out date in YYYY-MM-DD format. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
|
Supply point information number. |
|
Task ID for the update move-out date task. |
Example
{
"possibleErrors": [PossibleErrorType],
"spin": "she-area-forget-claim-system",
"newMoveOutDate": "1990-03-17",
"taskId": "39269914"
}UpdateNotesOnOpportunity
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 |
|---|---|
|
The number of the opportunity. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"opportunityNumber": "create-common-instead-through-read"
}UpdateOfferGroupOnOpportunity
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 |
|---|---|
|
The number of the opportunity. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"opportunityNumber": "green-election-ask-point-out"
}UpdateOnSiteJobsAppointment
The possible errors that can be raised are:
- KT-CT-13001: Appointment does not exist.
- KT-CT-13043: Cannot update appointment as it has terminal status.
- KT-CT-13044: Failed to update appointment slot.
- KT-CT-13018: Unable to record cancellation_category/cancellation_sub_category.
- KT-CT-13039: Cancellation fields require CANCELLED status.
- KT-CT-13045: Failed to update appointment assets.
- KT-CT-13050: Cannot provide both supply_point_identifier_to_market_name_mapping and supply_point_internal_id when creating assets.
- KT-CT-13051: Supply point not found when creating assets.
- KT-CT-13052: Multiple supply points found when creating assets.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The Appointment that was updated. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"onSiteJobsAppointment": OnSiteJobsAppointmentType
}UpdateOnSiteJobsRequest
The possible errors that can be raised are:
- KT-CT-13032: Request does not exist.
- KT-CT-13035: Request is inactive.
- KT-CT-13038: Invalid request status.
- KT-CT-13040: Agent not set on request.
- KT-CT-13045: Failed to update appointment assets.
- KT-CT-13050: Cannot provide both supply_point_identifier_to_market_name_mapping and supply_point_internal_id when creating assets.
- KT-CT-13051: Supply point not found when creating assets.
- KT-CT-13052: Multiple supply points found when creating assets.
- KT-CT-1113: Disabled GraphQL field requested.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
Fields
| Name | Description |
|---|---|
|
The updated request. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"onSiteJobsRequest": OnSiteJobsRequestType
}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-8906: Opportunity not found.
- KT-CT-8926: Unable to create 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": "decade-skin-quite-fund-something"
}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
}UpdateProductPricesOutput
Rate group prices for a product.
Fields
| Name | Description |
|---|---|
|
The rate group prices. |
Example
{
"prices": RateGroupPrices
}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
}UpdateTemplateOutput
Output type for updating a template.
Fields
| Name | Description |
|---|---|
|
The updated template. |
Example
{
"template": TemplateType
}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
}UploadPostRequest
Information that should be used in the POST request to the S3 API.
For more details please see this.
Fields
| Name | Description |
|---|---|
|
Required fields for presigned post. |
|
S3 key for resigned post. |
|
S3 presigned post url. |
Example
{
"url": "indicate-case-skill-office-best",
"fields": {"key": "value"},
"key": "true-skill-friend-lose-field"
}Fields
| Name | Description |
|---|---|
|
Present for completed dispatches, otherwise |
|
Present for planned dispatches, otherwise |
Example
{
"source": "available-discover-risk-do-method",
"location": "offer-girl-board-wait-list"
}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": "2025-12-29T13:08:03.478436+00:00",
"end": "1996-12-21T13:33:07.030406+00:00",
"startDt": "short-letter-church-candidate-answer",
"endDt": "so-down-once-hair-avoid",
"deltaKwh": 8,
"delta": "1.0",
"meta": UpsideDispatchMetaType
}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": "why-development-well-society-realize",
"description": "painting-attack-though-term-majority",
"uri": "behavior-politics-system-board-apply"
}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": "77814445",
"userActions": [UserActionReason]
}UserInputRequired
A type that returns user inputs that need to be provided for the device to be successfully registered
Fields
| Name | Description |
|---|---|
|
A unique identifier for this onboarding step. |
|
A list of requested inputs for a user to provide in order for the onboarding journey to continue. |
Example
{
"id": "29282656",
"userInputs": [UserInputType]
}Fields
| Name | Description |
|---|---|
|
Human friendly description of the requested input. |
|
True if the requested user input is required. |
|
True if the submitted user input has been successfully validated. |
|
Identifier for the requested user input. |
|
The value that has been submitted for this input. Can be a string, integer, or boolean. |
Example
{
"key": "hair-director-Mrs-upon-player",
"description": "investment-six-take-media-bag",
"value": "direction-summer-key-life-prove",
"isRequired": true,
"isValidated": true
}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": "budget-course-smile-about-reach"
}Fields
| Name | Description |
|---|---|
|
Override Field to add additional attributes and extend description with possible_errors |
|
Example
{
"vehicleId": "50346585",
"information": VehicleInformationType
}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
}Fields
| Name | Description |
|---|---|
|
Whether the GPIN is valid. |
Example
{
"isValid": true
}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.
- KT-CT-1111: Unauthorized.
- KT-CT-1112: 'Authorization' header not provided.
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
}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
}ValidityPeriod
Represents a validity period defined by specific start and end date times.
Fields
| Name | Description |
|---|---|
|
The end date and time of the period. Null indicates an open-ended period. |
|
The start date and time of the period. |
Example
{
"start": "2009-02-09T22:37:12.616377+00:00",
"end": "1988-02-21T20:21:51.449687+00:00"
}VariantProfile
Object representing a variant profile.
Fields
| Name | Description |
|---|---|
|
The characteristic values for the variant. |
|
The scheme labels for the variant. |
Example
{
"characteristicValues": {"key": "value"},
"schemeLabels": {"key": "value"}
}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": "first-process-stock-when-sure",
"weekdayTargetSoc": 34,
"weekendTargetTime": "ground-call-I-medical-focus",
"weekendTargetSoc": 21,
"minimumSocPercentage": 42,
"maximumSocPercentage": 25
}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": "current-information-future-director-since",
"brand": "simply-form-agree-stay-police",
"model": "recognize-record-listen-see-offer",
"year": 45,
"displayName": "age-show-likely-treat-role"
}Fields
| Name | Description |
|---|---|
|
Verification process status. |
|
Verification type. |
|
Customer with pending verification. |
Example
{
"userNumber": "reason-owner-if-such-others",
"status": "country-night-standard-open-range",
"type": "office-degree-personal-government-oil"
}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": "group-around-visit-seem-level"
}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": 95,
"edgeCount": 29
}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": "size-provide-wear-become-debate"
}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": 42,
"edgeCount": 54
}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": "four-agent-once-show-trade"
}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": "21613517",
"phoneNumber": "grow-think-coach-trade-play",
"status": "UNASSIGNED",
"callWindowStart": "1979-02-12T13:04:44.517498+00:00",
"callWindowEnd": "1986-03-01T04:32:54.624521+00:00",
"accountId": "23845132",
"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": "86581553",
"name": "hair-friend-clear-paper-number",
"description": "another-resource-good-religious-serious",
"customOutboundPhoneNumber": "road-figure-every-little-street",
"tags": CallTagConnectionTypeConnection,
"status": "ACTIVE",
"campaignType": "PREVIEW",
"campaignItems": VoiceCampaignItemConnectionTypeConnection,
"preventDuplicateRecords": 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": VoucherPurchaseConnectionTypeEdge,
"totalCount": 12,
"edgeCount": 73
}VoucherPurchaseConnectionTypeEdge
A Relay edge containing a VoucherPurchaseConnectionType and its cursor.
Fields
| Name | Description |
|---|---|
|
A cursor for use in pagination |
|
The item at the end of the edge |
Example
{
"node": VoucherPurchaseType,
"cursor": "interview-young-difficult-quickly-rock"
}Fields
| Name | Description |
|---|---|
|
When the voucher becomes available to be redeemed. |
|
The current balance left in the voucher. |
|
The amount charged for the voucher. |
|
A balance transfer for the voucher charge, if any. |
|
Additional metadata from client sources stored against the voucher. This data is not structural and won't be relied on by Kraken internally. |
|
Display name for the voucher purchase. |
|
The purchase ID. |
|
The payment associated with the voucher purchase, if any. |
|
When the purchase was performed. |
|
Fetch the redemptions for this voucher. |
|
The value of the voucher in cents. |
Example
{
"id": "24251435",
"charge": AccountChargeType,
"chargeBalanceTransfer": AccountBalanceTransferType,
"payment": AccountPaymentType,
"displayName": "drop-attention-cost-discover-these",
"clientParams": {"key": "value"},
"purchasedAt": "1998-04-09T19:25:07.353376+00:00",
"voucherValue": 17,
"availableFrom": "1990-06-17",
"balance": 31,
"redemptions": [VoucherRedemptionType]
}Fields
| Name | Description |
|---|---|
|
When the redemption was claimed. |
|
The amount credited for the voucher redemption. |
|
The redemption ID. |
Example
{
"id": "98594032",
"credit": AccountCreditType,
"claimedAt": "2020-12-14T04:28:07.123861+00:00"
}Fields
| Name | Description |
|---|---|
|
The balance from vouchers that will be redeemable in future. |
|
The balance from vouchers that can be redeemable today. |
Example
{
"redeemableToday": 18,
"redeemableInFuture": 47
}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": "91651057",
"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": "86352885"
}Fields
| Name | Description |
|---|---|
|
Serial number. |
|
Meter point reference. |
|
The frequency of the reading. |
Example
{
"marketSupplyPointId": "94215824",
"deviceId": "89098343",
"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 |
|---|---|
|
Whatsapp text message body. |
Example
{
"body": "become-adult-Mrs-mother-part"
}WithdrawAccount
Withdraws an account.
The possible errors that can be raised are:
- KT-JP-7801: Unknown error occurred.
- KT-CT-1113: Disabled GraphQL field requested.
Fields
| Name | Description |
|---|---|
|
The number of the account to withdraw. |
|
Field with the possible errors of the query/mutation. Deprecated The 'possibleErrors' field is deprecated. |
Example
{
"possibleErrors": [PossibleErrorType],
"accountNumber": "A-BA6DCC14"
}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": "51693470",
"name": "car-summer-message-beautiful-find",
"isOpen": true,
"isPublicHoliday": true,
"openOrClosedReason": "CLOSED_DUE_TO_PUBLIC_HOLIDAY"
}Fields
| Name | Description |
|---|---|
|
The time the temperature was reported. |
|
Value of the temperature in Celsius. |
|
Name of the zone. |
Example
{
"zone": "clear-control-page-room-in",
"value": "1.0",
"timestamp": "1985-12-18T04:19:31.608669+00:00"
}Authentication Server
Fields
| Name | Description |
|---|---|
|
The client ID of the application. |
|
The name of the application. |
Example
{
"name": "force-probably-room-admit-hour",
"clientId": "68580624"
}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": "like-the-themselves-middle-beyond",
"devicePhone": "put-cup-painting-difficult-front",
"totpSecret": "law-land-big-could-lead"
}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": "well-author-east-nature-past",
"SHA": "fire-similar-partner-opportunity-treat",
"isPinned": true
}Fields
| Name | Description |
|---|---|
|
The type of MFA device. |
|
Whether the MFA device is confirmed or not. |
Example
{
"deviceType": "red-happy-bad-finish-agent",
"isConfirmed": true
}PossibleError
Representation of a graphQL error.
Example
{
"code": "it-film-buy-without-strategy",
"type": "type-wide-Mr-create-message",
"message": "star-peace-market-maintain-body",
"description": "me-likely-member-others-production"
}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": "approach-PM-capital-grow-wait",
"code": "hospital-wrong-yeah-official-society",
"type": "house-little-dinner-hotel-drug",
"description": "poor-out-peace-industry-travel"
}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
}