Fetch Upload Credentials

This endpoint can be used to fetch the credentials needed to upload images to the Walgreens Storage server. Take note, when uploading to our storage, the files will not be accessible once uploaded and you should save image data if planning to use later in your checkout flow for previewing the images.

Endpoint URL

Sandbox:
https://services-qa.walgreens.com/api/photo/creds/v3
Production:
https://services.walgreens.com/api/photo/creds/v3

Endpoint Information

Request Body

Example Request

curl --request POST \ 
--url https://services-qa.walgreens.com/api/photo/creds/v3  \
--header 'Content-Type: application/json' \
--data '{ \
	"apiKey":"YOUR_API_KEY", \
        "affId":"YOUR_AFFILIATE_ID", \
        "platform":"ios", \
	"transaction":"photocheckoutv2", \ 
	"devInf":"DEVICE,##.#" \
	"appVer":"#.#", \
}' \
						

Example Response

{
    "uploadLimit": 200,
    "template": "default",
    "landingUrl": "https://m5.walgreens.com/photoprints/",
    "cloud": [{
        "sasKeyToken": "https://pstrgqp01.blob.core.windows.net/qpcontainerin?sig=
        BLAHBLAHBLAH&se=YYYY-MM-DDT22%3A53%3A57Z&sv=YYYY-MM-DD&sp=w&sr=c"
    }]
}
						

Generate Upload Token

Before an image can be uploaded, the value for the "sasKeyToken" (looks like a url) must be converted correctly into the "Upload_URL" . This is completed by doing the following:

Step by Step Guide

• A) Split the "sasKeyToken" value on the "?" character into a string array
• B) Create a string from the first element of the string array lets call it "blobContainerSplit"
• C) Create a string from the second element of the string array lets call it "signature"
• D) Create a string of the imageName, example: "Image-"+ YOUR_AFFILIATE_ID +"-"+ generateUUID() +".jpg" lets call it imageName
• E) Generate the "Upload_URL" like so: blobContainer +"/"+ imageName +"?"+ signature

Example Code

SWIFT:
let blobContainer:String = sasToken.components(separatedBy: "?").first!
let signature:String = sasToken.components(separatedBy: "?").last!
let imageName:String = "Image-\(affId)-\(UUID().uuidString).jpg"
let Upload_URL:String = "\(blobContainer)/\(imageName)?\(signature)"

KOTLIN:
var blobContainer:String = sasToken.split("?").toTypedArray().first()
var signature:String = sasToken.split("?").toTypedArray().last()
var imageName:String = Image-".plus(affId).plus("-").plus(UUID.randomUUID().toString()).plus(".jpg")
var Upload_URL:String = blobContainer.plus("/").plus(imageName).plus("?").plus(signature)

JAVASCRIPT:
function generateUUID() 
{
return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function(c)
{
var r = Math.random() * 16 | 0, v = c == 'x' ? r : (r & 0x3 | 0x8);
return v.toString(16);
});
}
var blobContainer = sasToken.split("?").shift();
var signature = sasToken.split("?").pop();
var imageName = "Image-"+affId+"-"+generateUUID()+".jpg";
var Upload_URL = blobContainer+"/"+imageName+"?"+signature;
		
                    

Example Response

https://pstrgqp01.blob.core.windows.net/qpcontainerin/
Image-YOUR_AFFILIATE_ID-a12b3cd-e4f5-6789-ghi0-1234567j89kl.jpg?
sig=BLAHBLAHBLAH&se=YYYY-MM-DDT22%3A53%3A57Z&sv=YYYY-MM-DD&sp=w&sr=c
					

Upload Images

To upload an image, make a PUT request to the generated "UPLOAD_URL" with the custom HTTP headers. Place the image data to be uploaded in the HTTP body. If multiple images are to be printed, repeat the process above for every single image.

Endpoint URL

The image url is generated using the process above.

Endpoint Information

Request Headers

Request Body

The binary data of the image file.

Example Request

curl -X PUT \
'https://pstrgqp01.blob.core.windows.net/qpcontainerin/Image-YOUR_AFFILIATE_ID-a12b3cd-e4f5-6789-ghi0-1234567j89kl.jpg?sig=BLAHBLAHBLAH&se=YYYY-MM-DDT22%3A53%3A57Z&sv=YYYY-MM-DD&sp=w&sr=c' \
-H 'Content-Length: 1073741824' \
-H 'Content-Type: image/jpeg' \
-H 'x-ms-blob-type: BlockBlob' \
-H 'x-ms-client-request-id: a12b3cd-e4f5-6789-ghi0-1234567' --upload-file image.jpeg
						

Example Response

HTTP STATUS CODE: 201
                        
						

Custom Upload Images

You are absolutely able to use your own url for images uploaded to another server then the Walgreens server. Please ensure the url is accessible for at least 36 hours (due to delays at store level) with a simple HTTP Get Request and that as that is how our image downloader will get the file to the store.

The landing URL can be obtained from the findURL web service, this url allows the customer to do the Photo Print Checkout.

Endpoint URL

Sandbox:
https://services-qa.walgreens.com/api/util/v3.0/mweb5url
Production:
https://services.walgreens.com/api/util/v3.0/mweb5url

Example Request

curl --request POST \ 
--url https://services-qa.walgreens.com/api/photo/creds/v3  \
--header 'Content-Type: application/json' \
--data '{ \
    "apiKey": "YOUR API KEY",
    "affId": "YOUR AFFILIATE ID",
    "productGroupId": "PRODUCT GROUP ID",
    "publisherId": "YOUR PUBLISHER ID",
    "channelInfo": "CHANNEL INFO: web or ''",
    "callBackLink": "IF CHANNEL INFO IS web: YOUR CALLBACK URL",
    "expiryTime": "IMAGE EXPIRATION TIME",
    "images": [
        "URL1",
        "URL2",
        "URL3",
        "etc..."
    ],
    "lat": "CUSTOMER LATITUDE",
    "lng": "CUSTOMER LONGITUDE",
    "customer": {
        "firstName": "CUSTOMER FIRST NAME",
        "lastName": "CUSTOMER LAST NAME",
        "email": "CUSTOMER EMAIL ADDRESS",
        "phone": "CUSTOMER PHONE NUMBER"
    },
    "transaction": "photoCheckoutv2",
    "act": "mweb5UrlV2",
    "view": "mweb5UrlV2JSON",
    "devinf": "THE DEVICE INFO",
    "appver": "THE APP VERSION",
    "affNotes": "TRACKING ID / NOTES"
}' \
						

Example Response

{
    "landingUrl": "CHECKOUT_LANDING_URL",
    "template": "TEMPLATE_FOR_CUSTOM_TEMPLATES",
    "uploadLimit": "UPLOAD_LIMIT_FOR_YOUR_ACCOUNT",
    "token": "ACCESS_TOKEN_FOR_CHECKOUT",
    "err": "ERROR_CODE_NUMBER"
}
					

Open the LandingURL:

Once a LandingURL has been obtained, the URL should be loaded in a WebView/Browser Window.

To properly open the URL you must append the value of "token" to queryString of the "landingUrl".

Example Response

{GET:landingUrl+"&token="+token}
                    

Handling Callbacks:

Once the user has loaded the checkout page there are some button interactions that must be handled by the callback URL passed in generating the checkout:

Possible Callback Scenarios:

• When the user taps the "Cancel" button on the landing page
• When the user taps the "Back" button on the landing page
• When the user taps the "Done" button on the landing page