Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

INSURANCE.SQUARE_TRADE

NAME

EXAMPLE VALUE

MANDATORY

DESCRIPTION

BASE_URL

api-stage4.squaretrade.com (test)

Yes

The base endpoint for the Telenor Wholesale REST API.

CLIENT_ID

N074R341V41u38u7C10533n0u9hR19h7

Yes

The value to use for the client_id part of the client_id:client_secret credentials that must be Base64-encoded and can then be used to call endpoint oauth/v2/token; see also parameter CLIENT_SECRET.

CLIENT_SECRET

4n07h3rF4k3V41u3

Yes

The value to use for the client_secret part of the client_id:client_secret credentials that must be Base64-encoded and can then be used to call endpoint oauth/v2/token; see also parameter CLIENT_ID.

USERNAME

api_F4k3V41u3

Yes

The value to use for the username argument in the call to endpoint oauth/v2/token; see also parameter PASSWORD.

PASSWORD

M0r3F4k3V41u3sF0r3v3r

Yes

The value to use for the password argument in the call to endpoint oauth/v2/token; see also parameter USERNAME.

TOKEN

No

If branded USERNAME,PASSWORD,CLIENT_ID, CLIENT_SECRET parameters are used, this parameter has to be created manually.

The currently valid token for authorization.

This will be automatically populated if there is only one set of credentials used. If multiple sets of credentials (USERNAME,PASSWORD,CLIENT_ID, CLIENT_SECRET) are used via branding of parameters, in combination with a set of non-branded/default credentials, this parameter has to be created beforehand, so as not to interfere with the non-branded/default one.

TOKEN_EXPIRY

No

If branded USERNAME,PASSWORD,CLIENT_ID, CLIENT_SECRET parameters are used, this parameter has to be created manually.

The point in time at which the current token will expire.

This will be automatically populated if there is only one set of credentials used. If multiple sets of credentials (USERNAME,PASSWORD,CLIENT_ID, CLIENT_SECRET) are used via branding of parameters, in combination with a set of non-branded/default credentials, this parameter has to be created beforehand, so as not to interfere with the non-branded/default one.

Hookpoints

Due to the amount of values that are needed in the api, but are not available in rator core, hookpoints are used to generate the requests:

Name

Hookpoint key

Description

Context

Result

Create

SQUARE_TRADE_CREATE_REQUEST

Used for creating insurances

A square trade order with key SQUARE_TRADE_ORDER

A com.cdrator.insurance.message.request.CreateInsuranceRequest with key SQUARE_TRADE_REQUEST

Change

SQUARE_TRADE_CHANGE_REQUEST

Used for changing between types of insurances

A square trade order with key SQUARE_TRADE_ORDER

A com.cdrator.insurance.message.request.ChangeInsuranceRequest with key SQUARE_TRADE_REQUEST

Terminate

SQUARE_TRADE_TERMINATE_REQUEST

Used for terminating an insurance

A square trade order with key SQUARE_TRADE_ORDER

A com.cdrator.insurance.message.request.TerminateInsuranceRequest with key SQUARE_TRADE_REQUEST