junifer_au_native_api v1.62.0

junifer_au_native_api

JuniferAuNativeApi - JavaScript client for junifer_au_native_api Junifer Native Web API provided by the Gentrack Cloud Integration Services

How It Works

For how to prepare your application to call Junifer Native Web API, please refer to:

• Read me first
• Sovereignty Regions
• Preparing your request
• Authentication
• Responses

Sample of requesting contact details

The following is an example of calling get contact details API in UK region:

curl -X GET \\
    https://api-uk.integration.gentrack.cloud/v1/junifer/contacts/1010 \\
    -H 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBJZCI6IjA2NDYxODczLTFlOWMtNGVkMy1iZWZkLTU3NGY5ZmEwYjExYyIsIm9yZ0lkIj
oiQzAwMDAiLCJ0b2tlbl91c2UiOiJhY2Nlc3MiLCJpYXQiOjE1MzA1ODkwODcsImV4cCI6MTUzMDU5MjY4NywiaXNzIjoiaHR0cHM6Ly9hcGkuZ2VudHJhY2suaW8vIn0.WUAFYWTTEAy
Q0Bt4YXu-mxCXd-Y9ehwdZcYvcGNnyLTZH_hiJjtXWWfsx69M606pvCP6lLMT7MfK-F3E4rLO6KAlGsuz4A_7oVWQf4QNeR178GnwgmqQRw5OnLxwPbPrRa9nODngwGq8dcWejhmEYU6i
w02bvYdQBHnnsc3Kpyzw7Wdv_3jnBS4TPYS20muQOgG6KxRp9hLJM7ERLoAbsULwqdPOV8eUJJhGrq1NDuH_lA83YRDZmCWEzw96tSm3hb7y88kXs-4OvamnO1m5wFPBx69VximlS4Ltr
3ztqU2s3fHoj0OJLIafge9JvTgvuB6noHfs1uSRaahvstGJAA'

The sample of response is as follows.

{
   \"id\": 1010,
   \"contactType\": \"Business\",
   \"title\": \"Mr\",
   \"forename\": \"Tony\",
   \"surname\": \"Soprano\",
   \"email\": \"bigtone@didntseeanything.com\",
   \"dateOfBirth\": \"1959-08-24\",
   \"phoneNumber1\": \"44626478370\",
   \"address\":{
     \"address1\": \"633 Stag Trail Road\",
     \"address2\": \"North Caldwell\",
     \"address3\": \"New Jersey\",
     \"postcode\": \"NE18 0PY\"
   },
   \"links\": {
     \"self\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/contacts/1010\",
     \"accounts\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/contacts/1010/accounts\"
   }
}

General Rules/Patterns

Navigation

A links section is returned in most requests.

This section contains how to access the entity itself and, more importantly, how to access items related to the entity.

For example take the following response:

{
  \"id\": 1,
  \"name\": \"Mr Joe Bloggs\",
  \"number\": \"00000001\",
  \"surname\": \"Bloggs\",
  \"links\": {
    \"self\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/customers/1\"
  },
  \"accounts\": [
    {
      \"id\": 7,
      \"name\": \"Invoice\",
      \"number\": \"00000001\",
      \"currency\": \"GBP\",
      \"fromDt\": \"2013-05-01\",
      \"createdDttm\": \"2013-05-08T13:36:34.000\",
      \"balance\": 0,
      \"billingAddress\": {
        \"address1\": \"11 Tuppy Street\"
      },
      \"links\": {
        \"self\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/accounts/7\",
        \"customer\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/customers/1\",
        \"bills\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/accounts/7/bills\",
        \"payments\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/accounts/7/payments\"
      }
    }
  ]
}

The self URL in the links section can be used to access the entities listed in the response. In the above example there are self fields for the customer itself, and the accounts under this customer. There are other links under the account.

For example the above example contains links for the following:

• bills – List of Bills for the Account
• payments – List of Payments for the Account
• customer – Link back to the Account’s Customer

About IDs

The id in the API requests (JSON payload and URL) and responses identifies the resource within the API. It has no business meaning or purpose, therefore shouldn't be exposed to the end user in any way.

As the IDs of the resources aren't sequential or aligned with any other resource IDs, it is highly recommended using the links section from the responses to navigate to other related resources. Given the example above, the customer with ID 1 links to the account with ID 7. The links section will populate the correct IDs in the URLs so none of the assumptions about related resource IDs need to be made by the implementer.

