Ticbolt API Integration
  • Introduction
  • ✨GET STARTED
    • Create Account
    • Create API project
    • Access control
  • 🎯API ENDPOINTS
    • POST - createEvent
    • GET - eventInfo
    • POST - buyTickets
    • GET - userPortfolio
    • POST - userSignedMessage
  • 🧳Webhooks
    • Webhook - createEventStatus
    • Webhook - buyTicketStatus
Powered by GitBook
On this page
  • Response:
  1. API ENDPOINTS

POST - userSignedMessage

Signs a message using the user's wallet for an NFT for a particular contract address.

The API is used to generate the QR code at the user app to display for verification.

Http method

POST

URL endpoint

https://api.ticbolt.com/v1/userSignedMessage

Request header

API token - The token can be easily copied from the partner dashboard for the project created.

Request body

Json object with the details of the event to be created.

Example structure :

{
    "emailAddress" : "[email protected]",
    "contractAddress" : "0xabcdef12345...",
    "nftId" : "1234.."
}

Parameter description :

  • userEmailAddress (String): The email address of the user making the purchase.

  • contractAddress (String): The contract address of the event for which the entry is required.

  • nftId (String) : The NFT for which the QR code to be generated.

Response:

The API will respond with a JSON payload. Depending on the outcome of the request, the structure will differ:

Successful Response:

{
    "status": "success",
    "data": {
        "signedMessage": "abcdef12345&12345absndkjbdrgj2498ywefuh3r98hfkjvbkjsduhr"
    }
}

Failed Response:

{
    "status": "fail",
    "data": {
        "message": "Descriptive error message"
    }
}

Error Response:

{
    "status": "error",
    "data": {
        "message": "Exception or error message"
    }
}

PreviousGET - userPortfolioNextWebhook - createEventStatus

Last updated 1 year ago

🎯