Connect Provkeep, for platforms

A button in your software. Each of your customers signs in to their own Provkeep account, approves, and your software gets a key that checks their orders. They choose and pay for their own plan. You connect free.

Connect Provkeep

Three steps

  1. Register your app. Sign in to your own Provkeep account, open Settings, Connections, and register your product with its https return address. Register a test app first: its customers get test keys for the sandbox.
  2. Send your customer to sign in. Your button opens the address below. They sign in or make a free account, see your product's name and your Provkeep account's name, and approve.
  3. Swap the code for a key. We send them back to your return address with a code. Your server swaps it for a key and a refresh token, and calls the API with the key.

The calls

The sign in address. PKCE with S256 is required, and no client secret is issued.

https://provkeep.com/oauth/authorize?response_type=code&client_id=pkc_YOUR_CLIENT_ID&redirect_uri=https%3A%2F%2Fapp.example.com%2Fprovkeep%2Fcallback&code_challenge=YOUR_S256_CHALLENGE&code_challenge_method=S256&scope=provkeep&state=YOUR_STATE

The swap, form encoded:

curl -X POST https://provkeep.com/oauth/token \
  -d grant_type=authorization_code \
  -d client_id=pkc_YOUR_CLIENT_ID \
  -d code=THE_CODE \
  -d redirect_uri=https://app.example.com/provkeep/callback \
  -d code_verifier=YOUR_VERIFIER

The answer:

{
  "access_token": "pk_live_...",
  "token_type": "Bearer",
  "refresh_token": "pkr_...",
  "scope": "provkeep"
}

A check with that key. A test app's key starts pk_test_ and goes to https://sandbox.provkeep.com/v2.

curl -X POST https://api.provkeep.com/v2/checks \
  -H "Authorization: Bearer pk_live_..." \
  -H "Idempotency-Key: your-order-123" \
  -H "Content-Type: application/json" \
  -d '{"code":"your-order-123","patient_state":"OH","consult_type":"video",
       "lines":[{"peptide":"BPC-157","dosage_form":"injectable"}]}'

The key lasts until the customer revokes it in Settings, Keys, where it appears with your product's name. Swapping the refresh token (grant_type=refresh_token) gives a new key and a new refresh token and ends the old ones. If a refresh answers invalid_grant, send the customer through the button again. Every field and answer: the API reference.

The button

Any link or button works. This one is plain HTML you can restyle.

<a href="YOUR_AUTHORIZE_URL"
   style="display:inline-block;padding:10px 16px;border-radius:8px;
          background:#2563EB;color:#fff;font:600 15px system-ui;text-decoration:none">
  Connect Provkeep
</a>

What you agree to, and what you get

  • Show the quote, its source and its date wherever you show an answer, and never present it as Provkeep saying an order is allowed or denied. Your clinician or pharmacist decides.
  • Send no patient or prescriber information. The API has no field for it: what we never receive.
  • Tell us when a quote looks wrong, at support@provkeep.com.
  • You earn 20% of what each customer you connect pays Provkeep, for their first 12 months, counted from the day they first connect through your live app. Settings, Connections shows how many you have connected. Your customer is told this on the approval screen, and their price is the same either way.
  • 12 months' notice before an API version you use stops answering: the change policy.

Building Provkeep into your product and want to talk first? Write to support@provkeep.com with what your software does and where the check would sit.