This article covers handling your Uploadcare account, it explains how to create, manage, and configure “Projects.”
The Uploadcare experience is centered around the concept of a “Project.” Projects are separate environments that can hold different sets of files and settings. For instance, you could use one project to receive user-generated content, another for implementing advanced security features, and a third one to serve your frontend assets.
When you sign up for a new Uploadcare account, we add one default project. So, explicitly adding another project is optional: you can stick with the default one for creating a test environment and going through every other section of this article.
Uploadcare APIs and API clients (e.g., File Uploader) tell your projects from one another by their API keys.
To discover API keys for an Uploadcare project, navigate to the respective section on the project overview page in your dashboard.
Depending on which Uploadcare features you want to use, you will implement
public_key or a key pair.
secret_key is required when using our REST API to
manage files within a Project or implement Video Processing,
Document Conversion or
Object Recognition, or when using Signed Uploads. You can add multiple secret API keys to
a single Uploadcare project to ensure extended control options over your
The Files section allows viewing the set of files associated with the project. You can add new files, search the set for entries, copy individual file URLs or UUIDs, and delete files from a project.
While the Files view allows you to implement basic files management, use our REST API for more sophisticated scenarios like integrating Uploadcare with your product’s API.
Under the “Settings” section, you can find more sophisticated options. Change those when setting up specific file flows; the deafults are perfectly fine for the majority of appliances.
When you “store” files on Uploadcare, you make them “permanent” as opposed to “temporary” ones that are deleted from your account in 24 hours after the upload. By default, Uploadcare automatically stores every uploaded file. You can change the behavior by disallowing “Automatic file storing.”
Then, every file will be treated as temporary unless you explicitly “store” a file by making a request to our REST API.
Uploadcare can copy every “stored” file to a custom S3 Bucket or Selectel Storage. The process is automatic, we require you to connect backup storage once, and will then systematically copy your files there to form a backup.
This section allows setting up OAuth applications for one of the available providers. Please, refer to our Community to learn more.
You may choose to connect your storage to Uploadcare instead of using the one provided by Uploadcare (storage limits depend on your Pricing Plan). Please, refer to the respective section of our Documentation for details.
You can further enhance the security of your file uploads by generating a special token on your backend and requiring our API to check token validity. This will allow you to implement access and control management in file uploading flows. This sections allows you to turn on the behavior. Note, when switched on, we will no longer accept any uploads to the project without a token. Please, refer to our Documentation to learn more.
Uploadcare REST API allows adding custom webhooks to notify your application about file uploads with the customized payload. Please, refer to our Documentation to learn more.
Protect your account from bad actors willing to do optimisations on your behalf, and get a proxy endpoint for Adaptive Delivery.
This section allows changing the name of your project or removing it from your account.
You can go to your Uploadcare Billing Options from your Dashboard or by using this link. From there, you can: