Docs · Connect your tools
Connect Smile ID
StackWeaver reads, and never changes, one read-only endpoint on your Smile ID account once a day, through a partner id and secret key you create yourself. Today this confirms the credential is valid and reachable; it does not yet perform or evidence a real identity verification. This guide says exactly what is read, which permission the credential needs, how to create one, and how to remove it.
Last reviewed: 6 November 2026 · Describes what is live in production on that date. A result is evidence of what the provider returned at a time, nothing more.
1. What it collects
Once a day StackWeaver mints a short-lived token from the partner id and secret key you paste, then calls one Smile ID endpoint with it. The result is kept as an Evidence Object with a SHA-256 fingerprint (platform), including a result that fails.
| Check (as shown in the portal) | What it looks at |
|---|---|
| API key valid and reachable | Whether the stored partner id and key are accepted and Smile ID's supported-ID-types catalog responds. Evidence only: no threshold is applied. |
2. What it does not do
- It does not perform or evidence a real identity verification. No document, biometric or other personal lookup is run through this connector. The one check reads a static catalog of supported document types, never a real person's data.
- It cannot change anything: the credential is used for one read-only endpoint.
- It does not say your KYC or AML programme meets any requirement. A result is what Smile ID returned at a certain time.
3. The access it needs
Two values: a partner id and a secret API key, used to mint a short-lived token (Smile ID) that authorises the one read-only call.
Who can connect. In StackWeaver, a workspace owner or admin pastes the partner id and key. Smile ID does not tell StackWeaver who created the credential or what role they hold, so create it with no more access than this one read-only check needs.
4. Connect steps
- In Smile ID's portal, open Security Settings / API Key Management and create a production credential.
- In StackWeaver, open Evidence, the Smile ID section, and paste the partner id and the secret API key.
- Press Test connection. StackWeaver records the result.
5. Reading the results
| Label | What it means |
|---|---|
| Pass | The provider returned data that meets the threshold at that time |
| Fail | The provider returned data that does not meet the threshold |
| Not enabled | There was nothing to check, or the feature needs a plan StackWeaver could not confirm |
| Could not check | StackWeaver could not read the data, or the check needs a higher plan than the account has |
6. Disconnect and revoke
- In StackWeaver, press Disconnect on the Smile ID section. StackWeaver deletes the stored key.
- In Smile ID's portal, remove the API key yourself — StackWeaver has no way to ask Smile ID to revoke a credential on your behalf.
What remains. Past evidence stays in your workspace as the audit trail. Disconnecting does not delete it.
7. Troubleshooting
| Message | What to do |
|---|---|
| Smile ID did not mint a token | Check the partner id and key were copied correctly and belong to the same account |
| Smile ID refused the partner id or key: they may be wrong or revoked | Check the credential has not been removed in the Smile ID portal |
Still stuck? Use the contact page.
Sources and method
Statements about GitHub and Okta link to their own documentation. Statements about StackWeaver link to the page that says them, or are recorded in a claims ledger with the file in StackWeaver's repository that they come from. See oureditorial policy. Spotted an error? Use the contact page.