Accessing accounts by account number

Throughout this API, anywhere an account is accessed by its id (i.e. the URL includes /accounts/:id), it can also be accessed by its account number by replacing /accounts/:id with accounts/accountNumber/:num.

For example: the Create Account Credit endpoint, available at /accounts/:id/accountCredits, can also be accessed at /accounts/accountNumber/:num/accountCredits.

Standard data types in JSON

The standard data types are as follows:

• String – Quoted as per JSON standard
• Number – Unquoted as per JSON standard
• Decimal – Unquoted as per JSON standard
• Date – In the standard ISO format \"yyyy-MM-dd\"
• DateTime – In the standard ISO format \"yyyy-MM-ddThh:mm:ss.SSS\" (no time zone component)
• Boolean – Unquoted 'true' and 'false' are the only valid values

Ordering of data

Response representations are not ordered unless specified on a specific resource. Therefore, clients should be implemented to use the name of fields/objects as the key for accessing data.

For example in JSON objects are comprised of key/value pairs and clients should be implemented to search on the ‘key’ value rather than looking for the nth key/value pair in the object.

Changes of data

Response representations may change without warning in the following ways.

• Additional key/value pairs may be added to an existing object
• Additional sub-objects may be added to an existing object

These changes are considered non-breaking.

Therefore, clients should be implemented to consume only the data they need and ignore any other information.

Versioning

The API is usually changed in each release of Junifer. Navigate to different versions by clicking the dropdown menu in the top right of this web page.

Pagination

Some REST APIs that provide a list of results support pagination.

Pagination allows API users to query potential large data sets but only receive a sub-set of the results on the initial query. Subsequent queries can use the response of a prior query to retrieve the next or previous set of results.

Pagination functionality and behaviour will be documented on each API that requires it.

Pagination on existing APIs

Existing APIs may have pagination support added. In the future this pagination will become mandatory.

In order to facilitate API users planning and executing upgrades against the existing APIs, pagination is optional during a transition period. API users can enable pagination on these APIs by specifying the pagination query parameter. This parameter only needs to be present, the value is not required or checked. If this query parameter is specified, then pagination will be enabled. Otherwise, the existing non-paginated functionality, that returns all results, will be used.

API users must plan and execute upgrades to their existing applications to use the pagination support during the transition period. At the end of the transition period pagination will become mandatory on these APIs.

For new APIs that support pagination, it will be mandatory with the initial release of the API.

Ordering

The ordering that the API provides will be documented for each API.

An ordering is always required to ensure moving between pages is consistent.

Some APIs may define an ordering on a value or values in the response where appropriate. For example results may be ordered by a date/time property of the results.

Other APIs may not define an explicit ordering but will guarantee the order is consistent for multiple API calls.

Limiting results of each page

The desiredResults query parameter can be used to specify the maximum number of results that may be returned.

The APIs treat this as a hint so API callers should expect to sometimes receive a different number of results. APIs will endeavour to ensure no more than desiredResults are returned but for small values of desiredResults (less than 10) this may not be possible. This is due to how pages of data are structured inside the product. The API will prefer to return some data rather than no data where it is not possible to return less than desiredResults

If desiredResults is not specified the default maximum value for the API will be used. Unless documented differently, this value is 100.

If desiredResults is specified higher than the default maximum for the API a 400 error response will be received.

Cursors

The pagination provided by the APIs is cursor-based.

In the JSON response additional metadata will be provided when pagination is present.

• after cursor points to the start of the results that have been returned
• before cursor points to the end of the results that have been returned

These cursors can be used to make subsequent API calls. The API URL should be unchanged except for setting the before or after query parameter. If both parameters are specified, then an error 400 response will be received.

Cursor tokens must only be used for pagination purposes. API users should not infer any business meaning or logic from cursor representations. These representations may change without warning when Junifer is upgraded.

When scrolling forward the after cursor will be absent from the response when there are no more results after the current set.

When scrolling backwards the before cursor will be absent from the response when there are no more results before the current set.

In addition, a paginated response will include a next and previous URLs for convenience.

Best practices

The following best practices must be adhered to by users of the pagination APIs:

