Promoted articles
- Exporting and Downloading Organization and Session Files
- Downloading Data using the Export Hub
- Release Notes v2.24
- Poster Sessions
- Talk Now for Poster Sessions
- How to use Keys to translate Meeting Names and Desktop Headers
- Creating Keys to Translate Meeting Names and Desktop Navigation
- Unpublishing an App from the Android App Store
- Removing an App from the Apple Store
Fetching Users' Magic Links via Pathable API Follow
The Pathable system generates a unique, "magic" login link for each user profile that bypasses the need to log in using a password. This link can be retrieved via the user's security settings in -admin, or can be fetched via an API call to the Pathable REST API.
Requirements for retrieving Magic Links via API:
- All attendees must be imported via a data feed
- The ability to call the Pathable API
- All attendees must be assigned a "personId" (more on that later)
Setting up the Data Feed
In order to generate a Magic Link for users, they must first exist in the Pathable database. You can learn more about importing users via a data feed in the article "Import People from Registration Service"
Set up an API Request
Review Pathable's API documentation to set up your call. A new public endpoint has been created for the Magic Link, which should be exposed on yourAPI call.
Finding your X-API-KEY
In your admin dashboard, visit Settings->API. The first Read+Write field will create tokens applicable to user records.
Your API endpoint will be listed in a footnote at the bottom of the page.
Once you have all this information, you are ready to make your first request.
Making the API Request
The Pathable REST API is compatible with simple requests, like the below sample request.
curl --location --request GET 'https://api.pathable.co/v1/people/{id}/magicLink' \
--header 'Accept: application/json' \
--header 'X-API-KEY: {API Token}'
Please note! The blue portions, {id} and {API Token} are only placeholders.
- https://api.pathable.co/v1 should be the endpointin the footnote referenced above
- {id} is the "personId", a unique record identifier which represents the attendee
- {API Token} is the key you copied from the Admin Settings' API screen
Retrieving Each User's personId
The easiest way to retrieve user's personids is calling the /people/profiles endpoint.
Requesting the people/profiles endpoint will provide you with the "personId" for each attendee if you don't already have it via your data feed.
With that information, your requests' response should look something like this
"https://communityName.pathable.co/?authToken=wtK3yfhcJPThc7G2suF8cFc7Ys0H9ryXCKAowx93LHr&openNativeApp=true"
Please note! The response comes with quotation marks. The blue communityName will be replaced with your community's subdomain. The URL response should already be correct when you receive it.
Retrieve Each User's personId
The easiest way to retrieve user's personids is calling the /people/profiles endpoint.
Requesting the people/profiles endpoint will provide you with the "personId" for each attendee if you don't already have it via your data feed.