Collaborate

Stage
Goal
Definition of done
Timeline

Stage 1

Hanchu will establish a dedicated sandbox environment for partner included a simulated device

  • Hanchu grants this sandbox environment for the partner

1 week

Stage 2

Partner builds for HanchuESS Connect

  • Hanchu provides partner credentials in sandbox (attached below)

  • Partner provides their details which is needed in next stage (detailed below)

  • Partner provides a completed feature development checklist (attached below)

  • Partner is able to access the test device and simulate the registration process on their own

Dependent on partner

Stage 3

Partner conducts a HanchuESS Connect verification process with a live device in their own sandbox environment

  • Partner is able to verfy HanchuESS Connect process with no issues

  • Partner provides their client details which is needed in next stage (detailed below)

1 to 2 week

Stage 4

Partner conducts a production test with Hanchu

  • Partner is able to successfully onboard one device in the production environment.

1 week

Stage 5

Partner conduction Alpha/Beta test commence on production and invite several colleagues or customers to experience

  • Partner finished Alpha/Beta test phase and confirm market release plan

2 to 4 week

Stage 6

Integration go live

NA

NA

What we provide

In order for 3rd parties to connect to the Hanchu, we will provide the following details.

  • Client ID and Client Secret

  • Org ID

  • Scopes (Default ALL if not specified)

  • Signature Key

  • Base URL

  • Endpoints

    • Auth URL

    • Token URL

    • Token revoke URL

    • Devices URL

    • Events URL

  • Dashboard URL or similar (i.e., a way for partner to confirm device behavior)

What you privode

In order for 3rd parties to connect to the Hanchu, you will need to provide the following details.

  • Redirect URI

  • Authentication API (used before we push telemetry to you)

  • Connect System User Email

  • Connect System User password

  • Api Key

  • 128 x 128 Logo (i.e., png, view in grant page)

  • Brand name (i,e., HanchuESS)

Please note that Kraken will ask to onboard a physical test device in the test environment, so please be prepared for this.

Checklist

Please find the checklist attached below. 3rd parties will be asked to return this checklist to Hanchu to indicate they have finished HanchuESS Connect development.

PreviousTutorialsNextPrinciples

Last updated