• Don't store cursors or next and previous URLs for long. Cursors can quickly become invalid if items are added or deleted to the data set
• If an invalid cursor is used, then a 404 response will be returned in this situation. API users should design a policy to handle this situation
• API users should handle empty data sets. In limited cases a pagination query using a previously valid cursor may return no results

Example

This example is illustrative only.

A small desiredResults parameter has been used to make the example concise. API users should generally choose larger values, subject to the maximum value.

The following API call would retrieve the first set of results.

Request

https://api-uk.integration.gentrack.cloud/v1/junifer/uk/meterPoints/1/payg/balances?desiredResults=3 \\
    -H 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9....aahvstGJAA'

Response

{
  \"results\": [
    {
      \"snapshotDateTime\": \"2019-04-20T00:00:00.000\",
      \"creditBalance\": 109,
      \"emergencyCreditBalance\": 0,
      \"accumulatedDebtRegister\": 0,
      \"timeDebtRegister1\": 0,
      \"timeDebtRegister2\": 0,
      \"paymentDebtRegister\": 0
    },
    {
      \"snapshotDateTime\": \"2019-04-19T00:00:00.000\",
      \"creditBalance\": 108,
      \"emergencyCreditBalance\": 0,
      \"accumulatedDebtRegister\": 0,
      \"timeDebtRegister1\": 0,
      \"timeDebtRegister2\": 0,
      \"paymentDebtRegister\": 0
    },
    {
      \"snapshotDateTime\": \"2019-04-18T00:00:00.000\",
      \"creditBalance\": 107,
      \"emergencyCreditBalance\": 0,
      \"accumulatedDebtRegister\": 0,
      \"timeDebtRegister1\": 0,
      \"timeDebtRegister2\": 0,
      \"paymentDebtRegister\": 0
    }
  ],
  \"pagination\": {
    \"cursors\": {
      \"after\": \"107\"
    },
    \"next\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/uk/meterPoints/1/payg/balances?pagination=&desiredResults=3&after=107\"
  }
}

The results section contains the payload of the API.

The pagination section contains details needed to retrieve additional results.

API users can choose to use the next URL directly or use the after cursor token to construct the URL themselves.

The API call to query the next set of results would be

Request

https://api-uk.integration.gentrack.cloud/v1/junifer/uk/meterPoints/1/payg/balances?pagination=&desiredResults=3&after=107 \\
    -H 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9....aahvstGJAA'

Response

{
  \"results\": [
    {
      \"snapshotDateTime\": \"2019-04-17T00:00:00.000\",
      \"creditBalance\": 106,
      \"emergencyCreditBalance\": 0,
      \"accumulatedDebtRegister\": 0,
      \"timeDebtRegister1\": 0,
      \"timeDebtRegister2\": 0,
      \"paymentDebtRegister\": 0
    },
    {
      \"snapshotDateTime\": \"2019-04-16T00:00:00.000\",
      \"creditBalance\": 105,
      \"emergencyCreditBalance\": 0,
      \"accumulatedDebtRegister\": 0,
      \"timeDebtRegister1\": 0,
      \"timeDebtRegister2\": 0,
      \"paymentDebtRegister\": 0
    },
    {
      \"snapshotDateTime\": \"2019-04-15T00:00:00.000\",
      \"creditBalance\": 104,
      \"emergencyCreditBalance\": 0,
      \"accumulatedDebtRegister\": 0,
      \"timeDebtRegister1\": 0,
      \"timeDebtRegister2\": 0,
      \"paymentDebtRegister\": 0
    }
  ],
  \"pagination\": {
    \"cursors\": {
      \"before\": \"106\",
      \"after\": \"104\"
    },
    \"previous\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/uk/meterPoints/1/payg/balances?pagination=&before=106&desiredResults=3\",
    \"next\": \"https://api-uk.integration.gentrack.cloud/v1/junifer/uk/meterPoints/1/payg/balances?pagination=&desiredResults=3&after=104\"
  }
}

This time the response contains both before and after tokens and previous and next URLs. The before token or previous link can be used to navigate backwards in the results.

This SDK is automatically generated by the OpenAPI Generator project:

• API version: 1.61.1
• Package version: 1.61.1
• Build package: org.openapitools.codegen.languages.JavascriptClientCodegen

Installation

For Node.js

npm

