NetGrind API · unofficial, by Cotlet

Create your own NetGrind API

NetGrind: no public API, webhooks or Zapier app found on netgrind.online (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your NetGrind account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in NetGrind session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by NetGrind. NetGrind is a trademark of its owner. If NetGrind's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/quiet-players" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"realm": "Trading Foundations", "days": 7}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/quiet-players";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ realm: "Trading Foundations", days: 7 }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/quiet-players",
    headers={"Authorization": f"Bearer {key}"},
    json={"realm": "Trading Foundations", "days": 7},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "player": "Player Two",
      "last_quest": "Quest 3",
      "days_quiet": 9,
      "xp": 640
    },
    {
      "player": "Player Seven",
      "last_quest": "Quest 5",
      "days_quiet": 8,
      "xp": 1120
    }
  ]
}

01 Build

How do you build a NetGrind endpoint with Cotlet?

  1. Sign in to NetGrind in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List the Players in Trading Foundations with no Quest done in 7 days, with their last Quest and XP."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a Realm or a number of days, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in NetGrind session.

02 Endpoints

Example endpoints you could build for NetGrind

Cotlet ships no fixed list of NetGrind endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/quiet-players

    Quiet Players

    Players with no Quest done in the days you name, with their last Quest

  • POST /api/v1/custom/edge-cases

    Submissions waiting

    Submissions in the Judgement Hall, with Player and Quest

  • POST /api/v1/custom/leaderboard

    Leaderboard

    Top Players by XP for the week

  • POST /api/v1/custom/quest-stats

    Quest results

    Submissions and fails per Quest for a period

  • POST /api/v1/custom/add-shop-reward writes

    Add a Shop reward

    A new reward with its Gold price

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/quiet-players" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"realm": "Trading Foundations", "days": 7}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "player": "Player Two",
      "last_quest": "Quest 3",
      "days_quiet": 9,
      "xp": 640
    },
    {
      "player": "Player Seven",
      "last_quest": "Quest 5",
      "days_quiet": 8,
      "xp": 1120
    }
  ]
}

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

What can you use your NetGrind endpoints for?

  • Monday Cotlet endpoint Discord or email

    A Monday check-in list.

    Quiet Players sent to your Discord or email, so you can reach out.

  • Friday endpoint Post draft

    A leaderboard post.

    The top five by XP, ready for your weekly community post.

  • Weekly endpoint Google Sheets

    A sheet of your own.

    Quest results pulled into Google Sheets to see which Quest needs a rewrite.

  • Chat agent endpoint Player progress

    Your own community bot.

    A chat agent that checks a Player's progress before it answers them.

04 Access

What can an endpoint see and change?

An endpoint works in your own NetGrind session, so it can read and change only what your NetGrind login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as adding a Shop reward, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

05 Official API

Does NetGrind have an official API?

NetGrind: no developer docs, API keys or webhooks found on netgrind.online; its public pages name Discord as the integration (checked 20 Nov 2026). The full picture with sources: Does NetGrind have an API or MCP server?

Want ChatGPT or Claude to work in NetGrind instead of code? See the NetGrind MCP server.

06 Pricing

What does it cost?

per successful call
10 credits
when a call fails
0
in the smallest pack
≈ 500 calls
free trial, no card
7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

NetGrind API with Cotlet: questions

Is this an official NetGrind API?

No. Cotlet is independent and not affiliated with NetGrind. The endpoints you build run in your own signed-in NetGrind account.

Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

What happens when NetGrind changes its screens?

An endpoint works while NetGrind works the way it did when you built it. If NetGrind changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

Build your first NetGrind endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.