Getting Started

​ ​Welcome

Blitline Job

Job Response

Job Options

Functions

Polling and Postbacks

Gotchas

Development Recommendations

Service Limits

Examples List

List of Available Functions

Output Options

S3 Destination

IAM Users

S3 Signed Url

Azure Destination

FTP Destination

Other Service Signed Urls

CDN

Advanced

Metadata

Colorspace

Color Extraction

Static IPs

Signed Jobs

Formats

Pipelines

Image Optimization

Smart Image

PDF

Fonts

Subimage

Special (Non-Image) Processing

AWS Rekognition/Facial Recognition

Apache Tika

Vector Processing

Animated GIFs

Screenshots of Websites

IM Scripts

Video Keyframes

Zipping

​ ​Trancoding Video Presets

​ ​Video Transcoding

Azure Destination

Updated a month ago ​by Blitline Support

PUSHING TO YOUR AZURE STORAGE CONTAINER


In your Blitline job, you will need to add an “azure_destination”. This “azure_destination” needs to have the following children:

  • account_name (The name of your account)
  • shared_access_signature (Your signature giving Blitline permission to write your photo)

This signature MUST be the FULL url to the target resource, including the SAS.

For example:

  http://blitline.blob.core.windows.net/sample/image.jpg?sr=b&sv=2012-02-12&st=2013-04-12T03%3A18%3A30Z&se=2013-04-12T04%3A18%3A30Z&sp=w&sig=Bte2hkkbwTT2sqlkkKLop2asByrE0sIfeesOwj7jNA5o%3D

SHARED ACCESS SIGNATURE:

Tips for making SAS (Shared access signature)

  • You should make it of type sr=”b” (for Blob)
  • You only need to give “w”rite permission
  • Make sure it’s the whole url, we are simply going to “put” to that location with the file data.

EXAMPLE

Here is a full Blitline job example, including a sample “azure_destination”:

{
  "application_id": "YOUR_APP_ID",
  "src" : "http://www.google.com/logos/2011/houdini11-hp.jpg",
  "postback_url" : "YOUR_WEBSITE_URL",
  "functions" : [{
      "name": "blur",
      "save" : {
          "image_identifier" : "YOUR_IMAGE_IDENTIFIER",
          "azure_destination" : {
              "account_name" : "YOUR_AZURE_APP",
              "shared_access_signature" : "http://blitline.blob.core.windows.net/sample/image.jpg?sr=b&sv=2012-02-12&st=2013-04-12T03%3A18%3A30Z&se=2013-04-12T04%3A18%3A30Z&sp=w&sig=Bte2hkkbwTT2sqlkkKLop2asByrE0sIfeesOwj7jNA5o%3D"
          }
      }
    }]
}

IMPORTANT FILE TYPE INFORMATION:


Blitline uses file extensions to guess what file types are desired for output. Sometimes, though, these extensions do no exist or are not easier discernible from the SAS. To accommodate this, we have an additional modifier to the “azure_destination” that allows you to set the output filetype without using an extension.


By setting:

“force_type” : “pdf” (or jpg, png, webp, etc)

You can tell Blitline that it should save the file as this type before pushing to your destination.




How did we do?