⚙️
API Docs
  • ⚙️WalletChat API Reference
  • Reference
    • API Reference
      • Authentication
      • Direct Messages (DMs)
      • NFT Chats
      • Group Chats (Non-NFT Related)
      • Common API Endpoints
      • Inbox
      • Unused / Legacy
Powered by GitBook
On this page
  1. Reference
  2. API Reference

Authentication

Authentication related API endpoints:

PreviousAPI ReferenceNextDirect Messages (DMs)

Last updated 2 years ago

  • POSTSign In with signed nonce value, currently JWT token returned should be valid for 24 hours
  • GETIf the current wallet doesn't have a valid local JWT, need to request a new nonce to sign

If the current wallet doesn't have a valid local JWT, need to request a new nonce to sign

get

As part of the login process, we need a user to sign a nonce genrated from the API, to prove the user in fact the owner of the wallet they are siging in from. JWT currently set to 24 hour validity (could change this upon request)

Path parameters
addressstringRequired

wallet address to get nonce to sign

Responses
200
OK
application/json
Responseany
get
GET /users/{address}/nonce HTTP/1.1
Host: 
Accept: */*
200

OK

No content

Sign In with signed nonce value, currently JWT token returned should be valid for 24 hours

post

Every call the to API after this signin should present the JWT Bearer token for authenticated access. Upon request we can change the timeout to greater than 24 hours, or setup an addtional dedicated API for an agreed upon development and maintenance cost

Body
addressstringOptional
msgstringOptional
namestringOptional
noncestringOptional
sigstringOptional
Responses
200
OK
application/json
Responseinteger
post
POST /signin HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 73

{
  "address": "text",
  "msg": "text",
  "name": "text",
  "nonce": "text",
  "sig": "text"
}
200

OK

1