To publish the library as a npm, please follow the procedure in "Publishing npm packages".

Then install it via:

npm install junifer_au_native_api --save

Finally, you need to build the module:

npm run build

Local development

To use the library locally without publishing to a remote npm registry, first install the dependencies by changing into the directory containing package.json (and this README). Let's call this JAVASCRIPT_CLIENT_DIR. Then run:

npm install

Next, link it globally in npm with the following, also from JAVASCRIPT_CLIENT_DIR:

npm link

To use the link you just defined in your project, switch to the directory you want to use your junifer_au_native_api from, and run:

npm link /path/to/<JAVASCRIPT_CLIENT_DIR>

Finally, you need to build the module:

npm run build

git

If the library is hosted at a git repository, e.g.https://github.com/GIT_USER_ID/GIT_REPO_ID then install it via:

    npm install GIT_USER_ID/GIT_REPO_ID --save

For browser

The library also works in the browser environment via npm and browserify. After following the above steps with Node.js and installing browserify with npm install -g browserify, perform the following (assuming main.js is your entry file):

browserify main.js > bundle.js

Then include bundle.js in the HTML pages.

Webpack Configuration

Using Webpack you may encounter the following error: "Module not found: Error: Cannot resolve module", most certainly you should disable AMD loader. Add/merge the following section to your webpack config:

module: {
  rules: [
    {
      parser: {
        amd: false
      }
    }
  ]
}

Getting Started

Please follow the installation instruction and execute the following JS code:

var JuniferAuNativeApi = require('junifer_au_native_api');

var defaultClient = JuniferAuNativeApi.ApiClient.instance;
// Configure API key authorization: tokenAuth
var tokenAuth = defaultClient.authentications['tokenAuth'];
tokenAuth.apiKey = "YOUR API KEY"
// Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
//tokenAuth.apiKeyPrefix['Authorization'] = "Token"

var api = new JuniferAuNativeApi.AccountCreditsApi()
var id = 3.4; // {Number} Account credit ID number
var callback = function(error, data, response) {
  if (error) {
    console.error(error);
  } else {
    console.log('API called successfully.');
  }
};
api.juniferAccountCreditsIdDelete(id, callback);

Documentation for API Endpoints

All URIs are relative to https://api-au.integration.gentrack.cloud/v1

Documentation for Models

