Reserve Digital Passports

Reserve digital passports from your pool for your target customers.

Before you begin

Some digital passports can be reserved from your digital passports pool. This feature is helpful to give versatility to brands.

Use case example: Your brand wants to secure 50 digital passports for loyal customers or VIPs.


  • When a user scans a code or click on the reserved link, but does not necessarily request the ownership of the digital passport, The digital passport is removed from the pool of digital passport to be distributed. This is secure the claiming experience of each user.
  • In the case of many digital passports that have been scanned but not claimed, you can reset digital passports to make them available for distribution again.
  • You must trigger an API call per digital passport. Example, if you need the generate 50 individual links, the API must be called 50 times.

Let's start πŸš€

To reserve 100 digital passports, use the dispenser/distribution/reserveOne.


The API is authenticated with the user rights required β†’ certCreate

tagsStringβœ…Tags to pickup a digital passport and reserve it. Can be 1 tag or a list of tags (see how to format query params array - separated by comma for example)
formatlink, linkObjectβœ…β†’ link: returns text plain link such as,passphrase
β†’ linkObject: returns link as .json object


200The digital passport is reserved.
400β†’ Your tag may not exist.
β†’ There is not available digital passport to reserve.
// linkObject return

    "method": "requestOwnership",
    "certificateId": 440105186,
    "passphrase": "v6lsj4vhg5dx",
    "deeplink": {
				"certificateId": 440105186,
        "passphrase": "v6lsj4vhg5dx",
        "link": ",v6lsj4vhg5dx"
// link return,v6lsj4vhg5dx
    "name": "API Error",
    "description": "No NFT found to distribute",
    "code": "nmp.back.dispenser.oneToOne.noNFTsToSend",
    "httpCode": 400