Skip to main content
This guide walks you from zero to a working watermark removal request. You need a GoStudio account and a Bearer token — there are no API keys to generate and no GoStudio SDK to install.

Step 1 — Get your Bearer token

The GoStudio API authenticates via a Supabase JWT issued when you log in. Read it from your Supabase Auth client, which holds the session for the signed-in user:
Tokens are Supabase JWTs that expire after approximately 1 hour, and the auth client refreshes them for you. Read the token from the client on each request rather than hardcoding it.
Always handle 401 unauthorized responses. Refresh the token through your auth client and retry the request.
For manual exploration only — never ship this, and never paste a token into a shared document or issue tracker.
  1. Open gostudio.ai and log in to your account.
  2. Press F12 to open DevTools → go to the Application tab.
  3. Expand Cookies → click https://www.gostudio.ai.
  4. Find the cookie named sb-<project-ref>-auth-token. Large sessions are split into numbered chunks (sb-<project-ref>-auth-token.0, sb-<project-ref>-auth-token.1, …) — concatenate their values in order.
  5. URL-decode the concatenated value to get the session JSON, then copy the access_token string. It starts with eyJ....
If the cookie format does not match what you see, get the token from your auth client instead — that is the supported path.

Step 2 — Verify your token and check model pricing

Before running any generation, confirm your token works and see which models you can use. GET /apps/watermark-remover/info does both — it is the cheapest call to prove your credentials, and it returns the current model IDs and their prices:
Expected response
Read pricing.credits rather than hard-coding a cost — it is what your account will be charged. If you see a 401, your token is invalid or expired; repeat Step 1.

Step 3 — Remove a watermark

Send a POST to /api/v2/apps/watermark-remover with an image URL and a model tier:
Expected response
The output_urls array contains the processed image(s), ready to use immediately. Treat the URLs as opaque — the hostname and path shape are not part of the contract, so do not hardcode or CSP-pin the host.

Next steps

Authentication

Learn about caller types and token expiry.

Watermark Remover Guide

Webhooks, model tiers, error handling, and more.