> ## Documentation Index > Fetch the complete documentation index at: https://nuntly.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve Domain > Returns a domain with its DNS record configuration and current verification status for each record. ## OpenAPI ````yaml /openapi.documented.yml get /domains/{id} openapi: 3.1.0 info: title: Nuntly REST API 1.x version: 1.0.0-alpha.20 description: Nuntly REST API definition termsOfService: https://nuntly.com/legal/terms-of-service contact: name: Nuntly Support url: https://nuntly.com/docs email: support@nuntly.com servers: - description: Nuntly API endpoint url: https://api.nuntly.com security: - bearerAuth: [] tags: - name: API Keys description: >- Create and revoke API keys used to authenticate requests to the Nuntly API. - name: Agents description: >- Read and write persistent state for an AI agent, optionally scoped to a specific inbox or thread. - name: Domains description: >- Add and verify sending and receiving domains. Manage DKIM records, SPF configuration, and enable inbound email routing. - name: Emails description: >- Send transactional emails, retrieve sending history, and track delivery status per message. - name: Inboxes description: >- Create email inboxes at a specific address on a verified receiving domain. Assign inboxes to namespaces or AI agents. - name: Messages description: >- Access received messages, download attachments, and send replies or forwards from an inbox. - name: Namespaces description: >- Isolate inboxes by tenant, client, or agent using namespaces. Use an external ID to map namespaces to your own data model. - name: Organizations description: >- Manage your organization profile, team members, and account-level settings. - name: Threads description: >- Browse email conversations grouped by subject. Mark threads as read or spam, and assign them to an agent. - name: Webhooks description: >- Register HTTP endpoints to receive real-time delivery events such as bounces, opens, and clicks. - name: Webhooks Events description: >- Inspect webhook event history and replay failed deliveries for debugging or recovery. - name: Webhooks Hook description: >- Endpoint your server implements to receive webhook events. Not a Nuntly API endpoint - this documents the shape your handler must accept. externalDocs: description: Nuntly API Documentation url: https://nuntly.com/docs paths: /domains/{id}: get: tags: - Domains summary: Retrieve Domain description: >- Returns a domain with its DNS record configuration and current verification status for each record. operationId: retrieve-domain parameters: - name: id in: path required: true description: The id of the domain schema: type: string responses: '200': description: Successful response. content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/DomainRecordsResponse' required: - data additionalProperties: false '500': description: An error response content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' x-codeSamples: - lang: cURL source: >- curl -X GET 'https://api.nuntly.com/domains/dns_01kabn43yqyxn2bx4ve84mczd3' \ -H 'Authorization: Bearer apk_xxx' - lang: JavaScript source: >- import { Nuntly } from '@nuntly/sdk'; const client = new Nuntly({ apiKey: process.env['NUNTLY_API_KEY'], }); const response = await client.domains.retrieve('dns_01kabn43yqyxn2bx4ve84mczd3'); - lang: Java source: >- import com.nuntly.sdk.Nuntly; import com.nuntly.sdk.ClientOptions; var nuntly = Nuntly.create(ClientOptions.builder() .apiKey(System.getenv("NUNTLY_API_KEY")) .build()); var response = nuntly.domains().retrieve("dns_01kabn43yqyxn2bx4ve84mczd3"); components: schemas: DomainRecordsResponse: type: object required: - id - name - createdAt - status - region - statusAt - sending - receiving - sendingStatus - sendingStatusAt - receivingStatus - receivingStatusAt - openTracking - clickTracking - records properties: id: description: The id of the domain type: string examples: - dns_01kabn43yqyxn2bx4ve84mczd3 name: description: The name of the domain to send e-mails' type: string examples: - example.com createdAt: description: Date at which the object was created (ISO 8601 format) type: string examples: - '2026-03-29T12:00:00.000Z' status: $ref: '#/components/schemas/DomainStatus' description: The status for the domain region: description: The region of the domain data type: string enum: - eu-west-1 statusAt: description: The date of the lastest verification of this record type: string sending: description: Whether sending is enabled for the domain type: boolean receiving: description: Whether receiving is enabled for the domain type: boolean sendingStatus: description: The sending status for the domain type: string enum: - enabled - disabled - paused sendingStatusAt: description: The date of the latest sending status change type: string receivingStatus: $ref: '#/components/schemas/DomainStatus' description: The receiving status for the domain receivingStatusAt: description: The date of the latest receiving status change type: string openTracking: description: Emit an event for each recipient opens an email their email client type: boolean examples: - true clickTracking: description: Emit an event for each time the recipient clicks a link in the email type: boolean examples: - true records: description: The DNS records for your domain. type: array items: type: object required: - name - fullname - recordType - ttl - group - value - status - statusAt properties: name: type: string fullname: type: string recordType: type: string enum: - TXT - MX - CNAME ttl: type: string group: type: string enum: - DKIM - SPF - MX - DMARC - MX_RECEIVING selector: type: string priority: type: string value: type: string status: $ref: '#/components/schemas/DomainStatus' statusAt: type: string ErrorResponse: type: object required: - error properties: error: $ref: '#/components/schemas/Error' description: >- This object provide you additional information about errors encountered while performing the operation DomainStatus: type: string enum: - bootstrapping - pending - success - failed - temporary_failure Error: type: object required: - status - code - title properties: status: description: >- The HTTP status code generated by the origin server for this occurrence of the error. type: number code: description: An API specific code representing the type of error. type: string title: description: A short, human-readable summary of the error type. type: string details: description: >- A (best effort) human readable explanation specific to this occurrence of the error. type: object additionalProperties: true securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Key (format apk_...) description: >- Use an API key from https://nuntly.com/api-keys. Required on every endpoint. ````