Skip to content

Conversation

@t-vila
Copy link
Contributor

@t-vila t-vila commented Jan 20, 2026

No description provided.

Copy link
Contributor

@ethankonk ethankonk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small nits, otherwise I think it looks good!

### Credential bundle method

**Note:** on web, this method is only supported with the legacy iframe-based flow, if no hard requirement to use encrypted bundles, we suggest to use the IndexedDB-based OTP flow instead.
**Note:** This method is only supported by **legacy iframe-based flows** and is not available in the current Turnkey SDKs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Started recently using our <Note></Note> component, I find it looks much better, could be used here!

Suggested change
**Note:** This method is only supported by **legacy iframe-based flows** and is not available in the current Turnkey SDKs.
<Note> **Note:** This method is only supported by **legacy iframe-based flows** and is not available in the current Turnkey SDKs. </Note>

Makes it looks like this:
image

| | public_key | string | The public key of the credential that approved the request |
| **Activity** | type | string | The type of the activity (e.g. ACTIVITY_TYPE_SIGN_TRANSACTION_V2) |
| | resource | string | The resource type the activity targets: `USER`, `PRIVATE_KEY`, `POLICY`, `WALLET`, `ORGANIZATION`, `INVITATION`, `CREDENTIAL`, `CONFIG`, `RECOVERY`, `AUTH`, `OTP`, `PAYMENT_METHOD`, `SUBSCRIPTION` |
| | resource | string | The resource type the activity targets: `USER`, `PRIVATE_KEY`, `POLICY`, `WALLET`, `ORGANIZATION`, `INVITATION`, `CREDENTIAL`, `CONFIG`, `AUTH`, `OTP`, `PAYMENT_METHOD`, `SUBSCRIPTION` |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we no longer target RECOVERY resource types? Even though we plan on deprecating the email recovery activities, I still feel we should keep it in some parts of our docs for legacy customers or anyone choosing to use the deprecated methods for whatever reason

Not too opinionated on this so if you feel we should remove it altogether feel free!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm down to keep references in the policies documentation. We can add (deprecated) just in case.

| | DELETE | ACTIVITY_TYPE_DELETE_PAYMENT_METHOD |
| **SUBSCRIPTION** | CREATE | ACTIVITY_TYPE_ACTIVATE_BILLING_TIER |
| **CONFIG** | UPDATE | ACTIVITY_TYPE_UPDATE_ALLOWED_ORIGINS |
| **RECOVERY** | CREATE | ACTIVITY_TYPE_INIT_USER_EMAIL_RECOVERY |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

Copy link
Contributor

@andrewkmin andrewkmin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for tackling this. Should be strong enough to steer people away from recovery; if people still somehow get confused, we could include some more explicit deprecation notices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants