Parking API

The Parking API lets your own programs, scripts, and AI assistants work with your parked domains the same way you do on NamePros.

It can do what your account can do on the site, and nothing more: every request runs as you, with the permissions you gave the token.

What it covers

• Domains: list your domains, view one, read and change its settings, add, verify, ignore, and remove domains, and read the nameservers to set at your registrar.
• Account settings: read and change the settings that apply to all of your domains, and read the settings reference.
• Imports: your import history and the entries of each import.
• Inquiries: the inquiries buyers send, with the actions you have on the site (hide, restore, send to your email).

Base URL

https://www.namepros.com/api/v1/parking/

Requests and responses are JSON. Lists are paged with page and per_page, and every list answers with a pagination block (current_page, last_page, per_page, shown, total).

Domains are addressed by name (e.g., ?name=example.com), in Unicode or punycode.

Every request needs a token that belongs to you, sent in the Authorization header.

Authorization: Bearer npp_your_token

Personal tokens

Create one under "Your account" > "API access". Give it a name, choose exactly the permissions the program needs, and choose when it expires.

The token is shown once, when you create it. Store it like a password. You can revoke it at any time from the same page, and a revoked token stops working at once.

Connected apps

An app or AI assistant that supports "Connect to NamePros" gets its own access without you copying a token. You sign in, see what the app asks for, and allow or deny it. The app can only do what you allowed.

Connected apps are listed on the same "API access" page, where you can disconnect any of them at any time.

Note: a token gives the holder the same access you gave it. Never paste a token into a program you do not trust.

Replace npp_your_token with a personal token that has the permission each call needs.

List your domains

curl -H "Authorization: Bearer npp_your_token" \
  "https://www.namepros.com/api/v1/parking/domains?page=1&per_page=50"

View one domain

curl -H "Authorization: Bearer npp_your_token" \
  "https://www.namepros.com/api/v1/parking/domain?name=example.com"

Read a domain's settings

curl -H "Authorization: Bearer npp_your_token" \
  "https://www.namepros.com/api/v1/parking/domain-settings?name=example.com"

Change a domain's settings

Send only the settings you want to change. A value of null makes the domain inherit your account setting again.

curl -X POST \
  -H "Authorization: Bearer npp_your_token" \
  -H "Content-Type: application/json" \
  -d '{"settings": {"for_sale": true, "bin_price": 1500}}' \
  "https://www.namepros.com/api/v1/parking/domain-settings?name=example.com"

Nameservers for your registrar

curl -H "Authorization: Bearer npp_your_token" \
  "https://www.namepros.com/api/v1/parking/nameservers"

The reference lists every endpoint with its parameters and response.

Each endpoint needs one permission, named in the reference as its ability (e.g., domains.list). A token only has the abilities you gave it.

When you create a token you pick abilities in groups, so the common cases are one click:

• View domains: list and view domains, their nameservers, their settings and settings history.
• Add and remove domains: add, verify, ignore, and remove domains.
• Change domain settings: change a domain's settings and restore an earlier version.
• View account settings: your account settings, the settings reference, and your settings history.
• Change account settings: change your account settings and restore an earlier version.
• View imports: your imports and their entries.
• View inquiries: the inquiries buyers sent, including their names, email addresses, and messages.
• Manage inquiries: hide and restore inquiries, and have one sent to your email.

"Full parking access" ticks all of them. A connected app asks for the groups it needs, and you see them before you allow it.

Tip: give a program only what it needs. You can create another token with more later, under "API access".

Every settings change made through the API is saved as a version, exactly like a change made on the site. The version records which token made it.

• GET parking/settings-history lists the versions of your account settings.
• GET parking/domain-settings-history?name=example.com lists the versions of one domain's settings.
• POST parking/settings-restore with a history_id puts a version back.

Restoring creates a new version rather than deleting anything, so a restore can itself be undone. You can see the same history under "Parking" > "Settings" > "Settings history".

Errors use the standard NamePros API shape: an errors list where each entry has a code and a message.

• 401: the token is missing, revoked, or expired.
• 403: the token does not have the ability the endpoint needs. The message names the ability.
• 404: no domain, import, or inquiry by that name or id is in your account.
• 400: a parameter or setting value was refused. For settings, errors names each setting that failed.
• 429: you are making changes too quickly. Wait the number of seconds in the Retry-After header, then try again.

Requests are rate limited per token. Space out large jobs, and stop and wait when you receive a 429.

AI assistants that support MCP servers (e.g., Claude and ChatGPT) can use your parking account through the Parking MCP server. It uses this same API, with the permissions you allow.

Connecting an assistant

1. In the assistant, add a custom MCP server (also called a connector) with this URL:

   https://mcp.namepros.com/parking

2. The assistant sends you to NamePros to sign in. You see what it asks for and allow or deny it.
3. That's it! The assistant can now list your domains, read and change settings, and read inquiries, within what you allowed.

You can disconnect an assistant at any time under "API access". Settings changes made by an assistant are versioned like any other, so you can put an earlier version back.

Questions about the API, or something that does not work as described here? Post in the parking help thread and we will take a look.

When you report a problem, include the endpoint, the time, and the error code and message. Never include your token.