- The private key stays on the machine and proves it is the one making requests.
- The public key is the matching half. You send it to us, we register it, and we use it to check that each request really comes from your machine.
The standard behind this is OAuth 2.0 with private key JWT client authentication (RFC 7523). Your machine signs a short-lived request with its private key, we check the signature against the public key you registered, and we then issue an access token. Keys use the ES256 algorithm on the P-256 elliptic curve.
Onboarding at a glance
1
Generate a key pair
Create an ES256 key pair on the machine that will call the API. See Key pair setup.
2
Send us the public key
Send only
es256-public.pem, with the fingerprint and your onboarding details, to your Credit Benchmark contact.3
Receive your onboarding pack
We register the key and send you an onboarding pack with your client details and runnable sample scripts.
4
Request access tokens
Your machine signs a short-lived client assertion with its private key and sends it to the token endpoint. We verify the signature against the public key registered under your
KID and return an access token. See Request an access token.
