> ## Documentation Index > Fetch the complete documentation index at: https://docs.name.com/llms.txt > Use this file to discover all available pages before exploring further. # Create Account > Creates a new sub-account under your authenticated reseller account and returns API credentials for the new account. This endpoint is only available to approved reseller accounts. Contact name.com support to request access. ## OpenAPI ````yaml post /core/v1/accounts openapi: 3.1.0 info: contact: email: reseller@name.com name: Reseller Account Services description: >- RESTful API for managing domains, DNS records, and related services at name.com. Access via HTTPS at api.name.com (production) or api.dev.name.com (testing). Supports standard authentication, rate-limited to 20 requests/second. title: name.com Core API version: 1.34.0 termsOfService: https://www.name.com/policies/api-access-agreement servers: - description: Testing url: https://api.dev.name.com security: - BasicAuth: [] tags: - name: Hello description: >- Use the Hello endpoint to verify that your API connection and credentials are working properly. This simple call returns a success message (along with server time and version info) to confirm the API is reachable and authenticated. - name: Account Info description: >- Use Account Info endpoints to retrieve basic information about your name.com account. For example, you can check your account’s current credit balance and other account details using these endpoints. - name: Accounts description: >- Use Accounts endpoints (available upon request) to manage sub-accounts under your main account. For example, resellers can programmatically create new customer accounts with their own login credentials and permissions. - name: Domains description: >- Use Domains endpoints to search for domain availability, register new domains, and manage existing domains. - name: Contact Verification description: >- Use Contact Verification endpoints to query a reseller’s unverified domains/emails and to programmatically mark an end user’s email as verified if the reseller has already completed the verification process. These endpoints help resellers meet ICANN requirements by ensuring end users confirm they can receive email at their listed address. - name: DNS description: >- Use DNS endpoints to manage DNS records for your domains. You can list all existing DNS records for a domain and create, update, or delete records as needed. - name: DNSSECs description: >- Use DNSSEC endpoints to configure DNS Security Extensions for your domains. These endpoints allow you to add, retrieve, or remove DNSSEC records. - name: Email Forwardings description: >- Use Email Forwardings endpoints to set up and manage email forwarding addresses on your domains. - name: URL Forwardings description: >- Use URL Forwardings endpoints to control URL redirection settings for your domains. - name: Vanity Nameservers description: >- Use Vanity Nameservers endpoints to configure custom nameserver hostnames (glue records) for your domains. - name: Transfers description: >- Use Transfers endpoints to move domains into your name.com account. Start by creating a transfer request for inbound transfers from **external** registrars, then monitor and manage the status of pending transfers. Use **internal transfer in** to pull a domain from another name.com account into your reseller account (enterprise allowlist; requires auth code from the losing account’s dashboard). You can cancel an incoming transfer if needed, or cancel an outbound transfer (domain leaving name.com) via the external transfer-out cancel endpoint. Use the **transfer eligibility** endpoint to check whether a domain is currently at name.com before initiating a transfer, so you can route to the correct flow (external vs internal transfer). - name: Orders description: Use Orders endpoints to review and track purchases made via the API. - name: Refunds description: > Use the Refunds endpoint to delete eligible domains and advanced security products during the Add Grace Period (AGP) and automatically issue refunds for the associated order items. You can use the List Orders endpoint to retrieve order IDs, then pass those IDs into the Refunds endpoint to process eligible deletions and refunds. This endpoint enforces AGP delete limits and supports only domain registrations and advanced security add-ons. Refunds are issued to the original payment method on file. If the original payment method is unavailable, the refund will be credited to the account balance. - name: Webhook Notifications description: > Use Webhook Notification endpoints to subscribe to real-time notifications for account and domain events. This keeps your application updated on important changes without polling the API. Outbound webhook POSTs include an `X-NAMECOM-SIGNATURE` header. HMAC uses one API v4 token per account, chosen deterministically when multiple tokens exist (see HMAC Signature Verification in the developer docs). The signing input format is unchanged. - name: Domain Info description: >- Use Domain Info endpoints to retrieve information about TLD-specific requirements and registration rules. These endpoints help you understand what fields, documents, or constraints are needed to successfully register domains across different TLDs. - name: TLD Pricing description: >- Use TLD Pricing endpoints to retrieve general pricing information for your account. - name: Premium Domains description: APIs for working with Premium Domains. paths: /core/v1/accounts: post: tags: - Accounts summary: Create Account description: >- Creates a new sub-account under your authenticated reseller account and returns API credentials for the new account. This endpoint is only available to approved reseller accounts. Contact name.com support to request access. operationId: CreateAccount requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateAccountRequest' description: >- CreateAccountRequest has the information that is needed to create an account with the CreateAccount function. required: true responses: '200': description: >- A successful response containing the newly created account details and credentials. content: application/json: schema: $ref: '#/components/schemas/CreateAccountResponse' '400': description: >- Bad request - Invalid query or request body parameters. Account creation requeires both TOS and APITOS values to be true. content: application/json: schema: $ref: '#/components/schemas/InvalidArgument400' '401': description: Unauthorized. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Unauthorized '403': description: Forbidden - you do not have permission to perform this action. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Permission denied details: type: - string - 'null' description: Additional context or information about the error example: Failed authentication '405': description: Method not allowed. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Method Not Allowed '415': description: >- All POST, PUT, PATCH requests for this API must include the `Content-Type: application/json` header in the requests. content: application/json: schema: $ref: '#/components/schemas/UnsupportedMedia415' '429': description: Rate limit has been exceeded. content: application/json: schema: type: object required: - message - details properties: message: type: string description: >- ### Too Many Requests You have exceeded the rate limit. **Headers returned:** * 'X-RateLimit-Reset': An integer (UTC epoch) indicating when you can retry. example: Rate Limit Exceeded headers: x-ratelimit-reset: description: >- Unix timestamp for the time at which the current rate limit will reset. schema: type: number example: 1747668270 '500': description: Internal server error. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: Internal Server Error details: type: - string - 'null' description: Additional context or information about the error. example: Something went wrong. '502': description: Bad Gateway content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: >- The server received an invalid response from the upstream server. '503': description: >- Service Unavailable — returned during scheduled maintenance when the API is offline. See https://status.name.com for updates. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: Service Unavailable details: type: - string - 'null' description: Additional context or information about the error. example: >- The API is offline for scheduled maintenance. See https://status.name.com for updates. '504': description: Gateway Timeout content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: The upstream server is taking too long to respond. components: schemas: CreateAccountRequest: description: >- CreateAccountRequest has the information that is needed to create an account with the CreateAccount function. type: object required: - account - apiTos - tos properties: account: $ref: '#/components/schemas/AccountRequest' description: The account details for the new account being created. apiTos: title: ApiTos indicates accepted API Terms of Service agreement description: >- Must be set to true to indicate acceptance of the API Terms of Service. type: boolean example: true tos: title: Tos indicates accepted Terms of Service agreement description: >- Must be set to true to indicate acceptance of the general Terms of Service. type: boolean example: true example: account: accountName: reseller_subaccount password: SecureP4ss! contacts: registrant: firstName: Jane lastName: Doe address1: 123 Main St. city: Denver state: CO zip: '12345' country: US phone: '+13035551212' email: admin@example.net apiTos: true tos: true CreateAccountResponse: description: >- CreateAccountResponse contains information about the newly created account and the API credentials generated for it. type: object required: - accountName - apiToken - apiTokenName properties: accountName: description: >- AccountName is the unique user-assigned name of newly created account. type: string example: new_reseller_account apiToken: title: ApiToken secret hash to make api requests description: >- The authentication token that should be used to access the API. This value is only returned once upon account creation. type: string format: password example: a1b2c3d4-e5f6-7890-abcd-ef1234567890 apiTokenName: description: ApiTokenName user assigned name of api token. type: string example: my_reseller_token example: accountName: new_reseller_account apiToken: a1b2c3d4-e5f6-7890-abcd-ef1234567890 apiTokenName: my_reseller_token InvalidArgument400: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: Bad Request details: type: - string - 'null' description: Additional context or information about the error example: '''domainName'' cannot be null' UnsupportedMedia415: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: >- The 'Content-Type' header must be 'application/json' for this request. AccountRequest: description: >- Account lists all the data for an account. This schema is used for requests. allOf: - $ref: '#/components/schemas/Account' - type: object properties: contacts: $ref: '#/components/schemas/ContactsRequest' description: Contact information associated with this account. Account: description: Account lists all the data for an account. type: object properties: accountId: description: AccountId is the unique id of account. format: int32 type: integer example: 12345 accountName: description: >- AccountName is the unique name of the account. Minimum length is 6 characters, maximum length is 60. type: string minLength: 6 maxLength: 60 example: namecom_reseller autoRenew: title: AutoRenew reflects account setting auto renew description: >- When set to true, domains in this account will be automatically renewed before expiration. type: boolean default: true contacts: $ref: '#/components/schemas/Contacts' description: Contact information associated with this account. createDate: description: CreateDate is the date the account was created. type: string format: date-time example: '2023-04-01T12:00:00Z' password: description: >- Password has minimum length of 7 characters. It must contain at least 1 letter and at least 1 number/symbol. type: string format: password minLength: 7 ContactsRequest: description: >- Contacts stores the contact information for the roles related to domains. This schema is used for requests. properties: admin: $ref: '#/components/schemas/ContactRequest' billing: $ref: '#/components/schemas/ContactRequest' registrant: $ref: '#/components/schemas/RegistrantContactRequest' tech: $ref: '#/components/schemas/ContactRequest' type: object Contacts: description: >- Contacts stores the contact information for the roles related to domains. properties: admin: $ref: '#/components/schemas/Contact' billing: $ref: '#/components/schemas/Contact' registrant: $ref: '#/components/schemas/RegistrantContact' tech: $ref: '#/components/schemas/Contact' type: object ContactRequest: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for creating and updating contacts (POST/PUT requests) and includes all validation requirements. All fields listed in the `required` array must be provided and cannot be null or empty. allOf: - $ref: '#/components/schemas/Contact' - type: object properties: firstName: description: First name of the contact. type: string example: John minLength: 1 lastName: description: Last name of the contact. type: string example: Doe minLength: 1 address1: description: The first line of the contact's address. type: string example: 123 Main Street minLength: 1 city: description: City of the contact's address. type: string example: New York minLength: 1 state: description: State or Province of the contact's address. type: string example: NY minLength: 1 zip: description: >- ZIP or Postal Code of the contact's address. This field is required and must be a non-empty string. type: string example: '10001' minLength: 1 country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: string example: US pattern: ^[A-Z]{2}$ email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: string format: email example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: string pattern: ^\+[1-9]\d{7,14}$ example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' pattern: ^\+[1-9]\d{7,14}$ example: '+15557654321' required: - firstName - lastName - address1 - city - state - zip - country - email - phone RegistrantContactRequest: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for creating and updating contacts (POST/PUT requests) and includes all validation requirements. All fields listed in the `required` array must be provided and cannot be null or empty. allOf: - $ref: '#/components/schemas/RegistrantContact' - type: object properties: firstName: description: First name of the contact. type: string example: John minLength: 1 lastName: description: Last name of the contact. type: string example: Doe minLength: 1 address1: description: The first line of the contact's address. type: string example: 123 Main Street minLength: 1 city: description: City of the contact's address. type: string example: New York minLength: 1 state: description: State or Province of the contact's address. type: string example: NY minLength: 1 zip: description: >- ZIP or Postal Code of the contact's address. This field is required and must be a non-empty string. type: string example: '10001' minLength: 1 country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: string example: US pattern: ^[A-Z]{2}$ email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: string format: email example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: string pattern: ^\+[1-9]\d{7,14}$ example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' pattern: ^\+[1-9]\d{7,14}$ example: '+15557654321' required: - firstName - lastName - address1 - city - state - zip - country - email - phone Contact: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for API responses and may contain null values for legacy data. For creating or updating contacts, use ContactRequest which enforces all validation requirements. type: object properties: firstName: description: First name of the contact. type: - string - 'null' example: John lastName: description: Last name of the contact. type: - string - 'null' example: Doe companyName: description: >- Company name of the contact. Leave blank if the contact is an individual, as some registries may assume it is a corporate entity otherwise. type: - string - 'null' example: Example Inc. address1: description: The first line of the contact's address. type: - string - 'null' example: 123 Main Street address2: description: The second line of the contact's address (optional). type: - string - 'null' example: Suite 400 city: description: City of the contact's address. type: - string - 'null' example: New York state: description: State or Province of the contact's address. type: - string - 'null' example: NY zip: description: ZIP or Postal Code of the contact's address. type: - string - 'null' example: '10001' country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: - string - 'null' example: US email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: - string - 'null' example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15557654321' isVerified: description: >- Indicates if the contact has been verified as per ICANN requirements. If the value is `false` it indicates that the contact has not completed the required verification process. This property is read-only and will be included in responses but should not be included in requests. type: boolean example: true readOnly: true verificationId: description: >- When the contact is unverified, this is the ID of the pending verification record. Use this ID with the resend verification email and verify contact endpoints. Omitted or null when the contact is verified. type: - integer - 'null' format: int64 example: 12345 readOnly: true RegistrantContact: description: >- Contact contains all relevant contact data for a domain registrant. This schema is used for API responses and may contain null values for legacy data. For creating or updating contacts, use RegistrantContactRequest which enforces all validation requirements. type: object properties: firstName: description: First name of the contact. type: - string - 'null' example: John lastName: description: Last name of the contact. type: - string - 'null' example: Doe companyName: description: >- Company name of the contact. Leave blank if the contact is an individual. Please be advised that ICANN policy links the "Company Name" field (Organization) in your domain's contact details to its legal ownership. If this field contains information, the listed organization is considered the legal "Registered Name Holder" (domain owner). type: - string - 'null' example: Example Inc. address1: description: The first line of the contact's address. type: - string - 'null' example: 123 Main Street address2: description: The second line of the contact's address (optional). type: - string - 'null' example: Suite 400 city: description: City of the contact's address. type: - string - 'null' example: New York state: description: State or Province of the contact's address. type: - string - 'null' example: NY zip: description: ZIP or Postal Code of the contact's address. type: - string - 'null' example: '10001' country: description: >- Country code for the contact's address. Must be an ISO 3166-1 alpha-2 country code. type: - string - 'null' example: US email: description: >- Email address of the contact. Must be a valid email format. The validation is performed against the `addr-spec` syntax in [RFC 822](https://datatracker.ietf.org/doc/html/rfc822) type: - string - 'null' example: john.doe@example.com phone: description: >- Phone number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15551234567' fax: description: >- Fax number of the contact. Should follow the E.164 international format: "+[country code][number]". type: - string - 'null' example: '+15557654321' isVerified: description: >- Indicates if the contact has been verified as per ICANN requirements. If the value is `false` it indicates that the contact has not completed the required verification process. This property is read-only and will be included in responses but should not be included in requests. type: boolean example: true readOnly: true verificationId: description: >- When the contact is unverified, this is the ID of the pending verification record. Use this ID with the resend verification email and verify contact endpoints. Omitted or null when the contact is verified. type: - integer - 'null' format: int64 example: 12345 readOnly: true securitySchemes: BasicAuth: scheme: basic type: http description: >- Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic ' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com. ````