Signup URL Redirect
Buyers Signup URL on Marketplaces goes to Suger first, then redirect to your service Signup URL.
Overview
When the buyers purchased your product in one marketplace (AWS, Azure or GCP
), they would get a link to set up or register the account on your service website. The link will be directed to the Suger endpoint, after decoding and processing, it will be redirected to your service signup URL.
How it works
-
You provide
Suger
with your product signup URL, for example,https://your-service-signup-url
. -
When a buyer purchased your service in the marketplace, they get a link sent to Suger endpoint
https://api.suger.cloud/public/signup/{partner}/orgId/{orgId}?partnerId={partnerId}
, where thepartner
can beaws
,azure
orgcp
, theorgId
is your SugerOrganization
ID and thepartnerId
is your SugerIntegration
partner ID. -
Suger will take care of several interactions (including decode token, register entitlement & buyer info, etc.) and will resolve to a
Suger Entitlement
ID. -
Suger redirects the buyer to your signup URL with several query parameters
https://your-service-signup-url?sugerEntitlementId=entitlement-id&partner={partner}&offerType={offerType}
, as defined below:Query Parameter Name Definition sugerEntitlementId
The ID of this Entitlement in the Suger partner
The cloud partner where this Entitlement comes from, such as aws
,azure
orgcp
(all lowercase)offerType
The type of the Offer on which this Entitlement is based , such as DEFAULT
for the default/public offer in the cloud marketplace. The possible values includeUNKNOWN
,AMI
,CONTAINER
,CONTRACT
,CPPO_OUT
,CPPO_IN
,CPPO
,CUD
,DEFAULT
,FIXED_FEE
,FIXED_FEE_WITH_OVERAGE
,FLAT_RATE
,FREE_TRIAL
,PAYG
,PAYG_WITH_CUD
,PER_USER
,PRIVATE
,PROFESSIONAL_SERVICES
andSUBSCRIPTION
-
Your service need to collect the
sugerEntitlementId
, and save it with the buyer's account. The ID can be used to fetch detailedEntitlement
&Buyer
info from the Suger API doc, and meter usage records as well.
- For AWS Marketplace, there can be a delay of up to 5 minutes to send the marketplace event to notify Suger the new purchase. So when buyers set up the account immediately right after the purchase, Suger know the product & buyer info, but may not know which offer is purchased.
- To bring better experiences, Suger creates new Entitlement with the default offer, and redirect the signup URL with the Entitlement ID. Once the marketplace event is received, the entitlement will be updated with the right Offer info. You webhook will receive the Entitlement Update event.
- Your service is responsible to fetch the latest Entitlement info. The entitlement ID & Status are not changed in this scenario.
FAQ
-
Could you clarify whether you guys build the sign-up form or we do?
Our platform handles the creation of the client sign-up form for Marketplace. You can provide some basic details, such as the Company Name and Logo, and we'll create the registration form automatically.
-
How do I update my new user signup page?
You can update it by navigating to Suger > Settings > New Client Sign Up.
-
When exactly do the clients see the sign-up page in the purchase process?
After they complete the purchase, they are immediately redirected to the sign-up page.
-
What is the meaning of the CC emails field? Emails that will be CC'd on the email to the client?
Yes
-
Is the email sent after they leave their details on this page?
Yes, after the customer completes the form, we send them a confirmation.
-
Does 'Public Notes' appear on the page?
That's correct, you can add any additional note you want on the page.
-
What is the integration of our solution going to look like? What are the requirements?
What needs to be done is to connect your product registration page to Suger's Webhook, here: https://www.suger.io/docs/get-started/webhook Once you have connected it, you can update the FullFilment URL of your AWS Product to your SaaS Registration page through Suger: Signup URL Redirect | Suger