The Growwer API: link building and digital PR from your own software

Growwer now has an API. Everything you do on the platform, finding outlets for a project, getting a quote, placing the order, reviewing the draft and approving the post, can now run from your own software. That is 68 REST operations over the catalogue of more than 40,000 media outlets, orders, the managed service and the publisher side.

This article covers what it does, how SaaS products and marketing tools can integrate it, what an agency gains by plugging it into the way it works, and what publishers who sell on Growwer can do with it.

What the Growwer API is

It is the same platform you use on the web, opened up over HTTP. You authenticate with a key you create on your profile, send requests and get JSON back. There is no cut-down version: a key can do what your account can do on the web, no more and no less.

Area	What you can do
Projects	Create a project per website or per client, with its topic, language, country and keywords, and let Growwer analyse it to recommend outlets.
Catalogue	Search outlets with more than 30 filters that combine: DR, organic traffic and its trend, country, language, price, link type, whether they label the post as advertising, whether they list it on their homepage, or whether they rank for the project's keywords.
Orders	Get a quote, order, attach your own text, review and approve drafts, request changes and approve the delivery.
Managed service	See your campaigns, accept or reject the team's proposals and download their summary as a PDF.
Wallets and invoices	Check your balance, movements and invoices, and download them as PDFs.
Publishers	Register outlets, change prices, accept, reject and deliver orders, and check your withdrawals.

Using the API costs nothing extra. You pay for the posts you order, at the same price as on the web, from your account balance.

For SaaS products and tools: link building inside your product

If you run an SEO, content, reputation or AI visibility tool, your users already know what they are missing: links, media coverage, a presence in the sources ChatGPT cites. What they cannot do is fix it without leaving your product. With the API, the step after the diagnosis is a button.

Integration ideas

• Link audits. Your tool finds that a site has few referring domains compared with its competitors and, on the same screen, shows the catalogue outlets that match its topic, country and budget.
• Rank tracking. For each keyword you track, the outlets that already rank for it. The filter is in the API: it returns the outlets that rank for the project's keywords.
• AI visibility. If you measure whether a brand shows up in ChatGPT, Gemini or Perplexity answers, you can cross that with the outlets the platform links to those answers and suggest where to earn the mention. It is the shortest path from measuring GEO to improving it.
• AI writing. Your tool writes the article, uploads it as a proposed draft and orders it on the chosen outlet. The user only reviews and approves.
• CMS and online stores. A plugin that, when a new category or product goes live, suggests outlets to push it and leaves the order ready.
• AI agents. The full reference is in a file written for language models, so an agent can read it and work with Growwer without anyone explaining the API to it.

Two ways to connect it

1. With each user's account. The user creates a key on Growwer and pastes it into your tool, as with any other integration. They pay for their orders from their balance and you never touch their money. A read-only key is enough to show the catalogue and quotes; ordering needs a read and write key.
2. With your own account. You buy, with one project per client, and bill it inside your service at the price you choose.

If your users do not have an account yet, send them to sign up with your affiliate program link: you earn 12% of their first top-up.

What saves you engineering work

• A public OpenAPI contract, a Postman collection and official clients for TypeScript, Python, PHP, Go, Java, .NET and Ruby.
• No duplicate orders. Every write carries an idempotency key: if the connection drops and you retry, the order is not paid twice.
• A locked price. You get the quote first, which charges nothing, and the order is placed only at the price it gave you. If the outlet's price changes in between, nothing is charged.
• Errors with a stable code and 600 requests per minute per user, plenty for an integration in production.

This is a search for press outlets in Spain with a DR of 40 or more and a dofollow link:

curl "https://tool.growwer.com/api/v1/projects/$PROJECT/medias?websiteType=press&country=ES&minDomainRating=40&postLinkType=dofollow&limit=20" \
  -H "Authorization: Bearer $GROWWER_API_KEY"

And the quote for a post on one of them, before you order it:

curl -X POST "https://tool.growwer.com/api/v1/orders/estimate" \
  -H "Authorization: Bearer $GROWWER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "post",
    "projectId": "'$PROJECT'",
    "mediaId": "'$OUTLET'",
    "briefing": { "links": [{ "type": "dofollow", "targetUrl": "https://www.yourstore.com/", "anchor": "your store" }] }
  }'

The answer carries the price and whether your balance covers it. You place the order at that price and the API reports its status until the post goes live.

For agencies: your dashboard, your clients, no copy and paste

An agency that buys links for twenty clients spends hours on work that adds nothing: filtering the catalogue client by client, copying orders into a sheet, chasing statuses, downloading invoices at the end of the month. The API turns all of that into processes that run on their own and keeps the data where you already work.

• One project per client, created from your CRM or project tool the moment the contract is signed.
• Saved filters with your quality bar (minimum DR, traffic, maximum price, no advertising label) applied the same way to every client. The ones you save on the web work in the API too.
• Favourites and discards per project, so the client sees a shortlist and not a catalogue of thousands of outlets.
• Outlets the client asks for. If the client wants to appear on specific domains, you send up to 200 at once and Growwer looks for them for that project.
• Flash offers watched by a script, so you know when an outlet you want drops its price.
• Automatic reports. Orders and their status, with the published URL, flow into your Looker Studio, a spreadsheet or the client's monthly report without anyone copying them.
• Drafts and approvals in your own workflow: you download the draft, the client reviews it and you approve it or request changes through the API.
• PDF invoices ready for accounting, without logging in to find them.

If you use the managed service, the API lets you see the outlet proposals the team prepares, know what they would cost, accept or reject them with a comment and download the summary as a PDF to send to the client. Accepting charges nothing: the balance is used when the orders are placed.

An example of what an agency builds in an afternoon: every Monday, a script goes through its clients' projects, finds new outlets that match its saved filter, adds them to favourites and sends the consultant the list with a quote for each. The consultant decides; the machine does the searching.

For publishers: manage your whole catalogue at once

If you sell posts on several outlets, the API is for you too. A media group with dozens of titles can register all of its outlets in a loop, update prices when its rates change and apply the competitive price Growwer suggests on each one.

• Receive orders in your own editorial system, accept or reject them and deliver the published URL without opening the web.
• Deliver drafts and answer the buyer's change requests.
• Turn on holiday mode when the newsroom stops.
• Check your seller balance, its movements and the invoice of each withdrawal.

If you do not sell on Growwer yet, see how it works in sell articles.

What to know before you start

• Keys are shown once. They start with gw_sk_, can expire and can be revoked whenever you want. Store them like any other secret.
• Money moves on the web. Balance top-ups and withdrawal requests happen on Growwer; the API reads balances, movements and invoices, and pays for orders from the balance you already have.
• The catalogue has a daily cap. Accounts with a recent completed order can see 5,000 distinct outlets a day through the API; the rest get a trial quota of 100 until their first order. For an integration, one completed order is enough to get the full cap.
• Everything is documented, with examples in several languages and a reference for each operation generated from the contract itself.

How to start in five minutes

1. Create your Growwer account if you do not have one. It is free.
2. Create an API key on your profile, read-only to try it out.
3. Call GET /api/v1/me to check it works: it returns your account, your balances and your catalogue quota.
4. Follow the API documentation, or ask ChatGPT or Claude to read it for you with the buttons on the page.

To see where Growwer fits next to SEO data APIs, read our comparison of the best SEO APIs. And if you are weighing an integration in your product or your agency and want to talk it through with the team, get in touch.