(*Not a very catchy title, but there's more to this topic than how to get a license!)
Tl;dr version: Use the Member/Profile API to check the status of an asset you want to purchase and your current quota, use Content/License to get a license, and download your asset. Also, use the LicenseHistory API to get a list of past purchases.
In the previous section, we covered how to hook up the Search API into your application. In this article, we'll cover the Adobe Stock Content and Member methods of the License API. These can get information about a user's licensing (entitlement) status, determine whether the user has an existing license for an asset, request a new license for an asset for that user, get a signed download URL for the asset, and get a history of past licensed assets.
Before you can purchase an asset using the API, there are a few tasks you will want to perform as part of your application flow, and this may trigger multiple decision points depending on your use case. Like a children's board game, the process is not difficult as long as you understand the rules.
To do any activity involving licensing, you will first need to generate an access token. This is covered in detail in Stock API Authentication and in the individual OAuth and Service Account workflow guides.
The user starts their journey by getting a file's Stock ID (also called "media ID" and "content ID") typically from a search. This was covered in the previous section, and is a key part of any Stock workflow.
Some important items to note:
- Stock IDs are not permanent/static. If you provide a checkout cart for your user, and the user saves the asset to license later, you should not assume that this asset is still available under that lD--you should verify. (See step #4, below.)
- Templates and 3D content are more likely to change IDs, because they are updated more often.
For example, your user wants to license an image of a cute, fluffy kitten (and who wouldn't?) This is an extract of the JSON response from the search request, showing the ID we will need for our next set of operations.
{
/*...*/
"id": 112670342,
"title": "Kitten on white blanket",
/*...*/
}
It's best practice to check if the item is licensed already. There are two methods for this:
- As part of the search. When you are performing the search in step #2, a convenience method is to add the
is_licensedfield, which will be set to the license name if that user or organization has licensed this asset.
The main difference between this search request and the ones discussed in the previous section is that this one must be authenticated with an access token. Note the headers used in this request are the same as the ones used for search, with the addition of the Authorization header. You will use these same headers for all remaining licensing requests.
curl "https://stock.adobe.io/Rest/Media/1/Search/Files?locale=en_US&search_parameters%5Bmedia_id%5D=62305369&result_columns%5B%5D=id&result_columns%5B%5D=is_licensed" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"Response:
{
"files": [
{
"id": 62305369,
"is_licensed": "Standard"
}
]
}- Using Content/Info. If you prefer an explicit method, you can call your first Licensing API request using Content/Info, which has the sole purpose of returning the current license state of an asset for that user (or for that org, if the user belongs to an enterprise).
Using this method, the API returns a contents object which contains the ID of the asset, and a sub-object purchase_details which lists the purchase state, license type and date.
curl "https://stock.adobe.io/Rest/Libraries/1/Content/Info?content_id=62305369&license=Standard" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"Response:
{
"contents": {
"62305369": {
"content_id": "62305369",
"size": "Comp",
"purchase_details": {
"state": "purchased",
"license": "Standard",
"date": "2017-11-01 22:57:48"
}
}
}
}In both cases, if the asset is licensed, then there is nothing else to do but get the URL and download the asset. Proceed to step #6.
Assuming the asset is not already licensed, then you will check to see if it's possible to license this asset. This is to prevent a bad user experience and error if you tried to license the item and it cannot be licensed.
For this step, you will use the Member/Profile API. In addition to checking if the asset can be licensed, this will return the user's quota and also return a localized message about how many credits the license will cost. Getting the quota is useful as you can show that the user has "X" number of credits in your application's UI.
For the query string, you will need to provide the Stock ID with the content_id parameter. Ideally, also provide the license type if it is known (because some assets can have multiple license types); for images the normal default is "Standard." Refer to the Licensing API reference for more details. Also, if you want a localized message, also provide the language code.
curl "https://stock.adobe.io/Rest/Libraries/1/Member/Profile?content_id=112670342&license=Standard&locale=en_US" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"Response:
{
"available_entitlement": {
"quota": 1,
"license_type_id": 42,
"has_credit_model": false,
"has_agency_model": true,
"is_cce": true,
"full_entitlement_quota": {
"standard_credits_quota": 1
}
},
"purchase_options": {
"state": "possible",
"requires_checkout": false,
"message": "This will use your last standard credit."
}
}In the example, you can see that the purchase_options.state is "possible," which tells you that licensing can continue. If it is not possible to license, go to Troubleshooting, below. Otherwise, continue to the next step.
Now you will perform the license purchase request using the Content/License API, which will deduct credits from the user or organizational account.
Use the same parameters and headers that you used in the Member/Profile request.
curl "https://stock.adobe.io/Rest/Libraries/1/Content/License?content_id=112670342&license=Standard" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"Response:
{
"available_entitlement": {
"quota": 0,
"license_type_id": 42,
"has_credit_model": false,
"has_agency_model": true,
"is_cce": true,
"full_entitlement_quota": {
"standard_credits_quota": 1
}
},
"contents": {
"112670342": {
"content_id": "112670342",
"size": "Comp",
"purchase_details": {
"state": "just_purchased",
"license": "Standard",
"date": "2017-11-06 02:54:18",
"url": "https://stock.adobe.com/Rest/Libraries/Download/112670342/1",
"content_type": "image/jpeg",
"width": 4256,
"height": 2832
}, /*...*/
}
}
}The response returns several fields, but the most important for your user is in the contents.XXXX.purchase_details object (where "XXXX" is the Stock ID). Here you will find the URL you will need to download the asset. In addition, if you want to update your UI, you can get the updated quota value from the response field available_entitlement.quota.
Finally, you can download the full asset. Here you will call directly to the URL of the licensed asset that you obtained in the previous step:
{
"contents": {
"112670342": {
"purchase_details": {
"url": "https://stock.adobe.com/Rest/Libraries/Download/112670342/1",
}
}
}
}Note that unlike the other requests, you do not include the Authorization header, because that can cause the request to fail. Instead, you pass the access token using the token parameter. The download also requires that your application has the ability to follow a redirect--make sure this option is enabled on your download client.
https://stock.adobe.com/Rest/Libraries/Download/112670342/1?token=AccessTokenHereResponse:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Disposition: attachment; filename="AdobeStock_112670342.jpeg";
Content-Length: 176164
Content-Type: image/jpeg
Date: Mon, 06 Nov 2017 03:18:50 GMTThe download URL provided by the Stock API is an alias that may redirect you to the actual location of the file on a cloud-based server. Therefore, your request must follow any redirect from the Stock API server, and output the result to a file.
Curl command line example (-L: Follow redirects)
curl -L -o AdobeStock_77438420.jpeg 'https://stock.adobe.com/Rest/Libraries/Download/77438420/1?token=<TOKEN>'PHP example:
$curl = curl_init($download_url);
curl_setopt($curl, CURLOPT_FILE, $fp); // output to file
curl_setopt($curl, CURLOPT_FOLLOWLOCATION, true); // follow redirects
curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1);
// add other options here as needed
$result = curl_exec($curl);
$fp = fopen($local_image_file, 'w+');
fwrite($fp, $result);
fclose($fp);This URL will trigger a download of the full asset. If you need a different size of the asset (for images only), you can use the size parameter. See Q&A, below.
Note that the token parameter does not include the word "Bearer" as it does when used as a header.
And you are done!
...assuming nothing went wrong. If it did, then continue reading. Also, check out common questions and answers about licensing assets.
Besides obtaining licenses for new assets (Content/License) or checking your credit quota (Member/Profile), another common use for the License API is to access your past history of purchases. This is done using the Member/LicenseHistory API. The format for this request is almost exactly the same as for other licensing methods, except that the result resembles a search request, even supporting pagination (if you have a lot of licensed assets).
In this example, license history is being requested for this account and the response is being limited to 1 file result (although 3 assets have been licensed), using the search_parameters[limit] query command.
curl "https://stock.adobe.io/Rest/Libraries/1/Member/LicenseHistory?search_parameters%5Blimit%5D=1" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"Result:
{
"nb_results": 3,
"files": [
{
"license": "Standard",
"license_date": "11/6/17, 2:54 AM",
"download_url": "https://stock.adobe.com/Download/DownloadFileDirectly/ikMRKBPqHDrtTifHkbbxGfKhIGVQPw6y",
"id": 112670342,
"title": "Kitten on white blanket",
"creator_name": "byrdyak",
"creator_id": 202614441,
"content_url": "https://stock.adobe.com/Rest/stock-photo/kitten-on-white-blanket/112670342",
"media_type_id": 1,
"vector_type": null,
"content_type": "image/jpeg",
"height": 2832,
"width": 4256,
"details_url": "https://stock.adobe.com/112670342?as_channel=affiliate&as_source=api&as_content=b4e3ee08719247cc85e9ba92970b1028"
}
]
}Notice that one of the fields returned is the download URL, making this a convenience method if you want your users to be able to re-download an asset they have previously licensed. Downloading the asset again does not trigger a new license request. Even though the format is slightly different, you would still use this download URL with a token=<access token> parameter.
https://stock.adobe.com/Download/DownloadFileDirectly/ikMRKBPqHDrtTifHkbbxGfKhIGVQPw6y?token=AccessTokenHereYou have completed the Adobe Stock API getting started guide.
- If you want more detail on anything you have read thus far, explore the API reference documentation.
- If you are ready to get started in earnest, browse our sample code and SDKs.
In most cases, everything should happen as outlined above. But if it doesn't, you need to know how to diagnose the issue and correct it.
In step #4 above, we used Member/Profile to check if licensing was possible. But what if it was not possible?
In that case, we would have seen a JSON response message like this:
"purchase_options": {
"state": "not_possible",
}If this happens, you can build some checks into your application.
First, check the type of asset you are licensing and compare that to what you are allowed to license. One of the most common situations is that you are trying to license a Premium or Video asset, which you might not be allowed to license under a standard image subscription. For a better understanding of asset types and how to license them, see the Adobe Stock plans page. Note that even if you plan only includes images, you may still be able to license the asset if Adobe has a payment instrument (such as a credit card) on file. In that case, the state will be "overage" instead of "not_possible."
You will see this message if the asset is Premium or Video, and your plan does not include this content:
{
"available_entitlement": null,
"member": {
"stock_id": 43289915
},
"purchase_options": {
"state": "not_possible",
"message": "You cannot license this type of asset with your standard credits quota. Please contact your administrator to upgrade your current plan."
}
}While the message above does not tell you what type of asset this is, you can get this from the search result you performed in step #2, above, if you request the content_type and premium_level_id response fields.
If the premium level is not 0 (standard), then it's possible your plan does not cover it.
{
"nb_results": 1,
"files": [
{
"id": 124287454,
"title": "Kitten Peeking Through Barn Doors; Steinbach, Manitoba, Canada",
"content_type": "image/jpeg",
"premium_level_id": 3
}
]
}Video assets could have a premium_level of 0, but simply because the content type is video (e.g., video/quicktime, video/mp4, etc.), realize that you must have credits to license it.
{
"nb_results": 1,
"files": [
{
"id": 121222021,
"title": "Christmas kitten meows",
"content_type": "video/quicktime",
"premium_level_id": 0
}
]
}
If you do not belong to an enterprise entitlement, the solution is easy: go to Adobe Stock plans and purchase a universal credit pack. You can still use your image credits for standard images, templates and 3D, and reserve your new credits for special assets.
If you do belong to an enterprise organization, you will need to contact your Adobe sales team for options.
The next most common scenario is that you don't have enough credits in your account. Situations where this may occur:
- All credits have been used up. This is indicated by a
available_entitlement.quotaproperty value of 0. - The asset you want to license requires more credits than you have. As mentioned above, Premium and Video assets cannot be licensed using standard image credits--they require universal credits, or an on-demand purchase separate from your subscription. Furthermore, the price per asset is greater than one credit. As seen on the Adobe Stock plans page, these assets could range from 2 credits up to 50 credits each.
In both cases, if purchase_options.requires_checkout is true but licensing is not possible, then you will need to take actions on your account to add more credits. This combination of values means that you cannot license at this time via the API, but may be able to if you correct the issue.
{
"available_entitlement": {
"quota": 0,
"full_entitlement_quota": {
"standard_credits_quota": 0
}
},
"purchase_options": {
"state": "not_possible",
"requires_checkout": true,
"message": "You don't have enough standard credits to license this asset. Please contact your administrator to add more standard credits to your account."
}
}
If you belong to an enterprise organization and you need more credits than you have available, you can simply add additional quota in your product license configuration (PLC). This is done by your account administrator, as described in the Service Account workflow guide, or documented here. Enterprise customers can add more quota than they have available, and those extra credits will be charged back at a later date.
One reason enterprises may want to intentionally limit their PLC is if each department is given a separate quota. A quota limit allows the administrator to force the department to request more quota if it goes over its limit.
Note that admins can only add more credits for the type of assets they have agreed to license, per their contract. For example, if a contract only has standard image credits, the administrator cannot add universal credits for Premium or Video assets. In this case, the Adobe sales team must be contacted.
You need credits to purchase licenses, whether those are standard image credits or universal credits. If you do not belong to an enterprise org, you can get a subscription or credit pack from Adobe Stock plans. Alternatively, if you keep a payment method on file (such as a credit card or PayPal account), it's possible that the API can automatically deduct the funds. In this case, the state in the Member/Profile response will be "overage."
Note that some assets (such as some Creative Cloud templates) are free, and do not require a subscription or credits as long as you are a non-enterprise user.
In the unlikely case where you do have credits and licensing is possible, then something else may be happening. Use the Postman or curl tools to verify that your application is not getting bad or stale data (for example, it is caching previous responses), and the Adobe Stock API is not returning a 400 error (see below).
If none of those things are happening, then contact Adobe Stock Support. Note that this support channel is for Stock customers. If you are a developer working on an application, contact the partner team for further direction.
In the previous cases, Member/Profile and the other APIs will return a valid 200 response. But in the cases below, you will get a 400 error. Here are a couple common reasons, but see more in the Stock API reference section.
You can get this error if you try to license an asset with a mismatched license type. For example, Images, 3D and Templates allow a "Standard" license, but Videos have valid licenses of "Video_HD" and "Video_4K." If you do not specify one of those values for a video, you will get this error.
{
"error": "The license \"Standard\" does not match type of content #121222021",
"code": "020",
"case": "pkx2JXqL7ePdNCXAewS2R7U0PvF27KND"
}As a best practice, your user should have to sign in for each session, or if you are using an enterprise application, it should request a new token. Access tokens have a 24-hour expiration, so unless you use a refresh token or unless your user told the Adobe sign-in screen to "remember me," it is expected that the token will expire after a fixed amount of time.
{
"error_code": "401013",
"message": "Oauth token is not valid"
}Yes, from the Member/Profile API. You can either call a specific ID and license type, or leave off those parameters.
Note that if you do include the content_id in your request and you have more than one type of credit (e.g., standard image credits and universal credits), the available_entitlement.quota value will reflect the credits available for that type of asset. For example, if you are querying about a video, then you will get back the number of credits available for Video and Premium content.
curl "https://stock.adobe.io/Rest/Libraries/1/Member/Profile?locale=en_US" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"Response:
{
"available_entitlement": {
"quota": 3,
"license_type_id": 16,
"has_credit_model": true,
"has_agency_model": false,
"is_cce": true,
"full_entitlement_quota": {
"credits_quota": 3
}
},
"member": {
"stock_id": 41003529
},
"purchase_options": {
"state": "possible",
"requires_checkout": false,
"message": "This will use 1 of your 3 credits."
}
}In general, if you are a member of an Adobe Enterprise customer you will realize this, however, if you are a partner using an OAuth integration, you may not know in advance what kind of user is signing in. For example, you may want to identify and target enterprise users differently than regular users.
This can also be done using the Member/Profile API. In the previous example, the property available_entitlement.is_cce will be true if the user has an enterprise Stock entitlement.
"is_cce": true,One thing to note is that Adobe Stock does not have enterprise "accounts" but rather enterprise "entitlements." The point is that a user may be signed in with a free Creative Cloud account, but still be assigned to an account which has enterprise Stock entitlements. That same user may also have a personal (non-enterprise) subscription to Creative Cloud applications. It is best to use the term "entitlement" rather than "account" when dealing with enterprises at Adobe.
When you license an image, you license the full/original size of the asset. However, there are times when you need a smaller size, for example to include in a social media post or email.
The Stock API has a command for this situation. Simply add a size= parameter to the download URL, and Adobe Stock will return the next larger size. The actual size returned depends on the original size of the asset; see the Licensing API reference for more details.
Example: You want a 400px image for your page.
https://stock.adobe.io/Rest/Libraries/Download/112670342/1?size=400&token=AccessTokenHereTwo things to note about this command:
- You cannot request any arbitrary size. Currently, the supported sizes are 400, 800, 1600, 2400, 3100, and 5000.
- If the asset doesn't have the requested size because the original was not high enough resolution, Stock API will return the max available size.
If you are an independent developer or student, you can follow the Affiliate workflow and sign up for an API key. If you want to also test licensing an asset, you can test it on a free asset like one of our great Creative Cloud Stock templates (not all templates are free, but many are).
However, if you are interested in partnering with Adobe Stock and have a legitimate reason for a demo account, contact us.
This is a special case for Print on Demand retailers, as described in the Service Account workflow. One of the requirements for print retailers in this use case is that they must license an asset for each application of the photo in a printable good. For example, if a customer purchases a key chain and a t-shirt of the same image, the retailer would make two license requests. Because the default behavior of Content/License is that a new license will not be used, applications in this use case must use a command to force Adobe Stock to issue a new license.
To notify Adobe Stock to license an asset again, use the license_again=true parameter.
curl "https://stock.adobe.io/Rest/Libraries/1/Content/License?content_id=112670342&license=Standard&license_again=true" \
-H "x-api-key: YourApiKeyHere" \
-H "x-product: MySampleApp/1.0" \
-H "authorization: Bearer AccessTokenHere"