Skip to content

Overview

If you are ready to begin integrating the SDK, make sure you have an SDK installed and configured. You can install each SDK by following the instructions in each page under Build in the sidebar.

When using the SDK, you can pass parameters to the default service constructors and use the provided methods to set different active profiles.

Authorization

See our security section for more information on how we have implemented wallet authentication and authorization.

SDK Services

Our SDK is broken down into the following services:

Using an SDK Service

If you are using one of the Trinsic SDKs, you will need to create an instance of a service in order to use it.

const accountService = new AccountService();

var myAccountService = new AccountService(_options);

account_service = AccountService(server_config=trinsic_config())

opts, err := NewServiceOptions(WithTestEnv())
if !assert2.Nil(err) {
    return
}

accountService, err := NewAccountService(opts)
if !assert2.Nil(err) {
    return
}

var accountService = new AccountService(TrinsicUtilities.getTrinsicServiceOptions());

account_service = Trinsic::AccountService.new(nil, Trinsic::trinsic_prod_server)

All service constructors also accept a ServiceOptions object as an argument, allowing you to specify a default ecosystem and other configuration properties.

ServiceOptions

Configuration for Trinsic SDK Services

Field Type Description
server_endpoint string Trinsic API endpoint; defaults to prod.trinsic.cloud
server_port int32 Trinsic API port; defaults to 443
server_use_tls bool Whether TLS is enabled between SDK and Trinsic API; defaults to true
auth_token string Authentication token for SDK calls; defaults to empty string (unauthenticated)
default_ecosystem string Default ecosystem ID to use for various SDK calls; defaults to default

Top

The exact structure of this object will depend on the language you are working with. You can always rely on your editor's intellisense when in doubt.

Authors: Michael Boyd, Joshua Coffey