Skip to content
ImageStep
Sign inGet a key

Support

Email support@imagestep.dev. ImageStep is built and run by one developer, so you are writing to the person who wrote the code — and which plan you are on decides how fast that person is expected to answer, not whether they do.

Include these and the first reply is usually the answer

  • The op you ran (resize, remove_bg, …) and the code from the error body — every failure carries one, along with retryable and the offending param.
  • The job id or asset id if you have one, and the time it happened, with a timezone.
  • The first eight characters of the API key you used — enough to identify the key. Never send the whole key: anyone holding it can spend your credit. If one has leaked, revoke it on API keys first and tell us afterwards.

Faster than an email

  • Quickstart · API reference · Errors, retries & limits — the error table there names every code and says which are worth retrying.
  • Synchronous ops if a call is slower than you expected: one image and a deterministic op does not need a job.
  • Billing, plan changes and cancellation are self-serve: switch, cancel or resume your plan, change the card and download invoices on the Billing tab of Usage & billing. Unused credit is refundable within 14 days — see terms and pricing, which also lists the support tier each plan includes.
  • A bug you can show in code (in an SDK, the CLI, the MCP server, the n8n node, or in what the API answered) is best filed on GitHub — it gets a version number and a public fix.

Security

Report a vulnerability to the same address with “security” in the subject and please do not open a public issue first. Include what you did, what you saw, and anything you had to be signed in as.