Content Comparison

Common problems

• The URL entered must end by /api. If Otipass provided a different url, like: https://otipass.net/api/toulouse, the part in bold must be removed and entered in the json as OtipassProjectId
• Check that the JSON  syntax is correct (for example using https://jsonlint.com/)
• The screen of external interfaces of tnac is buggy. It will remove the password each time you save. So you have to manually add everytime you do any change.

{
   
   "OtipassProjectId":"toulouse", //The project id of Otipass. It is generally the last part of the url that they provide.
   "NumType":"serial", //define this value if the pass codes start with letters
   "sectorInfos":{
      "DDMM_AUG":{ //This is the sector code as defined in TNAC configuration.
         "OtipassServiceId":"pcumid031fs00061", //Provided by Otipass
         "OtipassPSpaceId":"PROVIDER#PCUMID031FS00061", //Provided by Otipass
         "seasonCode":"DDMM23", //Those are the season and product codes on which the sales will be processed.
         "productCode":"PASSTOU"
      },
      "DDMM_MSR":{
         "OtipassServiceId":"PCUMID031FS00071",
         "OtipassPSpaceId":"PROVIDER#PCUMID031FS00071",
         "seasonCode":"DDMM23",
    

Beware of the following two points:

• In the parameters, a given sector code can only appear once.
• The device scanning Otipass tickets must be linked to a door which must be associated to only one sector.