As a developer, you can structure a Showpad sharing URL so that it can kickstart the Showpad iOS or Web app, and prefill elements of an email share or link share. This tutorial gives you the information you need to kick-start Showpad from other iOS or Web apps and pre-fill an email share for sellers, creating a smooth and productive experience from one app to another. Imagine a sales rep at a tradeshow scans a prospect's business card using your lead capturing scanner on their iPad. Now they can select the "Share Showpad Content" button you've developed, and the Showpad app will be open with an email share, subject line, content, and recipient already filled in. This makes it easy for sellers to do some final edits and send a share at the touch of a button.
You need this to succeed
- All passed elements must be URL encoded
- Administrator access to a Showpad's Online Platform if asset ID's are needed
- Showpad Ultimate Package
- A third-party app you wish to direct users to Showpad from
See how it works
Simply write in the subject you wish to include.
Add recipients who will receive the email share.
Adding content happens using the asset slugs. For multiple assets, use a comma-separated list of slugs. This is also the format that should be used in ShowpadJS. Content will be added to the end of the email body, the same as it appears when selecting content from within the content picker inside an email share.
Asset slugs can be found in the content library. Navigate to the particular asset, then click to open the asset detail panel. In the Info tab, copy the App Link. Read more about locating asset links or slugs here.
The combined parameters
On iOS URLs can have a length of INT_MAX and are limited to that due to compatibility with 32 bit.
The action parameter is required to trigger the share, but all other elements are optional.
Query parameters are as follows:
- action => String : email or link
- recipients => Array of json objects with following properties: Email: string, FirstName: Optional String, LastName: Optional string
- subject=> String
- attachments => Array of slugs
- body => String