• JuniferAuNativeApi.AcceptDraftBillPostBillsIdAcceptdraftResponse404
• JuniferAuNativeApi.AcceptQuotePostQuotesIdAcceptquoteResponse400
• JuniferAuNativeApi.AcceptQuotePostQuotesIdAcceptquoteResponse404
• JuniferAuNativeApi.AddPropertiesPostProspectsIdAddPropertiesResponse400
• JuniferAuNativeApi.AusCreateConcessionPostAuConcessionsCreateconcessionRequestBody
• JuniferAuNativeApi.AusCreateConcessionPostAuConcessionsCreateconcessionResponse200
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBody
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBodyAddress
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBodyContacts
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBodyElectricityProduct
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBodyElectricityProductMeterPoints
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBodyMultipleElectricityProducts
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerRequestBodySupplyAddress
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerResponse200
• JuniferAuNativeApi.AusEnrolBusinessCustomerPostAuCustomersEnrolbusinesscustomerResponse400
• JuniferAuNativeApi.AusEnrolCustomerPostAuCustomersEnrolcustomerRequestBody
• JuniferAuNativeApi.AusEnrolCustomerPostAuCustomersEnrolcustomerRequestBodyElectricityProduct
• JuniferAuNativeApi.AusEnrolCustomerPostAuCustomersEnrolcustomerResponse200
• JuniferAuNativeApi.AusEnrolCustomerPostAuCustomersEnrolcustomerResponse400
• JuniferAuNativeApi.AusGetDiscountsGetAuAccountsIdDiscountsResponse200
• JuniferAuNativeApi.AusLifeSupportSensitiveLoadPostAuCustomersLifesupportRequestBody
• JuniferAuNativeApi.AusLifeSupportSensitiveLoadPostAuCustomersLifesupportResponse400
• JuniferAuNativeApi.AusLinkDiscountPostAuAccountsIdDiscountsRequestBody
• JuniferAuNativeApi.AusRenewAccountPostAuAccountsIdRenewalRequestBody
• JuniferAuNativeApi.AusRenewAccountPostAuAccountsIdRenewalRequestBodyAgreements
• JuniferAuNativeApi.AusRenewAccountPostAuAccountsIdRenewalResponse200
• JuniferAuNativeApi.AusRenewAccountPostAuAccountsIdRenewalResponse200Results
• JuniferAuNativeApi.AusRenewAccountPostAuAccountsIdRenewalResponse400
• JuniferAuNativeApi.AusRenewAccountPostAuAccountsIdRenewalResponse404
• JuniferAuNativeApi.AusSiteAccessPostAuCustomersSiteaccessRequestBody
• JuniferAuNativeApi.AusSiteAccessPostAuCustomersSiteaccessResponse400
• JuniferAuNativeApi.BillEmailsGetBillemailsIdResponse200
• JuniferAuNativeApi.BillEmailsGetBillemailsIdResponse200Files
• JuniferAuNativeApi.BillEmailsGetBillemailsIdResponse200Links
• JuniferAuNativeApi.BillEmailsGetBillemailsIdResponse200Links1
• JuniferAuNativeApi.BillEmailsGetBillemailsIdResponse404
• JuniferAuNativeApi.CalculateNextPaymentDateGetPaymentscheduleperiodsCalculatenextpaymentdateResponse400
• JuniferAuNativeApi.CancelAccountCreditDeleteAccountcreditsIdResponse400
• JuniferAuNativeApi.CancelAccountDebitDeleteAccountdebitsIdResponse400
• JuniferAuNativeApi.CancelAccountReviewPeriodsDeleteAccountsIdCancelaccountreviewperiodResponse400
• JuniferAuNativeApi.CancelTicketPostTicketsIdCancelticketResponse400
• JuniferAuNativeApi.ChangeAccountCustomerPutAccountsIdChangeaccountcustomerRequestBody
• JuniferAuNativeApi.ChangeAccountCustomerPutAccountsIdChangeaccountcustomerResponse400
• JuniferAuNativeApi.ChangeAccountCustomerPutAccountsIdChangeaccountcustomerResponse404
• JuniferAuNativeApi.CommunicationsEmailsGetCommunicationsemailsIdResponse200
• JuniferAuNativeApi.CommunicationsEmailsGetCommunicationsemailsIdResponse200Links
• JuniferAuNativeApi.CommunicationsEmailsGetCommunicationsemailsIdResponse404
• JuniferAuNativeApi.ContactsGetAccountsIdContactsResponse200
• JuniferAuNativeApi.ContactsGetAccountsIdContactsResponse200Address
• JuniferAuNativeApi.ContactsGetAccountsIdContactsResponse200Links
• JuniferAuNativeApi.ContactsGetAccountsIdContactsResponse400
• JuniferAuNativeApi.ContactsGetCustomersIdContactsResponse200
• JuniferAuNativeApi.ContactsGetCustomersIdContactsResponse400
• JuniferAuNativeApi.CreateAccountCreditPostAccountsIdAccountcreditsRequestBody
• JuniferAuNativeApi.CreateAccountCreditPostAccountsIdAccountcreditsResponse400
• JuniferAuNativeApi.CreateAccountCreditPostAccountsIdAccountcreditsResponse404
• JuniferAuNativeApi.CreateAccountDebitPostAccountsIdAccountdebitsRequestBody
• JuniferAuNativeApi.CreateAccountDebitPostAccountsIdAccountdebitsResponse400
• JuniferAuNativeApi.CreateAccountDebitPostAccountsIdAccountdebitsResponse404
• JuniferAuNativeApi.CreateAccountNotePostAccountsIdNoteRequestBody
• JuniferAuNativeApi.CreateAccountNotePostAccountsIdNoteResponse200
• JuniferAuNativeApi.CreateAccountNotePostAccountsIdNoteResponse400
• JuniferAuNativeApi.CreateAccountRepaymentPostAccountsIdRepaymentsRequestBody
• JuniferAuNativeApi.CreateAccountRepaymentPostAccountsIdRepaymentsResponse200
• JuniferAuNativeApi.CreateAccountRepaymentPostAccountsIdRepaymentsResponse200Links
• JuniferAuNativeApi.CreateAccountRepaymentPostAccountsIdRepaymentsResponse400
• JuniferAuNativeApi.CreateAccountReviewPeriodPostAccountsIdAccountreviewperiodsRequestBody
• JuniferAuNativeApi.CreateAccountReviewPeriodPostAccountsIdAccountreviewperiodsResponse200
• JuniferAuNativeApi.CreateAccountReviewPeriodPostAccountsIdAccountreviewperiodsResponse400
• JuniferAuNativeApi.CreateAccountTicketPostAccountsIdTicketsRequestBody
• JuniferAuNativeApi.CreateAccountTicketPostAccountsIdTicketsResponse200
• JuniferAuNativeApi.CreateAccountTicketPostAccountsIdTicketsResponse200Links
• JuniferAuNativeApi.CreateAccountTicketPostAccountsIdTicketsResponse200TicketEntities
• JuniferAuNativeApi.CreateAccountTicketPostAccountsIdTicketsResponse400
• JuniferAuNativeApi.CreatePaymentSchedulePeriodPostPaymentscheduleperiodsRequestBody
• JuniferAuNativeApi.CreatePaymentSchedulePeriodPostPaymentscheduleperiodsResponse200
• JuniferAuNativeApi.CreatePaymentSchedulePeriodPostPaymentscheduleperiodsResponse400
• JuniferAuNativeApi.CreatePaymentSchedulePeriodPostPaymentscheduleperiodsResponse404
• JuniferAuNativeApi.CreatePropertyPostPropertysRequestBody
• JuniferAuNativeApi.CreatePropertyPostPropertysResponse200
• JuniferAuNativeApi.CreatePropertyPostPropertysResponse400
• JuniferAuNativeApi.CreateProspectPostProspectsRequestBody
• JuniferAuNativeApi.CreateProspectPostProspectsRequestBodyCustomer
• JuniferAuNativeApi.CreateProspectPostProspectsRequestBodyCustomerCompanyAddress
• JuniferAuNativeApi.CreateProspectPostProspectsRequestBodyCustomerPrimaryContact
• JuniferAuNativeApi.CreateProspectPostProspectsResponse200
• JuniferAuNativeApi.CreateProspectPostProspectsResponse400
• JuniferAuNativeApi.CreateProspectPutCustomersIdCreateprospectRequestBody
• JuniferAuNativeApi.CreateProspectPutCustomersIdCreateprospectResponse200
• JuniferAuNativeApi.CreateProspectPutCustomersIdCreateprospectResponse400
• JuniferAuNativeApi.CreateStripePaymentPostStripepaymentcardsIdPaymentsResponse200
• JuniferAuNativeApi.CreateStripePaymentPostStripepaymentcardsIdPaymentsResponse400
• JuniferAuNativeApi.CreateStripePaymentPostStripepaymentcardsIdPaymentsResponse401
• JuniferAuNativeApi.EmailPostCommunicationsEmailRequestBody
• JuniferAuNativeApi.EmailPostCommunicationsEmailResponse400
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBody
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBodyDirectDebitInfo
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBodyElectricityEstimate
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBodyElectricityProduct
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBodyGasProduct
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBodyGasProductMprns
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountRequestBodySupplyAddress
• JuniferAuNativeApi.EnrolAdditionalAccountPostCustomersIdEnroladditionalaccountResponse200
• JuniferAuNativeApi.EnrolCustomerPostCustomersEnrolcustomerRequestBody
• JuniferAuNativeApi.EnrolCustomerPostCustomersEnrolcustomerRequestBodyAddress
• JuniferAuNativeApi.EnrolCustomerPostCustomersEnrolcustomerRequestBodyContacts
• JuniferAuNativeApi.EnrolCustomerPostCustomersEnrolcustomerResponse200
• JuniferAuNativeApi.EnrolCustomerPostCustomersEnrolcustomerResponse400
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBody
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodyElectricityEstimate
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodyElectricityProduct
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodyElectricityProductMpans
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodyGasEstimate
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodyGasProduct
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodyGasProductMprns
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsRequestBodySupplyAddress
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsResponse200
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsResponse200Links
• JuniferAuNativeApi.EnrolMeterPointsPostAccountsIdEnrolmeterpointsResponse400
• JuniferAuNativeApi.GetAccountAgreementsGetAccountsIdAgreementsResponse200
• [JuniferAu