Get Your MapsDaddy API Key
Create your MapsDaddy API key, keep it out of your code, test it with one GET /me request, and regenerate it straight away if it is lost or leaked.
4 min read
Your MapsDaddy API key lets your own scripts, CRM or automation tools use MapsDaddy without opening the dashboard. This guide shows you how to create the key, where to keep it, how to test it with one request, and what to do if it ever leaks.
What Your MapsDaddy API Key Does
Every API request sends your key in a header. We use it to find your account, check your balance and attach new lists to your dashboard. Anything you start through the API shows up in Lists & Exports, just like work you start by hand.
The API uses the same credits and the same prices as the dashboard. There's no API fee and no separate plan. That also means anyone who has your key can spend your credits, so treat it like a password.
Each account has one key. If you work in a team, everyone's integrations use that same key, so changing it affects all of them.
Who Can Create the Key
The API Key page sits in the sidebar for the account owner and for teammates with the Admin role. Members and Viewers don't see it. If you need a key and can't find the page, ask your owner or an Admin, or read Invite Your Team and Set Roles to see what each role can do.
Create Your Key
- Sign in to your dashboard.
- Click API Key in the sidebar.
- Click Generate API Key.
- Click Copy and paste the key somewhere safe right away.
Keys start with md_live_ followed by a long string of characters. If you ever spot a string like that in a file, a chat or a screenshot, you'll know what it is.
Tip: For your security, the full key is only shown once, right after you create it. Later the page only shows the start of it followed by dots. If you didn't copy it in time, regenerate a new one.
Keep It Out of Your Code
Most leaked keys are pasted straight into a script that later gets shared or pushed to a repository. Read the key from an environment variable instead. On macOS or Linux:
export MAPSDADDY_API_KEY="md_live_your_key_here"
On Windows PowerShell:
$env:MAPSDADDY_API_KEY = "md_live_your_key_here"
- If you keep the key in a
.envfile, add that file to.gitignore. - In hosted tools (serverless functions, CI, no-code platforms), use their secrets store rather than a plain text field.
- Keep the key on your server. Never put it in browser code or a mobile app, where anyone can read it.
- Don't send it by email, chat or in a support ticket. We never need it to help you.
Test Your Key With One Request
The Quick start card on the API Key page has a ready-made command, and it shows the Base URL with a copy button. The base URL is https://api.mapsdaddy.com/api/v1. The quickest test is GET /me, which returns your account and credit balance. It doesn't start anything or spend credits.
curl https://api.mapsdaddy.com/api/v1/me \
-H "Authorization: Bearer $MAPSDADDY_API_KEY"
If the key works, you get a 200 response with your id, name, email and credits.available. Check the balance matches what you see in the dashboard.
If the test fails
- 401: the key is missing, mistyped or was regenerated. The header must read
Authorization: Bearer, a space, then the full key with no extra quotes or line breaks. - 429: you went over the rate limit of 60 requests per minute. Every response carries rate-limit headers, so your script can see how many requests it has left and slow down before it hits the limit. If you do get a 429, wait a few seconds and try again.
- Empty variable: if you set the variable in one terminal and ran curl in another, the second one doesn't know about it.
The Recent requests table on the same page lists your API calls from the last 14 days, with the endpoint, status code and any error. It's the first place to look when something isn't working.
Regenerate a Lost or Leaked Key
If you lose the key, or think someone else has it, click Regenerate API Key and confirm with Regenerate. A new key is shown once, and the old key stops working immediately. That makes a leaked key useless, but it also breaks anything still using the old one. Work through this list:
- Copy the new key.
- Update it everywhere: scripts, servers, automation tools and any AI assistant connected through MCP.
- Restart long-running processes that read the key when they started.
- Run the
GET /metest again. - Look through Credit History for anything you don't recognise, and contact support if you find it.
What to Do Next
Once /me returns your balance, you're ready to start real work. Start a Google Maps Scrape With the API walks through a full example, and Connect AI Assistants With the MCP Server shows how an assistant like Claude can use the same key. Every endpoint is listed in the API documentation.
Ready to try it?
Start your export with MapsDaddy. No browser extension, Google account or API key needed.
Related Guides
Still stuck?
Our team usually replies the same day.