The following email template can be used to share details with exhibitors regarding the Developer Kit. It is intended as a starting point and should be customized to fit the details, tone, and requirements of your event.
NOTE
The suggested sales cutoff is three (3) weeks prior to the event start date, and the suggested testing deadline is two (2) weeks prior. These timelines are recommended to help reduce last-minute support needs and potential onsite issues. However, there is no technical restriction preventing sales after these dates—as long as the exhibitor’s developer can fully implement and test the API before the event begins. All implementation and testing is the sole responsibility of the exhibitor’s developer.
Subject:
Developer Kit Instructions for {{EventName}}
Email Body:
Hi {{FirstName}},
Thank you for supporting {{EventName}} in {{EventLocation}} on {{EventDates}}. We are excited to partner with Cadmium event technology to offer the Eventscribe Developer Kit API for this event — please review the Developer Kit API Overview for details prior to purchasing.
To access the Lead Capture Portal, use your unique login URL for {{CompanyName}} – Booth {{BoothNumber}}: {{ExhibitorLoginURL}}
*If your organization has more than one booth, each will have a unique URL.
Log in to the Lead Capture Portal to:
- Purchase the Developer Kit (by [add date])
- Download your receipt
- Copy your booth's API Key, API documentation, and test account information to send to your developer
Reference the Developer Kit Guide for a checklist and instructions.
By [add deadline], ensure your third-party developer has configured and tested the connection to the API. Once confirmed, please reply to this email to notify us that this is complete.
If you have any questions, don't hesitate to reach out.
Regards,
[add signature]
Terms & Conditions
By using Eventscribe Lead Capture, you agree to Cadmium’s Privacy Policy and Terms & Conditions.
[add custom terms and policies]
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article