The MediaValet API allows developers to create code to execute all capabilities currently available within the MediaValet portal.
Getting Started
1. Ensure you have a user account in the MediaValet library you wish to integrate with.
- If you have a non-Administrator account, please ensure an Administrator of the library is CC'd on the email when emailing the support team.
2. Create an account in the MediaValet Developer Portal by going to the registration page here, following this article.
3. Once registration is complete and a subscription has been created, the MediaValet Support Team will receive your request and will contact you directly via email to finalize the setup.
- All custom redirect_URLs will need to be whitelisted by the MediaValet Support team in order to be successfully redirected back to the application you are working out of.
- By default, we whitelist https://www.getpostman.com/oauth2/callback, https://oauth.pstmn.io/v1/callback, https://oauth.pstmn.io/v1/browser-callback
5. Once you are contacted, the support team will ensure you are an active user in MediaValet and will provide the Client Id, Client Secret and approve the Subscription Key for the plan subscribed to.
6. With the Client ID, Secret, and Subscription Keys you will now be able to make use of the MediaValet API.
NOTE: The Client Id, Client Secret and Subscription Key values can be shared across multiple users in the same library that are working on the same third-party integrations.
Watch the video below for a quick tour of our API
NOTES:
-
Please ensure you have signed up for a developer account and subscribed to a subscription plan beforehand. This is required in order for MediaValet Support to complete the setup.
Parameter Description client_id Identifies the client and must match the value pre-registered with MediaValet. client_secret This client secret is used in conjunction with client_id to authenticate the client application. code The value is what was returned from the authorization endpoint. The code has a lifetime of 60 seconds. grant_type Can be one of the following: authorization_code or refresh_token. Determines the mechanism MediaValet uses to authorize the creation of the tokens. redirect_uri Required when grant_type is authorization_code. Specifies the callback location where the authorization was sent. This value must match the redirect_uri used to generate the original authorization_code. refresh_token Required when grant_type is refresh_token. The value is a valid refresh token that was returned from this endpoint previously.
Further Learning
Our team has created a helpful API training guide which can be found at https://docs.mediavalet.com
Should you have any further questions, please do not hesitate to contact MediaValet Support by sending an email to support@mediavalet.com