Separate Image Repositories
Create projects under your organization to separate different types of images. Each project gets its own upload URLs. Private API key access to projects can be configured for security and access control.
Project Organization Features
Simple project separation with isolated upload URLs and configurable API access.
Environment Separation
Use separate projects for production and staging environments.
// Environment separation exampleconst environments = {production: {projectId: 'prj_ypPsvV9RyQvtvz6GjIcAN',uploadUrl: 'https://api.icefiery.com/v1/upload-temporary-image/upl_3k8mN7qR9tXwZpVx2L4Df',apiKey: 'private_4r7N8kQ2mP9sT6vY1xZ5A'},staging: {projectId: 'prj_mX7nQ3kR8tYwZpV2jF9A',uploadUrl: 'https://api.icefiery.com/v1/upload-temporary-image/upl_7qR9sT2mN8kP5vY1xZ4A',apiKey: 'private_8kP5vY1xZ4A7qR9sT2mN'}};// Use different projects for different environmentsconst currentEnv = process.env.NODE_ENV === 'production' ? 'production' : 'staging';const config = environments[currentEnv];const uploadImage = async (file) => {const res = await fetch(config.uploadUrl, {headers: {'X-Original-Filename': file.name,},body: file,});return res.json();};
Keep production images completely separate from development and staging environments.
Production API keys cannot accidentally access staging images, and vice versa.
Test new features and transformations without affecting production image repositories.
Staging environments get their own isolated image collections and API access.
Common Use Cases
How projects help organize different types of image repositories.
Separate user-submitted profile pictures from product catalog images. Each type gets its own project and upload URL.
Keep production and staging images completely separate. No risk of staging data affecting production.
Ready to Organize Your Images?
Create projects to separate your image repositories with isolated upload URLs and API keys.