REST API

Follow

The Webdam API is the underlying interface for building apps using the power of Webdam. The API allows developers to securely read and write from Webdam so your users can push and pull their important files and metadata. You’ll also have access to powerful Webdam features such as file sharing, upload, search and more.

In order to use the API, you'll need to create and use an admin account within the system. Please ask your DAM admin to assist you with an account if you don't already have one.

If API usage/analytics is important to your organization, consider using a unique admin seat for the API.

More information on the Search 2.0 API can be found here and the Workstream API can be found here.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Lee - former customer Metcalfe
    Comment actions Permalink

    Is there a method to retrieve an assets in a given format and size or download an asset based on a given preset?

  • Avatar
    Permanently deleted user
    Comment actions Permalink

    Hi Lee- Thank you so much for reaching out. Your customer success manager, Scott, will be reaching out to you directly about this. Thanks!

  • Avatar
    Keith Holland
    Comment actions Permalink

    Bump. Was there ever a solution provided for the above question?

  • Avatar
    Sean Johnson
    Comment actions Permalink

    Hi Keith,
    Currently, the Original file is the only file type that may be retrieved using the Rest API.

    Thanks for the feature idea! I'm passing it on to our product team.

    I also recommend that you add your idea to our customer community so other users can vote on it. You can add the idea at: Ideas & Suggestions. We monitor all the suggestions and ideas very closely.

  • Avatar
    Kevin Dvorscak
    Comment actions Permalink

    Does anyone have a successful example of the file upload in PHP? When I get to Step 2, I keep getting a "SignatureDoesNotMatch" response from AWS. My variable dump looks like they match, but clearly I'm missing something.

  • Avatar
    Sean Johnson
    Comment actions Permalink

    Hi Kevin,

    In order to further assist you, I'd like to verify that all of the necessary parameters are being entered correctly.

    1. Verify that the request being made is a 'PUT' request
    2. Make sure you're getting the exact Presigned URL from step 1, and making the PUT request in step 2 exactly to that URL
    3. Verify that whatever value you've put for content type in step 1 is sent in step 2

    The content type is sent as a header in step 2 and matches exactly what is in step 1.

    If you still receive this response. Please submit a support ticket and we will be happy to further assist you with this process!

    Best,

  • Avatar
    Sergei Churilo
    Comment actions Permalink

    Are there any pitfalls with "Notifications" REST API endpoint?
    I'm trying to get the notifications but no luck.
    The endpoint returning empty notification list, such that
    (
    [last_read] => 2019-07-30 06:44:02
    [offset] => 0
    [limit] => 20
    [total] => 0
    [notifications] => Array
    (
    )
    )
    Tried different actions such as uploading/approving an asset, updating an asset to a new version, deleting an asset.
    Can anyone help me with that?

    Thanks!

Request Support
Existing Request