Version 1.0
Connector Overview: This page documents all 129 actions for the Bynderconnector v1.0.
Access rights (3)
POST Create metaproperty access
/api/content_access/metaproperties/{metaproperty_id}/
These API calls allow you to set up visibility restrictions on metaproperties
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The unique identifier of the metaproperty to set access rights for. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
Field to fetch specific permissions |
DELETE Delete metaproperty access
/api/content_access/metaproperties/{metaproperty_id}/
These API calls allow you to set up visibility restrictions on metaproperties
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The unique identifier of the metaproperty whose access rights should be removed. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperty access
/api/content_access/metaproperties/{metaproperty_id}/
These API calls allow you to set up visibility restrictions on metaproperties
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The unique identifier of the metaproperty whose access rights are requested. |
|
|
The response format expected from the API (e.g. application/json). |
Account (2)
GET Retrieve account information
/api/v4/account/
Retrieve information about the current account, such as account name, plan, and settings.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve derivatives
/api/v4/account/derivatives/
A derivative is a file that is based on another source, for example, a low-resolution representation of a print-quality photo. During the upload process, Bynder can automatically create pre-defined image derivatives with different dimensions, quality, and format. Bynder can either maintain the original aspect ratio of an image, or crop or pad an image to fit the specified dimensions. We can create smaller versions of your original image asset in both a JPG and PNG file extension. However, the resolution of derivatives can't be larger than the original file.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Analytics (18)
GET Asset Activity
/v7/analytics/api/v1/asset/{assetId}/
This endpoint will allow you to retrieve all the events performed in a given asset
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve events performed in a given asset ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Activity CSV
/v7/analytics/api/v1/asset/{assetId}.csv
This endpoint will allow you to retrieve all the events performed in a given asset
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve events performed in a given asset ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Archive
/v7/analytics/api/v1/asset/archive
Retrieve analytics data for asset archive events in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve archive events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Archive CSV
/v7/analytics/api/v1/asset/archive.csv
Retrieve analytics data for asset archive events in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve archive events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Create
/v7/analytics/api/v1/asset/create
Retrieve analytics data for asset create events in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve create events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Create CSV
/v7/analytics/api/v1/asset/create.csv
Retrieve analytics data for asset create events in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve create events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Download
/v7/analytics/api/v1/asset/download
Retrieve analytics data for asset download events in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve download events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Download CSV
/v7/analytics/api/v1/asset/download.csv
Retrieve analytics data for asset download events in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve download events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Remove
/v7/analytics/api/v1/asset/remove
Retrieve analytics data for asset remove events in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve remove events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset Remove CSV
/v7/analytics/api/v1/asset/remove.csv
Retrieve analytics data for asset remove events in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve remove events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset View
/v7/analytics/api/v1/asset/view
Retrieve analytics data for asset view events in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve view events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Asset View CSV
/v7/analytics/api/v1/asset/view.csv
Retrieve analytics data for asset view events in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve view events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Search Keyword
/v7/analytics/api/v1/search/keyword
Retrieve analytics data for search keyword usage in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve keyword events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET Search Keyword CSV
/v7/analytics/api/v1/search/keyword.csv
Retrieve analytics data for search keyword usage in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve keyword events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET User Activity
/v7/analytics/api/v1/user/{userId}/
This endpoint will allow you to retrieve all the events triggered by a given user
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
User id. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve events triggered by a user ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET User Activity CSV
/v7/analytics/api/v1/user/{userId}.csv
This endpoint will allow you to retrieve all the events triggered by a given user
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
User id. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve events triggered by a user ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET User Login
/v7/analytics/api/v1/user/login
Retrieve analytics data for user login events in JSON format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve login events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
GET User Login CSV
/v7/analytics/api/v1/user/login.csv
Retrieve analytics data for user login events in CSV format.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The maximum number of analytics events to retrieve. Allowed values are between 1 and 10000. |
|
|
The position in the dataset for the first event retrieved. To be used for pagination purposes. |
|
|
Retrieve login events ocurred after this date. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
Set a date range together with the "fromDateTime" parameter. ISO8601 format: yyyy-mm-ddThh:mm[:ssZ] with optional seconds. |
|
|
The response format expected from the API (e.g. application/json). |
Asset usage (4)
POST Create asset usage
/api/media/usage
These calls allow you to keep track of assets being exported from Bynder and imported into a third party application.
In order to get started or find an existing integration id you should check out this Bynder support article.
If you want to register a new third party application please contact us at support@bynder.com.
Warning: Requires the STATISTICS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The identifier of the asset whose usage is being recorded. |
|
|
The identifier of the integration that is using the asset. |
|
|
The URI where the asset is being used. |
|
|
The response format expected from the API (e.g. application/json). |
Options (5)
|
Option Name |
Description |
|---|---|
|
|
Integration id. |
|
|
Asset id. |
|
|
Datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Location. |
|
|
Additional information. |
DELETE Delete asset usage
/api/media/usage
These calls allow you to keep track of assets being exported from Bynder and imported into a third party application.
In order to get started or find an existing integration id you should check out this Bynder support article.
If you want to register a new third party application please contact us at support@bynder.com.
Warning: Requires the STATISTICS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Integration id. |
|
|
Asset id. |
|
|
Asset location. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve asset usage
/api/media/usage
These calls allow you to keep track of assets being exported from Bynder and imported into a third party application.
In order to get started or find an existing integration id you should check out this Bynder support article.
If you want to register a new third party application please contact us at support@bynder.com.
Warning: Requires the STATISTICS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
Integration id. |
|
|
URI. |
|
|
The response format expected from the API (e.g. application/json). |
POST Sync asset usage
/api/media/usage/sync
This alternative API call allows you to sync all your usage from a single integration.
Warning: Requires the STATISTICS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
Integration id. |
|
|
An array of URIs that are part of your integration. These are used to determine if usage should be created, updated or deleted. This list is not stored individually. |
|
|
A list of usage objects to be synced with the system. |
Assets (6)
POST Add metaproperty options
/api/media/options/
These calls allow you to change the metaproperty options attached to an asset.
Warning: Requires VIEW and EDIT access to the asset.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
Id of the asset. |
|
|
Id of the metaproperty from which you want to add options. |
|
|
List of metaproperty option ids you want to add to the asset. |
DELETE Delete asset
/api/v4/media/{id}/
Warning: Requires the MEDIAREMOVE security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
Whether to also delete all versions of the asset (set to 'true' or 'false'). |
|
|
Whether to also delete related statistics data (set to 'true' or 'false'). |
|
|
The response format expected from the API (e.g. application/json). |
DELETE Delete metaproperty options
/api/media/options/
These calls allow you to change the metaproperty options attached to an asset.
Warning: Requires VIEW and EDIT access to the asset.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
POST Modify asset
/api/v4/media/{id}/
Warning: Requires the MEDIAEDIT security role. Requires the MARKPUBLIC security role in order to change a asset's isPublic state.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
Whether to include version data in the modification (set to 'true' or 'false'). |
|
|
Whether to include statistics data in the modification (set to 'true' or 'false'). |
|
|
The response format expected from the API (e.g. application/json). |
Options (13)
|
Option Name |
Description |
|---|---|
|
|
Name of the asset, beware the asset will have no name when this is empty. |
|
|
Asset description. |
|
|
Copyright information of the asset. |
|
|
Id of the brand to save the asset to, can be retrieved using the Retrieve brands and subbrands call. |
|
|
Comma-separated tags. Tags will be appended to current tags list. If the tag doesn't exist it will be created. |
|
|
Dictionary with (metaproperty) options to set on the asset. Send fields as metaproperty.METAPROPERY_ID with a string of all its (metaproperty) options comma-separated. Note that the list of (metaproperty) options should include all the (metaproperty) options available in the lower hierarchy; meaning it should include the (metaproperty) options of the (metaproperty) options etc. |
|
|
Publication datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Indicating the archived state of the asset. |
|
|
Archive datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Indicating the limit state of the asset. |
|
|
Limit datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Watermark datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Indicating the public state of the asset. Warning irreversible, once changed to true it cannot be changed back. |
GET Retrieve assets
/api/v4/media/
Note: original is only returned for assets marked as public and requires the account to have the seoBaseUrl setting configured.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Brand id, can be retrieved using the Retrieve brands and subbrands call. |
|
|
Sub-brand id, can be retrieved using the Retrieve brands and subbrands call. |
|
|
Category id, can be retrieved using the Retrieve categories call. |
|
|
Collection id, can be retrieved using the Retrieve collections call. |
|
|
Asset id, will return the asset for that id. |
|
|
Comma-separated list of asset ids. Will return a asset for each existing id. |
|
|
Comma-separated list of (metaproperty) option ids, can be retrieved using the Retrieve metaproperties call. This parameter searches for assets that contain at least one of the metaproperty options passed in the list. |
|
|
Comma-separated list of tags, can be retrieved using the Retrieve tags call. |
|
|
Comma-separated list of asset types. |
|
|
Comma-separated list of asset orientation. |
|
|
Metaproperty option name.OR Comma-separated list ids of metaproperty options for that metaproperty.Note: NAME should be replaced by the Metaproperty name. |
|
|
Indicates whether or not the response should only contain assets marked as "limited usage". When 0, no filtering happens. |
|
|
Indicates whether or not the response should only contain archived assets. When 0, no filtering happens. |
|
|
Indicates whether or not the response should only contain assets marked as public. |
|
|
Search on filenames, tags, extensions, collection names, guidelines, brandstore, campaigns in workflow, enriched PDFs, word documents. The default order of results is relevance, but can be overriden with the order parameter. |
|
|
Retrieve assets created after this date.ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Set a date range together with the "dateCreated" parameter.ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Retrieve assets created on this specific date.ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Retrieve assets modified after this date.ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Set a date range together with the "dateModified" parameter.ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Retrieve assets modified on this specific date.ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
Order of the returned list of assets. |
|
|
Maximum number of results.Maximum: 1000. |
|
|
Offset page for results: return the N-th set of limit-results. |
|
|
Indicating whether or not the response should include count results. This parameter when passed as 1 overrides the total parameter. |
|
|
Indicating whether or not the response should include the total count of results. |
|
|
Indicating whether or not the response should include all the different media items (derivatives) available for each asset. |
|
|
Indicating whether or not the response should include the active version number. |
|
|
cursorMark returned in the X-Bynder-NextCursor response header which allows to return the next set of results.Note: This parameter can only be used if solr-cursor account feature is enabled. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific asset
/api/v4/media/{id}/
Warning: Requires the STATISTICS security role in order to retrieve views and downloads statistics data in the response, using the stats parameter.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
Include information about the different asset media items including versions. |
|
|
Include information about views and downloads. |
|
|
The response format expected from the API (e.g. application/json). |
Brands
GET Retrieve brands
/api/v4/brands/
Retrieve a list of all brands available in the account.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Brandstore (7)
POST Modify order
/api/store/order/{id}/
Warning: Requires the brandstore.orderadmin.edit security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Order id. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
New status of the order. |
|
|
Message |
|
|
Link to trackingnumber |
PATCH Modify orderline
/api/store/orderproducts/{id}
Warning: Requires the brandstore.orderadmin.edit security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Orderline id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve orders
/api/store/order/
Warning: Requires the brandstore.orderadmin.view security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Offset page for results: return the N-th set of limit-results. Limit is currently hardcoded to 10. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific order by id
/api/store/order/{id}/products
Warning: Requires the brandstore.orderadmin.edit security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Order id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific order by number
/api/store/order/{orderNumber}/products
Warning: Requires the brandstore.orderadmin.edit security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The order number without the country code (NA13334). |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific order info
/api/store/order/{id}/
Warning: Requires the brandstore.orderadmin.view security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Order id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific orderline
/api/store/orderproducts/{id}
Warning: Requires the brandstore.orderadmin.view security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Orderline id. |
|
|
The response format expected from the API (e.g. application/json). |
Collections (9)
POST Add assets to a collection
/api/v4/collections/{id}/media/
Warning: Requires the COLLECTIONS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id. |
|
|
A comma-separated list of asset IDs to remove from the collection before adding new ones. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
JSON-serialised list of asset ids to add. |
POST Create collection
/api/v4/collections/
Warning: To retrieve public collections the collection.public.view security role is required.
Warning: To retrieve collections other users shared/received the INBOXPUBLIC or OUTBOXPUBLIC security role is required.
Warning: To retrieve collections other users created the PUBLICCOLLECTIONS security role is required.Warning: Requires the COLLECTIONS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Limit the number of results returned. |
|
|
Specify the page number of results to retrieve. |
|
|
Define the order in which results are sorted. |
|
|
Provide a comma-separated list of collection IDs to filter. |
|
|
Include the total count of items in the response. |
|
|
Search collections by keyword. |
|
|
Filter collections by public status (true or false). |
|
|
Filter collections with a minimum number of assets. |
|
|
The response format expected from the API (e.g. application/json). |
Options (2)
|
Option Name |
Description |
|---|---|
|
|
Collection name. |
|
|
Collection description. |
DELETE Delete collection
/api/v4/collections/{id}/
Permanently delete a specific collection by its ID.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id to be deleted. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
POST Modify collection
/api/v4/collections/{id}/
Warning: Requires the COLLECTIONS security role. Requires the PUBLISHCOLLECTIONS security role in order to change a collection's isPublic state.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
Collection name. |
|
|
Collection description. |
|
|
Public state of the collection. |
DELETE Remove assets from a collection
/api/v4/collections/{id}/media/
Warning: Requires the COLLECTIONS security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id. |
|
|
Comma-separated asset ids to remove from the collection. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve collections
/api/v4/collections/
Warning: To retrieve public collections the collection.public.view security role is required.
Warning: To retrieve collections other users shared/received the INBOXPUBLIC or OUTBOXPUBLIC security role is required.
Warning: To retrieve collections other users created the PUBLICCOLLECTIONS security role is required.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Maximum number of results.Maximum: 1000. |
|
|
Offset page for results: return the N-th set of limit-results. |
|
|
Desired order of returned collection set. |
|
|
Comma-separated list of collection ids. Will return the collection for each existing collection. |
|
|
Indicates whether or not the response should include count results. |
|
|
Search on matching names. |
|
|
Indicates whether or not the return should only contain collections marked as public. When left unspecified, no filtering happens. |
|
|
Minimum amount of assets that the returned collections should have. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific collection
/api/v4/collections/{id}/
Retrieve details of a specific collection by its ID.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve the assets of a specific collection
/api/v4/collections/{id}/media/
Retrieve the assets associated with a specific collection.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id. |
|
|
A comma-separated list of asset IDs to remove from the collection before adding new ones. |
|
|
The response format expected from the API (e.g. application/json). |
POST Share collection
/api/v4/collections/{id}/share/
Warning: Requires the SHARECOLLECTION or SHARING security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Collection id. |
|
|
The response format expected from the API (e.g. application/json). |
Options (9)
|
Option Name |
Description |
|---|---|
|
|
Comma-separated email addresses of recipients. Mandatory if groups or profiles are empty. |
|
|
Comma-separated list of group ids. Mandatory if recipients or profiles are empty. |
|
|
Comma-separated list of profile ids. Mandatory if recipients or groups are empty. |
|
|
Recipient rights. |
|
|
Should recipients login to view the collection. Mandatory if collectionOptions is edit. |
|
|
Start date of the share. |
|
|
End date of the share. |
|
|
Wether the recipients should be notified using an e-mail. |
|
|
If sendMail is set to true, this is an optional message to be added for the recipient(s). |
Download (3)
GET Retrieve asset download location
/api/v4/media/{id}/download/
Warning: Requires the MEDIAHIGHRES security role.
Warning: Requires the ARCHIVEDOWNLOAD security role if the asset in question is archived.
Warning: Requires the DOWNLOADWATERMARK security role if the asset in question is watermarked.
Warning: Requires the KEYVISUALSDOWNLOAD security role if the asset in question is marked as limited usage.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
Type of files to download. Note that when multiple additional files are available only the download url of the latest one will be returned. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve asset version download location
/api/v4/media/{id}/{version}/download/
Get the download URL for a specific version of an asset.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id. |
|
|
Asset version to download. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific asset item download location
/api/v4/media/{id}/download/{itemId}/
Get the download URL for a specific item within an asset.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the asset you’d like to download a item of. |
|
|
The id of the specific asset item you’d like to download. |
|
|
Indicates whether or not to treat the itemId as a hashed item id. |
|
|
The response format expected from the API (e.g. application/json). |
Dynamic Asset Transformations
GET Generate dynamic asset transformation
/transform/{id}/{name}
Generate a derivative on the fly with a transformation (such as cropping, scaling, filling) applied to it.
More information about this feature can be found in our Knowledge Base item.
Image operations can be passed as io parameters in the form of transform:{operation},{param1}:{value1},{param2}:{value2},....
It's possible to specify several operations: ?io={operation1}&io={operation2}&.... The operations will be applied in the same order they are passed in the url.
These are the possible image operations and their parameters:
|
Operation |
Parameter |
Possible values |
|---|---|---|
|
|
color |
color name (yellow, black, etc.) or hexadecimal (rgb, rrggbb) |
|
|
width |
integer |
|
|
height |
integer |
|
|
x |
integer |
|
|
y |
integer |
|
|
gravity |
topleft / top / topright / left / center / right / bottomleft / bottom / bottomright |
|
|
shape |
circle / square |
|
|
blur |
integer |
|
|
background |
color name (yellow, black, etc.) or hexadecimal (rgb, rrggbb) |
|
|
width |
integer |
|
|
height |
integer |
|
|
background |
color name (yellow, black, etc.) or hexadecimal (rgb, rrggbb) |
|
|
width |
integer |
|
|
height |
integer |
|
|
gravity |
topleft / top / topright / left / center / right / bottomleft / bottom / bottomright |
|
|
aspectratio |
{integer}x{integer} |
|
|
width |
integer |
|
|
height |
integer |
|
|
(no parameters) |
|
|
|
(no parameters) |
|
|
|
angle |
integer between 0 and 360 |
|
|
background |
color name (yellow, black, etc.) or hexadecimal (rgb, rrggbb) |
|
|
width |
integer |
|
|
height |
integer |
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The operation(s) performed on the image before it's served to the client. It's possible to specify this parameter several times to have several operations applied. |
|
|
Focus point as a x,y coordinate (with values between 0 - 1). This will serve as the center point for the image operations. |
|
|
Format of the served image. This can either be jpg or png and it will overwrite the default webP. |
|
|
Image quality, ranging from 1 - 100 (has no effect when format is set to 'png'). |
|
|
The ID of the asset to transform. |
|
|
The name of the transformation to apply. |
|
|
The response format expected from the API (e.g. application/json). |
Groups
GET Retrieve groups
/api/groups/list/
Warning: Requires the GROUPMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Search on matching group names. |
|
|
What page of results to return. |
|
|
Maximum results to return. If limit is not provided the first 20 resulsts will be returned. |
|
|
Order of the returned list of groups. |
|
|
The response format expected from the API (e.g. application/json). |
Metaproperties (13)
POST Create dependency
/api/v4/metaproperties/{id}/dependencies/{dependencyId}/
Warning: Specific metaproperty dependency operations require the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty to which you’d like to add a dependency. |
|
|
Id of the (Metaproperty) option you'd like to become a dependency. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
POST Create metaproperty
/api/v4/metaproperties/
Warning: Requires the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Include the total count of metaproperties in the response. |
|
|
Specify the metaproperty type (e.g., text, date). |
|
|
Provide options for the metaproperty. |
|
|
Filter by metaproperty IDs. |
|
|
The response format expected from the API (e.g. application/json). |
POST Create metaproperty option
/api/v4/metaproperties/{id}/options/
Warning: Requires the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty to which you’d like to add a option. |
|
|
The response format expected from the API (e.g. application/json). |
DELETE Delete dependency
/api/v4/metaproperties/{id}/dependencies/{dependencyId}/
Warning: Specific metaproperty dependency operations require the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty from which you’d like to delete a dependency. |
|
|
Id of the (Metaproperty) option you'd like to no longer be a dependency. |
|
|
The response format expected from the API (e.g. application/json). |
DELETE Delete metaproperty
/api/v4/metaproperties/{id}/
Warning: Requires the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
Include additional data in the response. |
|
|
Include the total count of metaproperties. |
|
|
Specify the type of metaproperty to delete. |
|
|
Provide options for the deletion. |
|
|
The response format expected from the API (e.g. application/json). |
DELETE Delete metaproperty option
/api/v4/metaproperties/{id}/options/{optionId}/
Warning: Specific metaproperty option operations require the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option which you’d like to delete. |
|
|
The response format expected from the API (e.g. application/json). |
POST Modify metaproperty
/api/v4/metaproperties/{id}/
Warning: Requires the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
Include additional data in the response. |
|
|
Include the total count of metaproperties. |
|
|
Specify the type of metaproperty to modify. |
|
|
Provide options for the metaproperty. |
|
|
The response format expected from the API (e.g. application/json). |
POST Modify metaproperty option
/api/v4/metaproperties/{id}/options/{optionId}/
Warning: Specific metaproperty option operations require the METAPROPERTYMANAGEMENT or METAMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option which you’d like to modify. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperties
/api/v4/metaproperties/
Retrieve a list of all metaproperties.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Indicates whether or not the response should include asset count results for metaproperty-options. |
|
|
Comma-separated list of asset types. Filters the count results by asset type. It only makes sense to be defined if the count parameter was set to 1. |
|
|
Indicates whether or not the response should include the metaproperty options of each metaproperty. |
|
|
Comma-separated list of metaproperty ids. Will return a metaproperty for each existing id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperty dependencies
/api/v4/metaproperties/{id}/dependencies/
When a metaproperty has dependencies, the metaproperty won't be visble until a linked option is selected in the upload/bulk edit.
This call returns a list of depending meteproperty option ids.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperty options
/v4/metaproperties/{id}/options/
Retrieve the options for a specific metaproperty.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty option name. |
|
|
Maximum number of results.Maximum: 1000. |
|
|
Offset page for results: return the N-th set of limit-results. |
|
|
The ID of the metaproperty whose options to retrieve. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperty options by ids
/v4/metaproperties/options/
Retrieve metaproperty options filtered by provided IDs.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Comma-separated list of metaproperty-option ids. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific metaproperty
/api/v4/metaproperties/{id}/
Retrieve details of a specific metaproperty by its ID.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
Indicates whether or not the response should include asset count results for metaproperty-options. |
|
|
Comma-separated list of asset types. Filters the count results by asset type. It only makes sense to be defined if the count parameter was set to 1. |
|
|
Indicates whether or not the response should include the metaproperty options of the metaproperty. |
|
|
Include additional data in the response. |
|
|
The response format expected from the API (e.g. application/json). |
Metaproperty option dependencies (10)
POST Add a dependency
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/{dependencyId}/
Add a dependency between metaproperty options.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the option belongs to. |
|
|
The id of the (metaproperty) option to which you’d like to add a dependency. |
|
|
The id of the (metaproperty) option you’d like to become a dependency. |
|
|
The response format expected from the API (e.g. application/json). |
POST Add a dependency option to a group
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/group/{groupId}/{dependencyId}/
Add a dependency option to an existing dependency group.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option the dependency group belongs to. |
|
|
The id of the dependency group you’d like to add a dependency to. |
|
|
The id of the dependency (metaproperty option) you’d like to add to the dependency group. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
POST Create dependency group
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/group/
Create a new dependency group for metaproperty options.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option for which you’d like to create a dependency group. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
JSON-serialised list of dependency option ids. |
DELETE Delete a dependency
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/{dependencyId}/
Delete a specific dependency between metaproperty options.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the option belongs to. |
|
|
The id of the (metaproperty) option from which you’d like to delete a dependency. |
|
|
The id of the (metaproperty) option you’d like to delete. |
|
|
The response format expected from the API (e.g. application/json). |
DELETE Delete dependency group
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/group/{groupId}/
Delete a specific dependency group.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option the dependency group belongs to. |
|
|
The id of the dependency group you’d like to delete. |
|
|
The response format expected from the API (e.g. application/json). |
POST Modify dependency group
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/group/{groupId}/
Modify an existing dependency group.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option the dependency group belongs to. |
|
|
The id of the dependency group you’d like to modify. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
JSON-serialised string of dependency (metaproperty option) ids. |
DELETE Remove a dependency option from a group
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/group/{groupId}/{dependencyId}/
Remove a dependency option from a dependency group.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the metaproperty the (metaproperty) option belongs to. |
|
|
The id of the (metaproperty) option the dependency group belongs to. |
|
|
The id of the dependency group you’d like to remove a dependency from. |
|
|
The id of the dependency (metaproperty option) you’d like to remove from the dependency group. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve global option dependencies
/api/v4/metaproperties/options/dependencies/
Retrieve all global option dependencies across metaproperties.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperty option dependencies
/api/v4/metaproperties/{id}/options/dependencies/
Retrieve the dependencies defined for all options of a specific metaproperty. Use this action to see which option selections depend on others within a metaproperty.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific metaproperty option dependencies
/api/v4/metaproperties/{id}/options/{optionId}/dependencies/
Retrieve the dependencies defined for a specific option of a metaproperty. Use this action to see which other options depend on the given option.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
Metaproperty option id. |
|
|
Use grouped results like other option dependency calls. |
|
|
The response format expected from the API (e.g. application/json). |
OAuth 1.0a (3)
GET Authorise & Authenticate
/api/v4/oauth/authorise/
During this step the user has to authorise & authenticate the request token pair. This request should be executed in a webview or browser where the user has to login to the Bynder portal. No authorization header is needed for this request.
Warning: Make sure you understand that the permissions of the temporary access token pair that will be created afterwards, will be bound to the user that was used to login.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The value of the request token provided by the 1st step. |
|
|
A callback URL to be redirected to once the external portal login has been completed. If this parameter is missing then the auth_token is returned. |
|
|
The response format expected from the API (e.g. application/json). |
POST Exchange the request token pair for an access token pair
/api/v4/oauth/access_token
In the final step, you exchange the request token pair for a temporary access token pair. This requires a fully signed OAuth request.
You use the oauth_token and oauth_token_secret with the values provided by the response of the 1st request. If successful the request token pair is immediately expired.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST Obtain a Request token pair
/api/v4/oauth/request_token
The first step is obtaining a request token pair. A request token pair is only valid for 10 minutes and it will be used in the last step for obtaining the temporary access token pair.
This requires a valid signed OAuth request with only the Consumer Key and Secret.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
OAuth 2.0 (3)
GET Authorize application
/v6/authentication/oauth2/auth
When using the Authorization Code grant, redirect the user to the Authorize application endpoint. After the user
is authenticated and approves the authorization request, Bynder will redirect the user back with an
authorization code which can then be passed to the Token endpoint.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The client ID provided for the OAuth application. |
|
|
Scopes to request authorization for. These must be separated by a space. Include offline to get a Refresh Token. |
|
|
The URL for the authorize response redirect. This must exactly match one of the "Authorization redirect URIs" values specified for the OAuth application. |
|
|
Determines the grant being used. Only code is supported for the Authorization Code grant. |
|
|
A random string used to maintain state between the request and callback. This value must is used to prevent CSRF attacks. |
|
|
Optional origin header value to include in the request, typically the application's redirect URI origin. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve scopes
/v6/authentication/oauth2/scopes
The scopes endpoint provides a JSON formatted overview of the existing
scopes within Bynder and what user permissions are required in order
for the OAuth2 service to grant a scope to a user.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
POST Using an authorization code
/v6/authentication/oauth2/token
Use the token endpoint to retrieve a access token which can be used to authorize API
requests. Depending on the type of grant, different fields are required which are
outlined per request.
_The token endpoint requires authorization either in the body or by
sending the Authorization header._
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Optional origin header value to include in the request, typically the application's redirect URI origin. |
|
|
The response format expected from the API (e.g. application/json). |
Options (6)
|
Option Name |
Description |
|---|---|
|
|
Application client ID. |
|
|
Application client secret. |
|
|
Identifies the grant type being used. For Authorization Code grant use authorization_code. |
|
|
The URL specified in the Authorize application request, the values must match. |
|
|
The Authorization Code returned from the Authorize application request. |
|
|
List of scopes to request to be granted to the access token. Can only be a subset of the scopes requested in the Authorize application request. When not passed, all the scopes will be requested. |
Product layer metaproperties (4)
PUT Modify metaproperty option
/api/pim/metapropertyoptions/{id}/
Warning: Currently you can only edit the children of a metaproperty option.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty option id. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
A list of id's of the metaproperty options to be related as the metaproperty option's children. All current children will be overwritten. |
GET Retrieve metaproperties
/api/pim/metaproperties
Warning: Requires the metaproperty.view security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve metaproperty options
/api/pim/metaproperties/{id}/options/
Retrieves a paginated list of options for the given metaproperty id and these options' sub options.Warning: Requires the METAPROPERTYMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
Order of the options, based on the option z-index and option name. |
|
|
Index to load a specific set of metaproperty options. |
|
|
Amount of options that are retrieved per page. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific metaproperty
/api/pim/metaproperties/{id}/
Retrieve the metaproperty details and it's metaproperty options.Warning: Requires the METAPROPERTYMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Metaproperty id. |
|
|
The response format expected from the API (e.g. application/json). |
Security roles (2)
GET Retrieve security profiles
/api/v4/profiles/
To determine the security profile for your user you can compare the security profile id with the profileId retrieved from either the Retrieve specific user or Retrieve current user call.
It’s the API’s responsibility to enforce that users can only perform allowed actions but nevertheless we recommend that your application checks whether or not an action can be performed because this will create a better user experience.Warning: Requires the PERMISSIONMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific security profile
/api/v4/profiles/{id}/
This call allows you to retrieve your own security profile without requiring the PERMISSIONMANAGEMENT security role.
In order to get your own security profile use your user profile id retrieved by executing the Specific User or Current User call.Warning: Requires the PERMISSIONMANAGEMENT security role if not retrieving your own security profile.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Security profile id. |
|
|
The response format expected from the API (e.g. application/json). |
Smartfilters
GET Retrieve smartfilters
/api/v4/smartfilters/
Retrieve a list of all smartfilters configured in the Bynder portal. Use this action to fetch available smartfilters for filtering assets.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Tags (3)
POST Add tag to assets
/api/v4/tags/{id}/media/
Warning: Tag operations on assets require the MEDIAEDIT or MEDIAAUDIT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Tag id. |
|
|
A comma-separated list of asset IDs to remove from the collection before adding new ones. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
JSON-serialised list of asset ids to which you'd like to add the tag. |
DELETE Remove tag from assets
/api/v4/tags/{id}/media/
Warning: Tag operations on assets require the MEDIAEDIT or MEDIAAUDIT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Tag id. |
|
|
Comma-separated asset ids from which to remove the tag. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve tags
/api/v4/tags/
Retrieve a list of all tags used in the Bynder portal. Use this action to get the complete tag set for filtering or categorizing assets.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Maximum number of results.Maximum: 1000. |
|
|
Offset page for results: return the N-th set of limit-results. |
|
|
Order of the returned list of tags. |
|
|
Search on matching names. |
|
|
Minimum media count that the returned tags should have. |
|
|
The response format expected from the API (e.g. application/json). |
Trash
GET Retrieve recently removed assets
/api/trash/media/
Warning: You can only retrieve the removed assets from the last 30 days.
Warning: Requires the trash.assets security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Maximum number of results. |
|
|
Offset page for results: return the N-th set of limit-results. |
|
|
Retrieve assets removed after this date.Format: yyyy-mm-dd hh:mm:ss |
|
|
Field to sort on the returned list of assets. |
|
|
Sort order of returned list of assets. Sorts the list of assets by the field parameter defined, if the field parameter was not defined the results will be sorted by media.name. |
|
|
The response format expected from the API (e.g. application/json). |
Upload assets (7)
POST Finalise a completely uploaded file and save as a new asset additional
/api/v4/media/{id}/save/additional/{uploadId}/
Warning: This call should only be used if you are uploading an additional file for an asset, if you are not go to step 5.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id to which to save the new additional. |
|
|
The upload id of the file. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
Target id as returned by the initialise call. |
|
|
Base location of the uploaded file. |
|
|
Total number of chunks uploaded. |
GET Get closest AmazonS3 upload endpoint
/api/upload/endpoint
Retrieve the Amazon S3 endpoint URL closest to the caller's geographic location. Use this action before initializing an upload to ensure optimal transfer speed.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
POST Initialise upload
/api/upload/init
Initialize an upload session by requesting upload parameters from Bynder. Use this action to start the upload process and receive the necessary upload URL and fields.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (1)
|
Option Name |
Description |
|---|---|
|
|
Filename of new upload (extension required). |
POST Register uploaded chunk
/api/v4/upload/{id}/
Uploading a file consists of:
-
Breaking down your file in parts/chunks. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.
For more information, about how amazon handles parts/chunks, visit: Amazon's website.
-
Sending the chunks over to Amazon and then registering them to Bynder. You can repeat those calls up until your file has been uploaded completely.
1. Upload a chunk
Make a POST request to the Amazon upload endpoint you received from calling Get closest AmazonS3 upload endpoint.
Use a multipart/form-data to send all of the parameters that the multipart_params of the previous request included; plus the following additional parameters:
|
Name |
Value |
Type |
|---|---|---|
|
|
Content type extracted from the |
string |
|
|
Policy extracted from the |
string |
|
|
Signature extracted from the |
string |
|
|
Access control list extracted from the |
string |
|
|
Key extracted from the |
string |
|
|
Success action status extracted from the |
string |
|
|
Algorithm extracted from the |
string |
|
|
Credential extracted from the |
string |
|
|
Date extracted from the |
string |
|
|
Filename that was passed as attribute in the initialise upload request. |
string |
|
|
Chunk index number (indexing starts from 1). |
number |
|
|
Total number of chunks. |
number |
|
|
The value of the |
string |
|
|
File or chunk of the file to be uploaded. |
byte array |
2. Register uploaded chunk
After uploading a chunk, you must register it's completion to Bynder.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Upload id for the uploaded file. |
|
|
The response format expected from the API (e.g. application/json). |
Options (3)
|
Option Name |
Description |
|---|---|
|
|
Number of the chunk that was uploaded. |
|
|
The targetid that was returned by the initialise call. |
|
|
Location of the uploaded chunk. |
GET Retrieve poll state
/api/v4/upload/poll/
Warning: This call needs to be executed in a loop until its response returns the item(s) id(s) passed in the items parameter.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Comma-separated import id's of a finalised file, as returned by the finalise call. |
|
|
The response format expected from the API (e.g. application/json). |
POST Save as a new asset
/api/v4/media/save/{importId}/
Save the uploaded file as a new asset in Bynder. Use this action after the file has been uploaded to S3, providing the import ID from the initialization step.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Import id of a finalised and processed upload to be saved. |
|
|
The response format expected from the API (e.g. application/json). |
Options (17)
|
Option Name |
Description |
|---|---|
|
|
Brand id to save the asset to. |
|
|
Name of the asset. Warning: The asset will have no name if this is left empty. |
|
|
Description of the asset. |
|
|
Copyright information of the asset. |
|
|
Comma-separated list of tags of the asset. |
|
|
Dictionary with (metaproperty) options to set on the asset. Send fields as metaproperty.METAPROPERY_ID with a string of all its (metaproperty) options ids comma-separated. Warning: The list of (metaproperty) options ids should include all the (metaproperty) options ids available in the lower hierarchy; meaning it should include the (metaproperty) options of the (metaproperty) options etc. |
|
|
Comma-separated category ids of the asset. |
|
|
Flags if the asset should be sent to the waiting room. Warning: In order to be able to chose whether or not the asset will be uploaded to the waiting room you'll need both the MEDIAUPLOAD and MEDIAUPLOADFORAPPROVAL security role. |
|
|
Flags if the asset should be Public. |
|
|
If audit is set to true you can specify an accessRequestId to batch uploads to the waiting room. The accessRequestId is retrieved in the response of this endpoint, after you save the first asset of your batch. |
|
|
If audit is set to true you can specify a requestor ID (user ID) to identify the user uploading the asset to the waiting room. |
|
|
If audit is set to true you can specify an access type to define to which waiting room location the asset is uploaded to. The available locations are: Upload, Edit, Workflow approval (export), Shutterstock and Stock. |
|
|
Date/time of publication in ISO08601-format. |
|
|
DEPRECATED Date/time of publication in linked API user selected locale-format. |
|
|
Archive date/time of the asset in ISO8601-format. |
|
|
Watermark datetime. ISO8601 format: yyyy-mm-ddThh:mm:ssZ. |
|
|
CRC32 checksum of the original file, used for verification. |
POST Save as a new asset version
/api/v4/media/{id}/save/{importId}/
Save the uploaded file as a new version of an existing asset. Use this action to replace a previous asset version, providing the asset ID and the import ID from the upload initialization.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Asset id for which to save the new version. |
|
|
Import id of a finalised and processed upload to be saved. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
Users (6)
POST Create user
/api/v4/users/
Warning: User operations require the USERMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Optional flag indicating whether to include inactive users in the response; pass "true" to include inactive users. |
|
|
Limit the number of results returned. |
|
|
Specify the page number of results to retrieve. |
|
|
The response format expected from the API (e.g. application/json). |
Options (15)
|
Option Name |
Description |
|---|---|
|
|
Username for login. If not defined it will take your email as username. |
|
|
Password for login. |
|
|
Email address. |
|
|
Security profile id for determining the user's rights. Can be retrieved by using the Retrieve security profiles call. |
|
|
Whether or not the user will be active, inactive users won't be able to login. |
|
|
Prefered website language, options can be retrieved using the Retrieve account call. |
|
|
First name. |
|
|
Infix. |
|
|
Last name. |
|
|
A list of group ids to which the user will be added. Can be retrieved by using Retrieve groups call. Requires GROUPMANAGEMENT security role. |
|
|
Phone number. |
|
|
Company name. |
|
|
Company department. |
|
|
Job description. |
|
|
Company cost centre. |
DELETE Delete user
/api/v4/users/{id}/
Warning: Specific user operations require the USERMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id or username of the user you’d like to delete. |
|
|
The response format expected from the API (e.g. application/json). |
POST Modify user
/api/v4/users/{id}/
Warning: Specific user operations require the USERMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of the user you’d like to modify. |
|
|
The response format expected from the API (e.g. application/json). |
Options (16)
|
Option Name |
Description |
|---|---|
|
|
Username. |
|
|
Password for login. |
|
|
Email address. |
|
|
Security profile id for determining the user's rights. Can be retrieved by using the Retrieve security profiles call. |
|
|
Whether or not the user will be active, inactive users won't be able to login. |
|
|
Prefered website language, options can be retrieved using the Retrieve account call. |
|
|
First name. |
|
|
Infix. |
|
|
Last name. |
|
|
A list of group ids to which the user will be added. Can be retrieved by using Retrieve groups call. Requires GROUPMANAGEMENT security role. |
|
|
Phone number. |
|
|
Company name. |
|
|
Company department. |
|
|
Job description. |
|
|
Company cost centre. |
|
|
Indicates whether or not the user has accepted the login terms & conditions. |
GET Retrieve current user
/api/v4/currentUser/
Retrieve the current user information. Unlike Retrieve specific user this call doesn't require you to know your user id in order to retrieve your current user information.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific user
/api/v4/users/{id}/
Warning: Specific user operations require the USERMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id or username of the user you’d like to retrieve. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve users
/api/v4/users/
Warning: User operations require the USERMANAGEMENT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Whether to include inactive users in the list of results. |
|
|
Maximum results to return. If limit is not provided, all results are returned. Note: When using pagination, pagination information is returned as response headers. |
|
|
What page of results to return. |
|
|
The response format expected from the API (e.g. application/json). |
Workflow campaigns (5)
POST Create campaign
/api/workflow/campaigns/
Warning: Requires the CAMPAIGNADD security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
Options (8)
|
Option Name |
Description |
|---|---|
|
|
Name of the campaign |
|
|
4 character key representing the campaign |
|
|
Description of the campaign |
|
|
Date of when the campaign starts |
|
|
Date of when the campaign ends |
|
|
Status of Campaign open active/closed |
|
|
Id of the user responsible for the campaign |
|
|
Campaign Metaproperties |
DELETE Delete campaign
/api/workflow/campaigns/{id}/
Warning: Requires the CAMPAIGNREMOVE security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Campaign. |
|
|
The response format expected from the API (e.g. application/json). |
PUT Modify campaign
/api/workflow/campaigns/{id}/
Warning: Requires the CAMPAIGNEDIT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Campaign. |
|
|
The response format expected from the API (e.g. application/json). |
Options (8)
|
Option Name |
Description |
|---|---|
|
|
Name of the campaign |
|
|
4 character key representing the campaign |
|
|
Description of the campaign |
|
|
Date of when the campaign starts |
|
|
Date of when the campaign ends |
|
|
Status of Campaign open active/closed |
|
|
Id of the user responsible for the campaign |
|
|
Campaign Metaproperties |
GET Retrieve campaigns
/api/workflow/campaigns/
Warning: Requires the CAMPAIGNOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific campaign
/api/workflow/campaigns/{id}/
Warning: Requires the CAMPAIGNOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Campaign. |
|
|
The response format expected from the API (e.g. application/json). |
Workflow groups (5)
POST Create group
/api/workflow/groups/
Create a new workflow group in the Bynder workflow system. Use this action to define a group that can be assigned to workflow jobs.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
DELETE Delete group
/api/workflow/groups/{id}/
Permanently delete a specific workflow group by its ID. Use this action to remove a group that is no longer needed.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Workflow group. |
|
|
The content type of the request body, if needed. |
|
|
The response format expected from the API (e.g. application/json). |
PUT Modify group
/api/workflow/groups/{id}/
Update the details of an existing workflow group. Use this action to change group name or other properties.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Workflow group. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve groups
/api/workflow/groups/
Retrieve a list of all workflow groups. Use this action to get the available groups for assignment to workflow jobs.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific group
/api/workflow/groups/{id}/
Retrieve the details of a single workflow group by its ID. Use this action to get information about a specific group.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Workflow group. |
|
|
The response format expected from the API (e.g. application/json). |
Workflow jobs (8)
POST Create job
/api/workflow/jobs/
Warning: Requires the JOBADD security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Optional start date for filtering jobs by creation date, in ISO 8601 format. |
|
|
Optional end date for filtering jobs by creation date. |
|
|
Optional start date for filtering jobs by modification date. |
|
|
Optional end date for filtering jobs by modification date. |
|
|
Optional start date for filtering jobs by deadline. |
|
|
Optional end date for filtering jobs by deadline. |
|
|
Define the order in which results are sorted. |
|
|
Limit the number of results returned. |
|
|
Specify the page number of results to retrieve. |
|
|
The response format expected from the API (e.g. application/json). |
Options (7)
|
Option Name |
Description |
|---|---|
|
|
Name of the job |
|
|
Description of the job |
|
|
Date of when the job ends |
|
|
Id of the campaign the job is part of |
|
|
Id of the user responsible for the job |
|
|
Id of the preset the job should be created from |
|
|
ID and metaproperty values |
DELETE Delete job
/api/workflow/jobs/{id}/
Warning: Requires the JOBREMOVE security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Job. |
|
|
The response format expected from the API (e.g. application/json). |
PUT Modify job
/api/workflow/jobs/{id}/
Warning: Requires the JOBEDIT security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
The content type of the request payload sent to the API (e.g. application/json). |
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Job. |
|
|
The response format expected from the API (e.g. application/json). |
Options (6)
|
Option Name |
Description |
|---|---|
|
|
Name of the job |
|
|
Description of the job |
|
|
Date of when the job ends |
|
|
Id of the campaign the job is part of |
|
|
Id of the user responsible for the job |
|
|
ID and metaproperty values |
GET Retrieve jobs
/api/workflow/jobs/
Warning: Requires the JOBOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
Only return jobs which have a dateCreated on or after this datetime. |
|
|
Only return jobs which have a dateCreated before or on this datetime. |
|
|
Only return jobs which have a dateModified on or after this datetime. |
|
|
Only return jobs which have a dateModified before or on this datetime. |
|
|
Only return jobs which have a deadline on or after this datetime. |
|
|
Only return jobs which have a deadline before or on this datetime. |
|
|
Comma-separated list of workflow user IDs or workflow user group IDs. |
|
|
Comma-separated list of workflow user IDs. |
|
|
Comma-separated list of job status. |
|
|
Field to order results by |
|
|
Maximum results to return, maximum: 1000. If limit is not provided, all results are returned. Note: When using pagination, pagination information is returned as response headers. |
|
|
What page of results to return. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve media of specific job
/api/workflow/jobs/{id}/media/
Warning: Requires the JOBOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Job. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific job
/api/workflow/jobs/{id}/
Warning: Requires the JOBOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Job. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific job preset
/api/workflow/presets/job/{id}/
Warning: Requires the PRESETOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Job Preset. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve the jobs of a specific campaign
/api/workflow/campaigns/{id}/jobs/
Warning: Requires the CAMPAIGNOVERVIEW security role.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a Campaign. |
|
|
Only return jobs which have a dateCreated on or after this datetime. |
|
|
Only return jobs which have a dateCreated before or on this datetime. |
|
|
Only return jobs which have a dateModified on or after this datetime. |
|
|
Only return jobs which have a dateModified before or on this datetime. |
|
|
Only return jobs which have a deadline on or after this datetime. |
|
|
Only return jobs which have a deadline before or on this datetime. |
|
|
Comma-separated list of workflow user IDs or workflow user group IDs. |
|
|
Comma-separated list of workflow user IDs. |
|
|
Comma-separated list of job status. |
|
|
Field to order results by |
|
|
Maximum results to return, maximum: 1000. If limit is not provided, all results are returned. Note: When using pagination, pagination information is returned as response headers. |
|
|
What page of results to return. |
|
|
The response format expected from the API (e.g. application/json). |
Workflow metaproperties (2)
GET Retrieve metaproperties
/api/workflow/metaproperties/
Retrieve a list of all workflow metaproperties. Use this action to get the custom fields available for workflow jobs.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |
GET Retrieve specific metaproperty
/api/workflow/metaproperties/{id}
Retrieve the details of a single workflow metaproperty by its ID. Use this action to get information about a specific custom field.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The id of a metaproperty. |
|
|
The response format expected from the API (e.g. application/json). |
Workflow users
GET Retrieve users
/api/workflow/users/
Retrieve a list of all users in the workflow system. Use this action to get available users for assignment to workflow jobs.
Parameters
|
Parameter Name |
Description |
|---|---|
|
|
Additional HTTP header name/value pairs to include in the request. |
|
|
The response format expected from the API (e.g. application/json). |