search

How to update identity?

Process of updating an identity

hashtag
Arrange Identity

Arrange identity in the format

  • If want to remove addresses from secondary, do not add them in the list

  • If want to add new addresses in secondary, add them in secondary list

  • If want to keep some addresses in secondary, then keep them in the data

{
  "id": "string",
  "identifier": "string",
  "provider": "string",
  "default": {
    "address": "address",
    "chain": number,
    "isContract": boolean
  },
  "secondary": [
    {
      "address": "address",
      "chain": number,
      "isContract": boolean
    },
    {
      "address": "address",
      "chain": number,
      "isContract": boolean
    }
  ]
}

hashtag
Generate Message

Using the above arranged identity, generate a message using the below endpoint and sign it using default address by following guide for respective chains

hashtag
Generate Message

post
/identity/generate-message
Authorizations
secret-keystringRequired
Body
idstringRequired
identifierstringRequired
providerstringRequired
currentSignaturestringOptional
previousSignaturestringOptional
Responses
chevron-right
200Success
application/json
statusintegerOptional
timestampstring · date-timeOptional
post
/identity/generate-message

After generating message, you need to sign message using appropriate functions for respective chains, check our guide for each blockchain here

There are 2 signatures needed while updating identity

  • currentSignature - Will be signed by current (new) default address

  • previousSignature - Will be signed by previous (old) default address, only if default is updated

  • If default isn't updated, you need to use same signature for both currentSignature and previousSignature

hashtag
Update Identity

After signing the message, add the generated signature in the arranged identity, at currentSignature and previousSignature respectively

Now, data should look something like this

Call Update Identity API

hashtag
Important Note

  • If default chain is APTOS, then while calling this API, swap default address with public key of the same address, so that we can easily verify signatures

  • If default is changing in this request, then send previous default address's public key in extraData: { publicKey: "" }

  • For example

    • satyam@martian has APTOS has default chain

    • In this request, we are updating it to EVM

    • Signed message using EVM address will be in currentSignature

    • Signed message using APTOS address will be in previousSignature

    • To verify previousSignature, we need to have publicKey of the APTOS address, which we will send in extraData

So now, data will look something like this

hashtag
Update Identity

patch
/identity
Authorizations
secret-keystringRequired
Body
idstringRequired
currentSignaturestringRequired
previousSignaturestringOptional
Responses
chevron-right
200Success
application/json
idstringRequired
identifierstringRequired
providerIdstringRequired
defaultAddressstringRequired
nonceintegerOptionalDefault: 0
currentSignaturestringRequired
previousSignaturestringOptional
isContractbooleanOptionalDefault: false
syncedAtstring · date-timeRequired
createdAtstring · date-timeOptional
patch
/identity

Identity should now be created, if faced with any error, check our troubleshooting guide or ask in our discord

hashtag
Resolve Identity

hashtag
Get Identity

get
/identity
Authorizations
secret-keystringRequired
Query parameters
idstringOptionalExample: satyams@fetcch
addressstringOptionalExample: 0x8E9e20b90efa7d0A072bfc8b0C74D96104F1F6FE
signedMessagestringOptionalExample: 0x8E9e20b90efa7d0A072bfc8b0C74D96104F1F6FE34423232
Responses
chevron-right
200Success
application/json
statusintegerOptional
timestampstring · date-timeOptional
get
/identity
PreviousHow to create identity?NextTransaction Requests

Last updated