This guide builds on the starting from scratch guide and adding optional column guide and will go over how to create SMS code resolvers for your site columns.

SMS Code Resolvers

Jancy has third-party integrations that can resolve SMS codes. The formatting of these integrations can be found on our profile documentation page here.

  1. The image below shows an empty site column, this example is using a site column that specifies the Ticketmaster site, but the steps will be the same regardless of the site being specified.

profilecsv8.png

  1. For this example, we will use the seathero resolver, to find the formatting of the other resolvers please visit our profile documentation here.

profilecsv18.png

<aside> ❗ After making changes to your profile CSV, make sure to save the file then refresh its contents on the profile settings page in Jancy using the refresh button under the CSV.

</aside>

<aside> ❗

Make sure you also add the SMS Number column to your profile CSV as well. This will be the number Jancy uses when making the request for the code. You can find information on how to format this column here.

</aside>

Adding Parser to SMS Resolver

  1. To add a parser to the email resolver above the formatting is going to be seatheros:API-KEY:parser. For the parser to be identified we need to add a colon then the parser at the end of the resolver. In the example below we will use the ticketmaster ****parser, for a list of all of the recognized Jancy parsers please visit our profile documentation here.

profilecsv19.png

The step above is all you will need to do to add a parser.

<aside> ❗ After making changes to your profile CSV, make sure to save the file then refresh its contents on the profile settings page in Jancy using the refresh button under the CSV.

</aside>

<aside> ❗

Make sure you also add the SMS Number column to your profile CSV as well. This will be the number Jancy uses when making the request for the code. You can find information on how to format this column here.

</aside>

This concludes creating SMS resolvers. The process to adding any of the other integrated services will be the same, with the difference being how that specific resolver is formatted. You can find all of the resolvers and how they are formatted in our profile documentation here.