Cloud API Integration
How a web application enhances user-uploaded images with the VIESUS Cloud API — asynchronous, webhook-driven, no infrastructure — and which interface fits.
Last updated
Was this helpful?
How a web application enhances user-uploaded images with the VIESUS Cloud API — asynchronous, webhook-driven, no infrastructure — and which interface fits.
The scenario: A web application lets users upload photos that are enhanced automatically and made available to download. Processing is asynchronous — users upload, are notified when the result is ready, and retrieve it — with no enhancement infrastructure to run and billing per image.
Use the VIESUS Cloud API. It's a hosted GraphQL API — no library to install, no GPU to provision, no license to manage. You pay per enhancement and get AI features (including upscaling) without a local NVIDIA GPU.
Choose the Cloud when you don't want to operate servers. If you need on-premise processing or air-gapped operation, use the CLI or Node.js module instead.
Upload an image or PDF — either from a public URL, or via a signed upload URL so the browser uploads directly to VIESUS Cloud storage (keeping large files off your backend).
Trigger enhancement with the parameters you want.
Get the result by either polling the job status or — recommended for production — receiving a webhook when processing completes, then downloading the enhanced file.
Billing is credit-based, charged per enhancement.
Connectivity
Requires internet access and file upload; not suitable for air-gapped environments.
Upload pattern
The signed-URL flow avoids routing large files through your backend, reducing latency and egress cost.
Webhooks
Prefer webhooks over polling at scale, and always verify the webhook signature before trusting an event.
Credits
Track consumption and budget against your volume — see Credits.
Limits
Requests are subject to API rate limits and file-size limits.
Last updated
Was this helpful?
Was this helpful?
