Control project access
Project-scoped keys keep media access within its project. Create and revoke keys from your account.
Platform
Your media, organized by project.
Prepare images, process PDFs and generate codes with a consistent way to authenticate requests and track usage.
- Your projectOne scope for media and keys
- Your serverAn authenticated API request
- Your outputImage, PDF, PNG or SVG bytes
Choose the work your application needs.
Pick a capability, then authenticate with a project key from your server.
Manage keys, media and usage.
Keep access, limits and output choices visible in one workspace.
Track usage and limits
Track credits, storage and bandwidth against your assigned limits in the Customer portal.
Set output options
Explicit dimensions, formats and processing options make requests easy to inspect and reproduce.
Getting started
Four steps, one project.
Create a project
Keep your images, API keys and usage together in a project.
Create an API key
Copy it when issued. Keep it on your server and revoke it when no longer needed.
Choose a source
Upload an original. Remote URL input is available when your account entitlement allows it.
Request a transformation
Set the dimensions, fit and format. Receive image bytes in the response.
The processing pipeline
Keep the original. Specify the derivative.
Uploads preserve the original bytes. Transformations can orient, trim, crop, flip, rotate, resize, adjust color, apply effects and encode a new image. Derived images omit embedded metadata.
Explore image operations →| Stage | What it contains |
|---|---|
| Source | An uploaded image, or a remote URL when enabled for your account. |
| Specification | Dimensions, fit, format and optional supported operations. |
| Response | Image bytes returned through an authenticated request. |
| Workspace | Project media metadata, API keys and usage. |
Storage choices
Choose the lifetime of the result.
PERSIST- Store the transformed image for later authenticated retrieval, subject to deletion and retention policies.
CACHE- Reuse a matching stored result within its cache lifetime. Expiry and physical cleanup are separate.
EPHEMERAL- Return the transformed bytes without saving an output media file.
Processing, storage and bandwidth remain subject to account limits. Ephemeral output does not remove an uploaded original.
Built for server integration
A key belongs to a project.
Use a project API key from your server to work with that project’s media. Keep it out of browser bundles, public repositories and client-side URLs.
Review authentication boundaries →A workspace for the account owner.
The Customer portal uses account authentication to manage projects and keys. Media requests accept a customer bearer token or a project API key, never both together.
Useful wherever dimensions matter.
Prepare catalog thumbnails, editorial images and application assets with explicit sizes and formats. Deliver the result through your own application.
Product questions, answered.
Should I use the Customer portal or the API?
Use the portal to manage your account, projects and keys, and to run the media tools interactively. Use the API from your server to integrate those operations into an application. Choose a tool or build your first API request.
Do I need a separate project for each tool?
One project can hold image, PDF and code outputs. Projects give each integration its own media and API keys; operation access follows your account’s assigned terms. Read projects and keys.
Can I keep generated files for later?
Code and PDF generation return temporary bytes. You can download those bytes or explicitly save supported outputs as private project artifacts. Image transformations have their own storage modes. See saving and retrieving outputs for the distinction and current limits.
Can I put an Imazeo media URL directly on my public website?
Media downloads require authentication; public CDN URLs and customer signed delivery URLs are unavailable. Receive the bytes on your server and deliver them through your own application. Review security and server-side key handling.
Where can I check plans, usage and renewal?
Plans and pricing explains the manual paid-access model. Your account’s Plan page shows your actual assigned terms; the limits guide explains credits, storage and bandwidth.
Where do I go if an integration fails?
Start with errors and recovery. For help, use account support or Contact. Include an operation and request ID when available; never send passwords, tokens or API keys.
Build with Imazeo
Start with your first project.
Create an account, set up a project and make your first API request.