Cloudinary offers SDKs for many programming languages and frameworks. Even though it also offers an Upload API endpoint for both back-end and front-end code, most developers find the SDKs very helpful. If you’re working with a powerful back-end framework like Python Flask, you’ll be happy to hear that a Python SDK is now available.
This tutorial walks you through the process of building an API to upload images to Cloudinary. You can also upload other file types, including video and even nonmedia files, with the API.
Generally, code that runs on the server is back end, and code that runs on the browser is front end. However, since server code can render HTML, CSS, and JavaScript, which all run on the browser, confusion sometimes results.
In the context of the Cloudinary SDKs, the back-end ones can read secret credentials, which should not be shared in the front end. In other words, you must never expose the back-end environment variables in the front end because front-end SDKs cannot hide credentials that are meant to be kept secret. As a solution, you can upload browser code with Cloudinary’s unsigned presets without revealing secret credentials. A better way would be to build a back-end API for secure uploads, keeping your API_SECRET
credential hidden. Read on to see how to do that with Cloudinary’s Python SDK and Python Flask or Python Django.
The Flask framework makes it easy to define routes and their functionalities. To get started, first create a route named /upload
, which accepts a POST
that contains multipart/form-data. You then package up the image file input into a FormData
object in a submit handler and POST
it to your own Flask API to call Cloudinary’s Upload API, which is configured with your full set of Cloudinary credentials.
Flask’s request
option enables you to get data from the client. When submitting files, such as uploading images, you can call upon request
to access them.
from flask import Flask,render_template, request
if request.method == 'POST':
file_to_upload = request.files['file']
Code language: JavaScript (javascript)
However, if you’re looking to simplify the process of building RESTful web services with Flask, you can utilize the flask_restful module. By creating a new class that inherits from Resource, you can define a post() method that accepts the file as a parameter. The werkzeug.datastructures.FileStorage class can be used to get the file object, which can then be saved to a desired location.
Here’s an example of how you can integrate this approach:
from flask import Flask, request from flask_restful import Resource, Api from werkzeug.datastructures import FileStorage app = Flask(__name__) api = Api(app) class UploadFile(Resource): def post(self): file = request.files['file'] file.save('/uploads/' + file.filename) return 'File uploaded successfully!' api.add_resource(UploadFile, '/upload')
This code creates a new Flask project and an API endpoint that allows users to upload files. The post() method of the UploadFile class accepts the file as a parameter and saves it to the /uploads directory. The return statement provides a success message. To test this code, tools like Postman can be used to send a POST request to the /upload endpoint.
The data retrieved from request.files['file']
is an instance of werkzeug.FileStorage
. The object can be handed off to the Python SDK’s Upload function. Flask then wraps Werkzeug, which handles the details of the Web Server Gateway Interface (WSGI).
if file_to_upload:
upload_result = cloudinary.uploader.upload(file_to_upload)
app.logger.info(upload_result)
For uploads to Cloudinary, the default resource_type
is image
. To expand or create a new Flask API, add resource_type: 'video'
or resource_type: 'raw'
for video or raw files, respectively. Raw refers to nonmedia file formats, including text and JSON.
Finally, upload_result
is an object that contains the upload response. To complete the actions of your upload
API, return that response to the client, like this:
from flask import jsonify
return jsonify(upload_result)
Code language: JavaScript (javascript)
Below is the complete code of your upload
API.
@app.route("/upload", methods=['POST'])
def upload_file():
app.logger.info('in upload route')
cloudinary.config(cloud_name = os.getenv('CLOUD_NAME'), api_key=os.getenv('API_KEY'),
api_secret=os.getenv('API_SECRET'))
upload_result = None
if request.method == 'POST':
file_to_upload = request.files['file']
app.logger.info('%s file_to_upload', file_to_upload)
if file_to_upload:
upload_result = cloudinary.uploader.upload(file_to_upload)
app.logger.info(upload_result)
return jsonify(upload_result)
Code language: JavaScript (javascript)
Next, follow the steps below to build the app.
The command below establishes your virtual environment. This is an important step for encapsulating the libraries you’ll be using in this app.
python3 -m venv env
source env/bin/activate
To deactivate the environment, type:
deactivate
source env/bin/activate
Install Flask with this command:
python3 -m pip install Flask==1.1.1
Create a requirements.txt
file to keep track of all the versioned libraries you need for the app and to facilitate future deployment.
python3 -m pip freeze > requirements.txt
Code language: CSS (css)
If necessary, upgrade the Python package installer, called PIP, with the command below. The command might vary, depending on your local Python installation. As shown below, the freeze
command writes the library and version to the requirements.txt
file.
usr/local/opt/python@3.9/bin/python3.9 -m pip install --upgrade pip
python3 -m pip freeze > requirements.txt
Next, install Cloudinary to gain access to its Upload API for the Python SDK.
python3 -m pip install cloudinary
python3 -m pip freeze > requirements.txt
Code language: CSS (css)
If you want to access your upload
API from a client served from a different host, add Cross Origin Resource Sharing (CORS) support:
python3 -m pip install flask-cors
python3 -m pip freeze > requirements.txt
Code language: CSS (css)
Now you can add code to configure CORS for all the APIs and, specifically, the upload
API. The code below demonstrates both options.
from flask_cors import CORS, cross_origin
app = Flask(__name__)
# After creating the Flask app, you can make all APIs allow cross-origin access.
CORS(app)
# or a specific API
@app.route("/upload", methods=['POST'])
@cross_origin()
Code language: PHP (php)
You can easily load environment variables with Python. Conveniently, the python-dotenv
library is modeled on the Node.js dotenv
package. You need three Cloudinary environment variables, i.e., CLOUD_NAME
, API_KEY
, and API_SECRET
, for your code, but don’t share API_SECRET
. You can export those variables to the local environment. When you deploy to Heroku, you can add them to make them available to the app when it runs in a Heroku container.
from dotenv import load_dotenv
load_dotenv()
Code language: JavaScript (javascript)
In your upload
API, you read in the environment variables with the cloudinary.config()
function. You then access those variables with the os.getenv()
function in the dotenv
library.
cloudinary.config(cloud_name = os.getenv('CLOUD_NAME'), api_key=os.getenv('API_KEY'),
api_secret=os.getenv('API_SECRET'))
Code language: JavaScript (javascript)
When working locally, you can create a gitignore’d .env
file that contains your Cloudinary credentials for local testing. The values for those credentials are displayed in your Cloudinary console.
CLOUD_NAME=CLOUD_NAME
API_KEY=API_KEY
API_SECRET=API_SECRET
Next, install the python-dotenv
library:
python3 -m pip install python-dotenv
python3 -m pip freeze > requirements.txt
Code language: CSS (css)
You’re now ready to test the app locally. You can do end-to-end testing with Postman and a local form that points at a server running on localhost
.
Create your app with an upload function by downloading, cloning, or copying from this GitHub repository. Add your credentials to a .env
file and then start your server on localhost
.
python3 app.py
Code language: CSS (css)
The above command opens a server at http://127.0.0.1:5000/
. Note that the default port is 5000.
In Postman, do the following:
- Set the method to
POST
. - Set the body type to
form-data
. - Establish Key/Value pairs for input. Set the value for the Key to
file
. Mouse over the Key field and choose Text or File from the drop-down menu. Under File is a Select Files button; click it to select a file from your local drive. - Click Send to process the request.
The Cloudinary Upload API response is displayed at the bottom of the page
Follow these steps:
-
Open the
index.html
file with a local HTTP server. Choose a local file and click Upload. -
Run the JavaScript code below. The
fetch
command calls the server that runs onlocalhost
.fetch("http://127.0.0.1:5000/upload", options) .then((response) => { return response.json(); }) .then((data) => { console.log(data); }) .catch((error) => { console.log(error); });
Code language: JavaScript (javascript)If the process is successful, the Cloudinary Upload API response is displayed in the console. Don’t forget to set
event.preventDefault();
for the submit handler. Otherwise, you’ll get a page refresh and won’t see your log. -
Post a file in a submit handler by creating a
FormData
object and appending the file, as shown in the code below.const formData = new FormData(); formData.append("file", fileInput.files[0]); const options = { method: "POST", body: formData, };
Code language: JavaScript (javascript)
The above code packages up the file you select in your form input as if you had submitted a multipart form. A multipart form is important for submitting files because each input is sent as a block of data, separated by boundaries. The result is then displayed in your console, like this:
Heroku is a platform as a service (PaaS) for serving prototypes or production-ready apps. Host the API you just built on Heroku by doing the following:
-
Create a free account on Heroku.
-
Install Gunicorn, short for Green Unicorn, a Python WSGI HTTP server for hosting apps.
python3 -m pip install gunicorn==20.0.4 python3 -m pip freeze > requirements.txt
-
Create a file called
Prodfile
with instructions for Heroku to start your app with Gunicorn:web: gunicorn app:app
Code language: CSS (css) -
Create a file called
runtime.txt
that contains the Python version you want to use:python-3.9.1
Code language: CSS (css) -
Deploy with Git:
git init git add . git commit -m"my first commit" # Create a new Heroku app heroku create # You will get a URL where the app will be hosted git remote -v # will confirm that you have set up a remote to push to Heroku # If you have an existing Heroku app that you created in the Heroku GUI # you can add it with this command instead of creating a new one heroku git:remote -a thawing-inlet-61413 # To deploy, you can now just push to Heroku git push heroku master # Open your server (it's nice to have a GET method so you can verify like this) heroku open # To log in to Heroku from the command line, type: heroku login # You’ll then be prompted to open the webpage to log in
Code language: PHP (php)
You can build the new Heroku app with the CLI. However, as noted above, if you built it on the heroku.com dashboard, you can just add the link Heroku created for you to a git:remote
command.
To load environment variables on Heroku, open the dashboard and navigate to your new server instance. Click the Settings tab and scroll down to the Config Vars section. Click Reveal Config Vars, where you can enter Key/Value pairs. This is where you load your Cloudinary environment variables: CLOUD_NAME
, API_KEY
, and API_SECRET
.
For more options for setting up prod
and dev
instances, see the Heroku documentation.
If you have a GET
method API like the “Hello World!” in the app.py
example, you can open the Heroku app in the browser.
For end-to-end testing, you can POST
to the Heroku server link from Postman. The result is similar to that for local testing.
Alternatively, modify the index.html
file to post to your Heroku server. Just add your Heroku server link to the fetch
command, like this:
fetch("https://xxxx.herokuapp.com", options)
Code language: JavaScript (javascript)
You might have noticed that the Heroku deployment link has been erased from the images above. That’s for security. Deploying this app to Heroku enables you to upload data to Cloudinary. If the link is not secured for use on an authenticated webpage only, anyone can upload to your Cloudinary cloud. Even though you are hiding your environment variables, you’d have created a public method to change data on your cloud.
This tutorial does not cover how to set up authentication. Many options are available for authentication of API routes. You might want to look into Auth0, Google, or GitHub. Alternatively, build your own process based on your user database for this type of authentication.
Once you get this API running, you can build other media APIs with the Cloudinary Python SDK by following the same pattern. Have fun!