Studio API access for product teams that need layer workflows in production
Connect your app, queue jobs from your own interface, and move layered image operations into a repeatable API pipeline without rebuilding the Studio logic yourself.
Access policy
API access is currently available for Studio users who need production workflows, scoped onboarding, and a clear integration path.
Best fit
Product teams, internal tooling groups, and SaaS platforms moving validated Studio workflows into code.
Request details
Include your workflow, expected traffic, output format, and delivery destination so access can be scoped accurately.
Launch path
Start in Studio, validate the workflow, then move into a reviewed API onboarding path when your use case is ready.
Core capabilities
What Studio API access is designed to support
The page is positioned for teams that need real workflow execution, not just a single endpoint without operational context.
Layer workflow execution
Run layered image jobs, retrieve structured outputs, and feed downstream design or automation systems with predictable result formats.
Background operations
Trigger subject isolation, background splitting, and reconstruction flows when your product needs more than a single transparent cutout.
Visual editing pipelines
Route requests through the same Studio logic used for guided editing flows, including prompt-driven transformations and multi-step outputs.
Operational onboarding
Access is provisioned with implementation guidance so Studio customers can align rate expectations, output handling, and launch requirements before production traffic.
Best fit
Where API access fits best
Teams usually outgrow manual Studio-only usage when the same workflow needs to run repeatedly inside another system.
Internal creative tooling
Use the API when your design or ops team already works inside a custom dashboard and needs layered output without switching products.
Content automation systems
Pipe requests from campaign builders, CMS jobs, or asset pipelines when image editing must run as part of a larger workflow.
Studio-backed SaaS features
Add layered image, cleanup, or background workflows to your own product while keeping request handling inside a managed Studio relationship.
Integration path
How API access works
The request path is intentionally scoped so teams can move from Studio validation to production integration without guessing at output shape or launch readiness.
Step 01
Confirm your Studio use case
Share the workflow you need to automate, expected monthly volume, output format, and where the results should land.
Step 02
Review access scope and onboarding
We align on the Studio plan, the operations you need, integration constraints, and any launch requirements before enabling API access.
Step 03
Integrate and validate in your environment
Connect your product or automation layer, run sample jobs, and verify request handling, output shape, and downstream processing before rollout.
Request details
What to include in your request
Good API requests are specific. This helps scope the workflow correctly and avoids a vague handoff that slows onboarding.
| Field | What to send |
|---|---|
| Workflow goal | What the API should automate and what the result should enable. |
| Volume estimate | Expected weekly or monthly request volume and any launch spikes. |
| Output format | Layered assets, background outputs, edited images, or downstream payload needs. |
| Delivery path | Where results should go after processing: internal tools, CMS, storage, or product UI. |
| Production timeline | Whether you are validating, piloting, or preparing for a near-term launch. |
Evaluation table
When Studio is enough and when API access makes sense
Not every workflow needs an API on day one. The right path depends on whether the job is still being shaped or already needs to run repeatedly inside another system.
| Situation | Best path | Why |
|---|---|---|
| Manual validation and one-off runs | Studio only | Best when your team is still shaping the workflow and wants direct operator control. |
| Internal team workflow automation | Studio + API access | Useful when the workflow is already proven and needs to run inside your own dashboard or ops tooling. |
| Customer-facing product features | API access | Appropriate when layered image or editing operations must happen programmatically behind your product experience. |
| High-volume repeatable jobs | API access | Better fit when throughput, output handling, and launch constraints need to be reviewed as part of onboarding. |
Request access
Start with your Studio workflow, then request API onboarding
The fastest request gets specific about workflow intent, expected traffic, output format, and where results must be delivered.
FAQ
Frequently asked questions
These answers are written for teams evaluating whether Studio API access is the right operational path.
Who can request Studio API access?
Studio API access is intended for Studio users who need operational workflows in production, not one-off personal experiments.
Can I get an API without using Studio first?
The current path starts from Studio usage because access is scoped around workflow fit, output expectations, and onboarding readiness.
What can I run through the API?
Typical requests cover layered image outputs, background operations, and visual editing pipelines that map cleanly to the Studio workflow model.
Is the API intended for high-volume automation?
Yes, but access is reviewed with expected volume so throughput, onboarding, and production constraints can be aligned before rollout.
Do I get PSD or layered asset outputs through the API?
That depends on the workflow you are approved for, but the goal is to support downstream editing and automation use cases rather than a flat image-only handoff.
Can I use the API for customer-facing product features?
Yes, if your Studio setup is intended to power a customer-facing experience and the workflow is a fit for supported operations.
How do I apply for access?
Use the request CTA on this page and describe your Studio workflow, product context, expected traffic, and desired outputs.
Does API access include onboarding support?
Yes. The access process is designed to clarify workflow scope, implementation expectations, and launch readiness before production use.
Can I start with Studio and add API access later?
Yes. That is the recommended path when your team wants to validate the workflow manually before moving it into code.
Where should I send API access questions?
Use the contact channel on this page and include your Studio use case so the request can be reviewed with the right context.