Integration
Connect CloudConvert to Marketplace Fee Data
When something happens in CloudConvert, your agent does the next thing in Marketplace Fee Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CloudConvert and Marketplace Fee Data to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with CloudConvert and Marketplace Fee Data
Triggers and actions 2 triggers ยท 6 actions
Trigger
Job FailedTriggers when a job failed.
Trigger
Job FinishedTriggers when a job finished.
Action
Capture a WebsiteCreates job to capture a website as PDF or create a website screenshot as JPG or PNG.
Action
Convert a FileCreates job to convert a file.
Action
Get file metadataExtract metadata (e.g. page count, dimensions, duration) from a file (metadata operation task).
Action
Get jobLook up the status and results of a conversion job by ID (GET /v2/jobs/{id}).
Action
Get marketplace fees by platformRetrieve the published fee schedule (percentage rates and fixed charges) for one named marketplace or payment processor, e.g. Etsy or Stripe (GET /data/fees/{platform}.json).
Action
List all marketplace feesRetrieve the full fee schedule dataset for all 21 supported marketplaces and payment processors in one document (GET /data/fees.json).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.