Get embedded URL
Use this Tango endpoint to obtain the secure, temporary embedded reward URL after placing an order. You later use this URL to integrate Tango's landing page into your application, eliminating the need to send rewards via email, or open a separate browser window/tab. See Gift card experience to learn about his feature.
Endpoint
Not all UTIDs support embedded URL. Use the following endpoint to get an embedded URL for eligible rewards:
| Endpoint | Description |
|---|---|
GET {URI}/lineItems/{referenceLineItemID}/embeddedUrl | Returns the embedded URL for integration into your application. |
How does it work?
If a UTID supports embedded, you can:
- Use
GET {URI}/catalogsto list all UTIDs available in catalog. The UTIDs provideitemAttributewhich shows the delivery method. - Take the UTID with the embedded delivery method and place an order with
POST {URI}/orders. - After placing the order, the response payload returns a
referenceLineItemID. - Use that
referenceLineItemIDto call theGET {URI}/lineItems/{referenceLineItemID}/embeddedUrlendpoint to return a URL with a temporary token. - Embed the token in your software iFrame to load the reward experience into your application:
- The token expires after five minutes and is evaluated on page load.
- Once displayed, your recipient has eight hours to unlock the reward.
Note:This endpoint only works for items that return
credentialTypesofrewardSecurityUrlandrewardSecurityCode.
Parameters
The following path parameter can be used for this endpoint:
| Path parameter | Data type | Requirement | Description |
|---|---|---|---|
referenceLineItemId | string | required | Reference line item Id is returned in the line item response payload. |
Examples
Here's an example payload of a successful response:
{
"url": "https://sandbox.rewardcodes.com/r2/1/F4I45887987"
}Response codes
The possible response codes for this endpoint are as follows. For details, see i18nkey codes and their error messages:
| Response code | Meaning |
|---|---|
| 200 | The request was successful. |
| 400 | The server could not understand the request due to invalid syntax. |
| 500 | Something went wrong on the server, but the server cannot be more specific about what the exact problem is. |
Updated about 5 hours ago
