Engineering · Okta coverage
Spike API and Okta: SSO, SCIM and offboarding
API that collects and standardizes health data from wearables such as Apple Health, Oura and Garmin. No SCIM provisioning found.
SCIM pricing for every app →What Okta covers for Spike API, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Spike API account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 8 of 8 capabilities for Spike API.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to Spike API with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Spike API logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the Spike API account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes Spike API roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes Spike API access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in Spike API. | Changes the Spike API password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Spike API accounts. | Pulls the Spike API user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Spike API. | Step level evidence for every action StitchOps takes in Spike API. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to Spike API with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Spike API logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the Spike API account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes Spike API roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Spike API access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Spike API.
StitchOps
Changes the Spike API password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Spike API accounts.
StitchOps
Pulls the Spike API user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Spike API.
StitchOps
Step level evidence for every action StitchOps takes in Spike API.
Okta coverage from the Okta Integration Network, read October 24, 2026. Spike on okta.com StitchOps for Okta →
SCIM and API tax
What Spike API charges to automate accounts.
We found no SCIM provisioning for Spike API: the Okta Integration Network lists no provisioning for it, and Spike API does not publish SCIM support. Ask the vendor before you count on it.
Pricing notes
No SCIM found: no provisioning in the Okta Integration Network as of October 24, 2026 and no published SCIM support.
Last verified 2026-10-24 (estimate). SCIM pricing for every app · Method
Estimate Spike API and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Spike API accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the Spike API account with the right role when your HR system or identity provider says someone starts.
Movers
Change Spike API roles, teams and access when someone changes department or manager.
Leavers
Remove Spike API access the same day someone leaves, and free the seat.
Access checks
List who can log in to Spike API on a schedule, with evidence for the audit.
Common questions.
Does Spike API support SCIM?
Not that we found. The Okta Integration Network lists no provisioning for Spike API, and Spike API does not publish SCIM support, so accounts are created and removed by hand or by a tool that works in Spike API the way an admin would.
Can Spike API accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Spike API accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is Spike API in the Okta Integration Network?
Yes. As of October 24, 2026, the OIN lists Spike with SWA sign in and no provisioning.
Can Okta deprovision Spike API users?
Not through an OIN connector. StitchOps removes Spike API accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Spike API passwords when someone leaves?
StitchOps logs in to Spike API, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.