Environments and Credentials
We currently have 2 environments available for partners:
- Production - operational and highly available. Uses real Kin.
- Beta - A place to test your newest Kin integrations. Lower availability. Uses fake Kin.
Each environment services multiple applications. Each application has it's own:
app_id- the main identifier for the app.
- JWT public keys - the keys exchanged by the digital service and kin upon the onboarding process.
- Rate limits and configuration
On beta, we have generic credentials for a
test app that are prebuilt into our sample app. The sample app has no server side to generate and sign JWT messages, thus it generates and signs the JWT payloads locally on the device with the example private key (see Android example).
You can use these credentials to connect to the beta environment as the
test app before you start your onboarding.
On production you will have to have been set up with your own credentials.