Marketing Miner

SEO keyword and website data from Marketing Miner.

Docs: https://profilers-api.marketingminer.com/docs (live OpenAPI at /openapi.json) Knowledge base: https://help.marketingminer.com/en/cat/data-api-profilers/ Base URL: https://profilers-api.marketingminer.com

Connection

An API token from your user profile section — not the general settings pages.

API access is plan-gated. Marketing Miner only issues a token on a paid plan with at least 1 million credits (Digger, Machine or Custom). On a smaller plan there is no token to copy.

That matters for support: the API answers 401 Invalid Credentials both for a genuinely wrong value and for an account without API access, so the two are indistinguishable from our side. The connection error names both causes rather than telling the user to re-copy a token that was never the problem.

Marketing Miner takes the token as an api_token query parameter, not a header. That's its documented design and this piece follows it — but it means the token travels in the request URL, so avoid pushing raw request URLs into downstream logging. TaskMagic stores the token itself as a secret, and trims it before use so a trailing newline from a copy-paste doesn't read as invalid.

The connection check deliberately sends a one-character keyword, which is below the documented 2–80 character minimum. The API validates the token before the parameters, so a 422 back proves the token works — without running a real lookup, which would bill 3 credits.

Actions

| Action | Endpoint | Docs | |---|---|---| | Get Keyword Search Volume | GET /keywords/search-volume-data | search volume | | Get Keyword Suggestions | GET /keywords/suggestions | suggestions | | Get Website Stats | GET /websites/stats | visibility | | Get Website Stats Over Time | GET /websites/stats-range | visibility |

That's the entire published surface — the OpenAPI document lists exactly these four endpoints.

Documented value sets

Everything with a fixed set of accepted values is a dropdown carrying exactly those values, so a user cannot guess wrong:

• Market (lang, required everywhere) — us, gb, cs, sk, pl, hu, ro. It's a market code, not a language name. uk and cz are the natural guesses for the UK and Czech markets and both are rejected; this field used to be free text suggesting them.
• Type — domain, subdomain, exact, prefix. url is not valid and used to be suggested.
• Suggestions Type — questions, new, trending.
• Scheme — http, https.

Include Keyword Data on suggestions is a Yes/No dropdown rather than a checkbox — an untouched checkbox saves as false and would silently strip the metrics for users who never opted out.

Period stays free text: the docs give monthly as an example but never publish the full set.

Costs

Search volume bills 3 credits per keyword and is rate-limited to 120 keywords per minute.

No triggers

All four endpoints are request/response lookups with no subscription and nothing resembling an event feed. The trigger anyone would want — "ranking changed" — would mean storing and diffing history ourselves, which is reimplementing a rank tracker rather than integrating one.