name.com Core API Python Library
Official SDK for the name.com Core API.
List endpoints are paginated: use the page and perPage query parameters.
Responses include totalCount, nextPage, and lastPage, and most list
endpoints also return a Link header with next/prev/last URLs.
Write endpoints that accept an idempotency key are safe to retry — reusing the same key returns the original result instead of repeating the operation.
See https://docs.name.com for full guides and the API reference.
Table of Contents
- Documentation
- Installation
- Reference
- Usage
- Environments
- Async Client
- Exception Handling
- Advanced
- Contributing
Documentation
API reference documentation is available here.
Installation
pip install namecom-core-api
Reference
A full reference for this library is available here.
Usage
Instantiate and use the client with the following:
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.hello()
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.account_info.check_account_balance()
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.domains.search(
keyword="mydomain",
)
from namecom_core_api import Namecom, DomainCreatePayload
client = Namecom(
username="<username>",
password="<password>",
)
client.domains.create_domain(
domain=DomainCreatePayload(
domain_name="example.com",
),
)
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.domains.list_domains()
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.domains.get_domain(
domain_name="example.com",
)
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.dns.list_records(
domain_name="domainName",
)
from namecom_core_api import Namecom
client = Namecom(
username="<username>",
password="<password>",
)
client.dns.create_record(
domain_name="domainName",
answer="answer",
host="host",
type="A",
)
Environments
This SDK allows you to configure different environments for API requests.
from namecom_core_api import Namecom
from namecom_core_api.environment import NamecomEnvironment
client = Namecom(
environment=NamecomEnvironment.SANDBOX,
)
Async Client
The SDK also exports an async client so that you can make non-blocking calls to our API. Note that if you are constructing an Async httpx client class to pass into this client, use httpx.AsyncClient() instead of httpx.Client() (e.g. for the httpx_client parameter of this client).
import asyncio
from namecom_core_api import AsyncNamecom
client = AsyncNamecom(
username="<username>",
password="<password>",
)
async def main() -> None:
await client.hello()
asyncio.run(main())
Exception Handling
When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.
from namecom_core_api.core.api_error import ApiError
try:
client.hello()
except ApiError as e:
print(e.status_code)
print(e.body)
Advanced
Access Raw Response Data
The SDK provides access to raw response data, including headers, through the .with_raw_response property.
The .with_raw_response property returns a "raw" client that can be used to access the .headers and .data attributes.
from namecom_core_api import Namecom
client = Namecom(...)
response = client.with_raw_response.hello()
print(response.headers) # access the response headers
print(response.status_code) # access the response status code
print(response.data) # access the underlying object
Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
Which status codes are retried depends on the retryStatusCodes generator configuration:
legacy (current default): retries on
recommended: retries on
- 408 (Timeout)
- 409 (Conflict)
- 429 (Too Many Requests)
- 502 (Bad Gateway)
- 503 (Service Unavailable)
- 504 (Gateway Timeout)
Use the max_retries request option to configure this behavior.
client.hello(request_options={
"max_retries": 1
})
Timeouts
The SDK defaults to a 60 second timeout. You can configure this with a timeout option at the client or request level.
from namecom_core_api import Namecom
client = Namecom(..., timeout=20.0)
# Override timeout for a specific method
client.hello(request_options={
"timeout": 1
})
Custom Client
You can override the httpx client to customize it for your use-case. Some common use-cases include support for proxies
and transports.
import httpx
from namecom_core_api import Namecom
client = Namecom(
...,
httpx_client=httpx.Client(
proxy="http://my.test.proxy.example.com",
transport=httpx.HTTPTransport(local_address="0.0.0.0"),
),
)
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!
Metadata
Release files for namecom-core-api 1.36.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| namecom_core_api-1.36.4.tar.gz | 178.3 kB | With provenance | Details for namecom_core_api-1.36.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| namecom_core_api-1.36.4-py3-none-any.whl | Python 3 | none | any | Details for namecom_core_api-1.36.4-py3-none-any.whl |
Total release size: 492.2 kB
Release files / namecom_core_api-1.36.4.tar.gz
| Download URL | namecom_core_api-1.36.4.tar.gz |
|---|---|
| Size | 178.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea461e8b794d82595f54238cd34cf7f7e91d01fa6c297671aa95766218ec9ef9
|
|
BLAKE2b-256 checksum How to use checksums |
ba3972f6067c73b428132660e3e43e872ecb2d142f4032f3747770b9bcde240a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / namecom_core_api-1.36.4-py3-none-any.whl
| Download URL | namecom_core_api-1.36.4-py3-none-any.whl |
|---|---|
| Size | 313.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e81941304b018962515bb4aae3d5adbc46c45eee45f3d53c19b58a59e704437a
|
|
BLAKE2b-256 checksum How to use checksums |
fd8e4a9f3bf314a675639c19e22c39fc441cbaf6a5b06d0efcf1ebe0f79c14a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for namecom-core-api 1.36.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for namecom_core_api-1.36.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.