Introduction
The Submitator API launches your clients' products on up to 100 directories each, under your agency's brand.
Submitator API · v1
Launch every client from your code
Create a project for each client, launch it on up to 100 directories, and follow every listing until it is live. The work the console does, over REST and JSON.
The API is for agencies that sell directory listings to their own clients. You create a project from your client's URL, add a logo and a screenshot, and launch it. We submit the product to each directory and report every listing back to you.
Your client sees your brand: reports carry your agency's name, and the badge links to your site. You see every status, live link and proof in one place.
You can use it to
- Add a client by URL. Send the site's address and we fill in the name, tagline and description we find there. You add a logo, 1 to 5 screenshots and a contact email.
- Preview a launch before you spend. A free readiness call shows how many directories the project gets now, up to 100, and what would add more.
- Launch with one call. One launch picks up to 100 directories the project qualifies for and starts a listing at each.
- Track every listing. Read each listing's status and live link, or get every change pushed to your endpoint as a signed webhook.
- Build it for free. A test key runs every call in test mode: listings move on their own in about 15 minutes, and nothing is spent.
How a launch works
- You create a project. It stays a draft until you launch it, and a draft costs nothing.
- You launch it. That uses 1 launch from your balance and creates up to 100 listings, one per directory.
- Each listing moves from
pendingtolive, or endsnot_acceptedorcancelled. Most listings go live within a week.
How it works covers every status and the words these docs use.
Base URL
Every request goes to https://api.submitator.com/v1 with your key in the Authorization header. Requests and responses are JSON, ids are strings with a type prefix such as prj_, and times are ISO 8601 in UTC.
v1 is stable: a change that can break working code only ever ships in a new version. Versioning has the policy.