
The Primeforge API lets teams manage Primeforge's Google Workspace and Microsoft 365 cold email infrastructure in code rather than through a dashboard. It is a good example of a wider category: email infrastructure APIs, which provision domains, DNS, mailboxes and workspaces, then hand those mailboxes to a sending platform. This guide summarises what the Primeforge API covers according to Salesforge's own help documentation, explains how email infrastructure APIs work in general, compares the documented capabilities with the LiteMail API, and lists the questions to ask before you build automation on any of them. We only report what each vendor publishes; where documentation is silent, we say so.
What Is the Primeforge API? The Short Answer
Primeforge is part of the Salesforge "Forge" family and provides Google Workspace and Microsoft 365 mailboxes for cold email. According to Salesforge's help article Primeforge API explained, the Primeforge API manages domains, DNS records, mailboxes, pre-warmed mailboxes, workspaces and exports to platforms such as Salesforge and Warmforge. The article points readers to the API documentation inside Salesforge (Settings → API & MCP) rather than a public URL.
Area | Documented Primeforge API capabilities |
|---|---|
Domains | Check availability, search, buy, transfer, list/retrieve, auto-renew on/off, forwarding |
DNS | View and manage DNS records; bulk DNS updates |
Mailboxes | List, retrieve, create, update, delete; cancel scheduled deletion; get OTP codes |
Pre-warmed mailboxes | Purchase and check availability |
Workspaces | List, create, retrieve, delete |
Exports | Export mailboxes to Salesforge, Warmforge or other supported platforms |
Billing | Adjust mailbox top-up amount |
💡 Key Takeaways
Infrastructure APIs like Primeforge's and LiteMail's automate the layer beneath your sequencer. They don't send campaigns themselves; they create and connect the mailboxes that do. Check authentication method, rate limits and export targets in the live docs before building.
How Email Infrastructure APIs Work
Every email infrastructure API, whatever the vendor, follows roughly the same lifecycle:
Workspace — a container for a client, brand or team.
Domains — bought through the API or connected from an existing registrar.
DNS — SPF, DKIM, DMARC, MX and forwarding records written automatically.
Mailboxes — Google Workspace or Microsoft 365 users created on those domains.
Warm-up or pre-warmed stock — either ramp new mailboxes or buy mailboxes with history.
Export — connect mailboxes to a sequencer (Instantly, Smartlead, Salesforge, Lemlist), ideally via OAuth.
Monitor — status, warm-up analytics, placement tests, webhooks.
Our companion guide SPF, DKIM and DMARC setup explains what the DNS step does, and Smartlead inbox setup shows the export step from the sequencer side.
Primeforge API vs LiteMail API: Documented Capabilities
Both are infrastructure APIs for Google Workspace and Microsoft 365 cold email mailboxes. This table compares only what each vendor documents publicly; "not stated" means we couldn't find it, not that it doesn't exist.
Capability | Primeforge API (per Salesforge help) | LiteMail API (per docs.litemail.ai) |
|---|---|---|
Domains: buy / connect | Buy, transfer, search availability | Purchase/register, connect domains, list assignable domains |
DNS management | View/manage, bulk update | Get, create, update, delete records; check DNS; add DMARC |
Mailboxes | Create, update, delete, OTP codes | Assign to domain, update, remove at renewal, details |
Pre-warmed | Purchase pre-warmed mailboxes | Pre-warmed inboxes and domains sold via plans |
Workspaces | List, create, retrieve, delete | List, create, update |
Exports | Salesforge, Warmforge, other platforms | Export mailboxes, connect inboxes to platforms |
Monitoring | Not stated in the help article | Warm-up analytics, placement tests, dashboard status counts |
Webhooks | Not stated in the help article | Register, list, delete webhooks |
Rate limit | Not stated in the help article | 5 requests/second soft limit; 429 on excess |
Public docs URL | Inside Salesforge (Settings → API & MCP) |
For the full LiteMail picture see the cold email infrastructure page and plans (API on Pro and Scale). Comparing providers more broadly? See LiteMail vs Zapmail, LiteMail vs Infraforge and the Mailforge alternative page.
Primeforge Constraints Worth Knowing
Salesforge's help article lists a few structural rules that affect automation design:
A Primeforge domain can hold up to 5 mailboxes.
Microsoft 365 domains need at least 3 mailboxes when first created; Google Workspace domains have no minimum.
Full API reference lives inside the Salesforge app rather than a public page.
Those rules matter for capacity planning: if you design around 2–3 mailboxes per domain, as many teams do (see how many inboxes you need), the Microsoft minimum shapes how you split providers. Our Google Workspace vs Microsoft 365 comparison helps you choose the mix.
What to Check Before Automating Any Email Infrastructure API
🔐Authentication and scopes
API keys vs bearer tokens, per-workspace access, key rotation.
⏱️Rate limits and retries
Documented limits, 429 handling, idempotency for purchases.
💳Billing side effects
Domain and mailbox purchases cost money; add confirmation steps in code.
📤Export targets
Which sequencers are supported, OAuth or SMTP, bulk export.
🧾DNS ownership
Can you export DNS and move domains later? See our domain risks guide.
📊Monitoring hooks
Webhooks, status endpoints, placement tests.
🧭Portability
Are mailboxes official Google/Microsoft accounts you can keep using elsewhere?
Teams building the sending side as well should pair this with a sequencer API; our email infrastructure for AI outbound platforms guide shows the full stack, and MCP servers for email infrastructure covers AI-assistant access to the same operations.
Example: Automating a Client Launch with an Infrastructure API
Illustrative workflow, vendor-neutral. An agency adds a client and wants mailboxes live the same day:
Step | Call (generic) | Guardrail |
|---|---|---|
1 | Create workspace | One workspace per client |
2 | Check and buy 3–4 domains | Human approval before purchase |
3 | Write SPF/DKIM/DMARC | Verify records before creating mailboxes |
4 | Create or buy pre-warmed mailboxes | Respect per-domain mailbox caps |
5 | Export to sequencer | OAuth; per-inbox daily caps set on arrival |
6 | Register monitoring | Alerts on bounce or placement drops |
Agencies can read the cold email agency setup guide, client onboarding and LiteMail for agencies for the operational side.
APIs Don't Fix Deliverability on Their Own
Automation makes it easy to create hundreds of mailboxes — and just as easy to burn them. Keep per-inbox volume low (safe sending limits), verify lists (verification tools), warm or buy pre-warmed inboxes, and monitor reputation with Google Postmaster Tools. Our deliverability guide covers the fundamentals.
What Most Primeforge API Write-Ups Miss
Most pages about the Primeforge API stop at the endpoint list. When you evaluate any email infrastructure API, three operational questions matter more than the number of endpoints:
Question | Why it matters | Where to look |
|---|---|---|
How are DNS changes verified? | Bad DNS breaks authentication silently | DNS check endpoints; compare with Google Workspace domain setup |
What happens at export? | OAuth vs app passwords changes stability | |
How is health exposed? | You need data to pause inboxes early | Status, warm-up and placement endpoints; Postmaster data |
How portable are mailboxes? | Switching sequencers shouldn't mean rebuilding |
Also plan for scale: per-domain mailbox caps change how many domains you buy (pre-warmed inbox formula, inbox network sizing), and agencies need per-client isolation (agency domain scaling). Microsoft-heavy lists need properly configured Microsoft 365 mailboxes (common Microsoft 365 mistakes) — another reason to check how an API handles DKIM for each provider.
LiteMail: An Alternative Infrastructure API
LiteMail | Infrastructure API with public docs
API on Pro and Scale plans
Domains, DNS, mailboxes, workspaces, exports, placement tests and webhooks
LiteMail provisions official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs. Its public API documentation covers domains, DNS, mailboxes, workspaces, exports to sending platforms, placement tests and webhooks, with a documented 5 requests/second soft limit. Pre-warmed domains and pre-warmed inboxes are available alongside fresh inboxes from $2.50.
Strengths | Keep in mind |
|
|
Read the LiteMail API Docs → Compare infrastructure APIs on documentation, portability and monitoring — not just price. See LiteMail Plans →
Frequently Asked Questions
What is the Primeforge API?
It is Primeforge's API for managing its cold email infrastructure — domains, DNS, mailboxes, pre-warmed mailboxes, workspaces and exports — programmatically, according to Salesforge's help documentation.
Where are the Primeforge API docs?
Salesforge's help article says the documentation is available inside Salesforge under Settings → API & MCP.
Can the Primeforge API export mailboxes to other tools?
The help article says it can export mailboxes to Salesforge, Warmforge and other supported platforms.
How many mailboxes can a Primeforge domain have?
The help article states up to 5 mailboxes per domain, with a minimum of 3 when creating Microsoft 365 mailboxes on a domain.
Does the Primeforge API support pre-warmed mailboxes?
Yes, the help article lists purchasing pre-warmed mailboxes and checking availability.
Is there an alternative infrastructure API with public docs?
LiteMail publishes its API documentation at docs.litemail.ai, covering domains, DNS, mailboxes, workspaces, exports, placement tests and webhooks.
Do infrastructure APIs send cold emails?
Generally no. They create and connect mailboxes; sequencers send campaigns. See AI outbound infrastructure.
What should I check before choosing an email infrastructure API?
Authentication, rate limits, billing safeguards, export targets, DNS portability, monitoring endpoints and whether mailboxes are official Google or Microsoft accounts.
Build on Infrastructure You Can Inspect
LiteMail's public API covers domains, DNS, Google Workspace and Microsoft 365 mailboxes, workspaces and exports, on dedicated US and EU IPs.
Public API docs · Automated DNS · Export to your sequencer
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Cold Email Infrastructure · Scaling to 500 Inboxes · Agency Infrastructure Guide · LiteMail vs Infraforge · Mailforge Alternative · Bulk Email Inboxes


