View Source Turnkey.APIClient.SubOrganization (TurnkeyEx v0.0.1-alpha2)

Turnkey Sub Organizations allow for a permissioning model where our users have control over their keys and our api key has read access only.

https://docs.turnkey.com/api#tag/Organizations

Summary

Functions

All users are given a suborganization controlled by their passkey ( authenticator_params ). It is created with a single Ethereum private key. Our api key retains read access.

Functions

Link to this function

create_sub_organization_from_authenticator(email, authenticator)

View Source
@spec create_sub_organization_from_authenticator(
  String.t(),
  Turnkey.APITypes.Authenticator.t()
) ::
  {:ok, Turnkey.APIClient.SubOrganization.TrimmedResult.t()}
  | {:error, {:instructer_parse_error, String.t()}}
  | {:error, String.t()}

All users are given a suborganization controlled by their passkey ( authenticator_params ). It is created with a single Ethereum private key. Our api key retains read access.

This is an asyncronous activity, so the activity is polled until completion.