Migrating to Trinsic Domain

As part of the rebrand from Streetcred.id to Trinsic, we will be discontinuing the api.streetcred.id domain and will continue hosting the Trinsic APIs at api.trinsic.id. This document is to help you seamlessly make the transition to the new Trinsic domain.

Use Cases

Manual API Calls

If you are manually calling the Streetcred APIs, simply change the hostname of the URL and swap out the API path to the renamed API.

Streetcred.idTrinsic
api.streetcred.idapi.trinsic.id
/agency/credentials
/custodian/wallet
N/A/provider

For example,GET https://api.streetcred.id/agency/v1/connections becomes GET https://api.trinsic.id/credentials/v1/connections.

C# Service Client

If you are currently using our Streetcred C# Asp.Net service client, switch to the new Trinsic C# Asp.Net service client. There will be some minor changes to methods and classes that will be needed, but it this is the service client that we will continue to maintain and upgrade as we make additions to our APIs.

Javascript Service Client

If you are currently using our Streetcred Javascript service client, switch to the new Trinsic Javascript service client. Versions 1.1.4070 and earlier of the Trinsic service client will need to upgrade to version 1.1.4220 or newer.

Migrating from the Streetcred service client to the Trinsic service client will introduce a few breaking changes. These primarily regard an effort to make requests have a flatter, simpler JSON structure. On our docs site, all endpoints have sample code that document how to access the endpoint via the service clients. If you have questions about a specific method, please reference this documentation.

For endpoints where a request body is required, the top level of JSON is no longer required. For example:

let connection = await agencyClient.createConnection({
  connectionInvitationParameters: {
      name: name,
      connectionId: connectionId,
      multiParty: multiParty
  }
});

becomes:

let connection = await credentialsClient.createConnection({
  name: name,
  connectionId: connectionId,
  multiParty: multiParty
});

For endpoints where a request body is optional, the top level of JSON is still required. For example:

// Optionally issue a credential with different values than offered
let newCredentialValues = {
  "Attribute A": "new value",
  "Attribute B": "new value"
};
await credentialsClient.issueCredential(credential.credentialId, {
    body: newCredentialValues
});

We have also renamed a few methods:

  • custodianClient.getConnections()walletClient.listConnections()
  • custodianClient.getInvitations()walletClient.listInvitations()

Did this page help you?