Service Costs

General

Implement a custom fee service

The service costs feature enables you to implement complex variations for determining shipping fees. Basic service costs for shipping are already configurable via the SCAYLE Panel. Using this checkout extension allows you to use your very own logic to determine service costs and build a highly customized user experience around it.

Once you have configured the API Credentials for this service, checkout will execute calls to the given endpoint. The results of your calculation will be used and stored with the order.

How to implement

You need to provide a http service that can handle the usual load of your shop and which accepts requests from the SCAYLE networks.

If you want to limit incoming traffic by IP address, your SCAYLE Account Manager can provide more information about our networks.

This service needs to implement a POST endpoint according to the following schema:

Request

Your endpoint needs to be able to serve the following request.

Authentication

Basic auth according to SCAYLE Panel configuration.

Headers

Parameter	Details
X-Shop-Id	Integer The current shop-country id

Parameter

Details

X-Shop-Id

Integer

The current shop-country id

Body

Request example

Request schema

id integer

address object (optional)
- billing object (optional)
  - id integer
  - additional string ([!-ɏ0-9 ]) (optional)
  - city string ([!-ɏ0-9 ])
  - countryCode string (optional) (minimum length: ) (maximum length: 3)
  - houseNumber string ([!-ɏ0-9 ])
  - recipient object
  - referenceKey string (optional)
  - state string (optional) (maximum length: 60)
  - street string ([!-ɏ0-9 ])
  - title string ([!-ɏ0-9 ]) (optional)
  - zipCode string ([A-z0-9\- ]{1,12})
- shipping object (optional)
  - id integer
  - additional string ([!-ɏ0-9 ]) (optional)
  - city string ([!-ɏ0-9 ])
  - collectionPoint object (optional)
  - countryCode string (optional) (minimum length: ) (maximum length: 3)
  - houseNumber string ([!-ɏ0-9 ])
  - recipient object
  - referenceKey string (optional)
  - state string (optional) (maximum length: 60)
  - street string ([!-ɏ0-9 ])
  - title string ([!-ɏ0-9 ]) (optional)
  - zipCode string ([A-z0-9\- ]{1,12})

cost object
- appliedReductions array (optional)
  - amount object
  - category enum (voucher)
  - code string (optional)
  - type enum (relative absolute)
- withoutTax integer
- withTax integer

customData object (optional)

customer object
- id integer
- customData object (optional) (object is extensible as desired)
- firstName string (optional)
- gender enum (m f d) (optional)
- lastName string (optional)
- referenceKey string (optional)

ipAddress string (optional)

items array
- id integer (optional)
- availableQuantity integer (optional)
- currency string (optional) (minimum length: ) (maximum length: 3)
- customData object (optional) (object is extensible as desired)
- deliveryForecast object (optional)
  - deliverable object
  - subsequentDelivery object
- key string
- merchant object (optional)
  - id integer
- price object
  - appliedReductions array (optional)
  - tax object
  - withoutTax integer
  - withTax integer
- product object
  - id integer
  - attributes object (object is extensible as desired)
- variant object
  - id integer
  - referenceKey string
  - stock object (optional)

payment array
- amount integer
- key string
- options object (optional)
  - countOfInstallments integer (optional)
  - hasPaybreak boolean (optional)

shipping object
- deliveredOn string ([0-9]{4}\-[0-9]{2}\-[0-9]{2}) (optional)
- policy enum (least_packages earliest_shipping delivery_deadline next_business_day_express) (optional)

Response

Your service needs to follow this specification when handling the checkout request.

Response body

Response example

Response schema

shipping object
- deliveryCosts integer
- expressDeliveryCosts integer (optional)

The response body will be written to the order.customData.fees property. In case the request failed, checkout will store "requestFailed": true.

Status Codes:

Code	Description	Response Body
`201`	request was successful
`401`	authentication failed	empty