An Entity is an end user (individual or business) of your product.

Endpoints in this section contain methods to create, verify, and get information about Entities.

Business Entities
Registration and validation of business entities has a very specific order of operations. We suggest reviewing the KYB (Know Your Business) section for an overview of the process.

Registration Flow

All flows start with registering an individual or a business entity.

Checks if a specific handle is already taken.

Creates a new business or individual user and attaches KYC data and specified blockchain address to an assigned handle.

This step does not start the KYC verification; it only adds the data to be verified.
Generating a specified blockchain/crypto address (wallet) is part of the /register endpoint.
See User Private Key & Wallet Public Key callout below.

Starts KYC verification process on a registered user handle.

Returns whether entity attached to user handle is verified, not valid, or still pending.

We recommend setting up webhook management in the Console and taking advantage Sila's KYC Status Update Event webhook to check KYC.

Before you can transact you will need to link a bank account to the entity's crypto (wallet) address.


User Private Key & Wallet Public Key

Sila uses ECDSA to secure and validate requests. Learn more about that here.

If you are using a Sila Native SDK see "wallet generation" section for the public/private key pair function.

  • wallet private key = user private key
  • crypto_address (aka ETH Address or blockchain address) = public key

If you are building you own AUTH refer to the Authenticating with ECDSA docs.


Private keys

Please NEVER share your private keys.

  • Even test private keys used in the sandbox need to be kept a hidden.
  • Remember to redact private keys and any other PII when sending code samples.
  • Private Keys must be stored in an approved KMS
    Sila Security Requirements can be reviewed here.

Did this page help you?