Picsart API Platform
← All models

Picsart Effects

New

Picsart · Image · Image → Image

Apply curated Picsart effect presets to a photo — multi-step Magic Flow pipelines, one tap.

Model ID: picsart-flowWorkflow: picsart-flow/v1/effects
Effect PresetsImage Required
Try on Playground ↗

Overview

Alongside the unified model APIs, we expose compatibility APIs that take each vendor's original parameters exactly as the vendor defines them — nothing renamed, nothing reshaped on the way through.

That makes them the shortest path onto Picsart if you already work with the vendor directly: the request bodies you've already written keep working as they are. You keep their parameter names and defaults, and you get the vendor's full parameter set rather than the subset that is shared across every model.

The cost is that a request is written for one vendor — switching models later means rewriting it, and results come back in the vendor's own shape. When you'd rather write once and change models freely, use the unified API.

Make a request

Call the workflow with ai.apis.run() in TypeScript, or hit /workflows/{workflow}/execute directly — params is passed through untouched either way.

These endpoints are addressed by workflow name rather than model id: the one in this model's header, since one model runs as one workflow. Authentication is unchanged — your Picsart API key as a bearer token (see Authentication).

ts
import { createClient, ApiRunMode } from '@picsart/ai-sdk';

const ai = createClient({
  apiKey: process.env.PICSART_API_KEY,
  apiUrl: 'https://api.picsart.com',
});

// Calls the 'picsart-flow/v1/effects' workflow directly — params are sent as-is.
const { result, usage } = await ai.apis.run('picsart-flow/v1/effects', {
  template: "your value here",
  imageUrls: [
    "your value here"
  ]
}, {
  mode: ApiRunMode.SYNC,
});

console.log(result); // workflow-specific output
console.log(usage?.credits); // credits charged

Parameters

4 parameters, sent inside params. These are the vendor's own names, so they line up one-for-one with the vendor's documentation. Required ones must be supplied; the rest fall back to their defaults.

ParameterTypeRequiredDefaultDetails
template
Effect template id from picsart-flow/v1/catalog/templates (the Magic Flow id the engine executes)
stringyes
imageUrls
User images, in slot order — exactly as many as the template's `meta.imageSlots` (1..3)
string[]yes
options
Platform GenAI options. `options.drive` saves the results to the user's Picsart Drive — name, attributes and folder are honored as-is. Safety checks do not apply here (no prompt; the engine moderates its own pipeline via `moderationLevel`)
objectno
safety_checks
Safety check settings
objectno
enabled
Whether to run content moderation. Defaults to true.
booleanno
drive
Save result to Picsart Drive
objectno
name
File name in Picsart Drive
stringyes
attributes
Custom attributes to attach to the file
objectno
folder
Target folder in Picsart Drive
objectno
moderationLevel
Content moderation strictness level. NONE means no moderation
stringno
nonelowmediumhigh

Response

Over HTTP the output arrives inside a status envelope, at response.result. ai.apis.run() unwraps that envelope for you and resolves to { result, usage } instead. Either way the resultitself is the vendor's own shape.

json
{
  "result": {
    "items": [
      {
        "url": "https://cdn.picsart.com/…/result.jpg",
        "type": "…",
        "driveFile": {
          "id": "wf_abc123"
        }
      }
    ]
  }
}