# sns\_getRegistrationTransaction

### Parameters <a href="#parameters" id="parameters"></a>

* **domain** `string` *required*: The domain name.
* **buyer** `string` *required*: The base58-encoded Solana public key of the buyer's paying wallet.
* **buyer\_token\_account** `string` *required*: The base58-encoded Solana public key of the buyer's paying token account.
* **space** `integer` *required*: The number of bytes to allocate in the new registered domain.
* **mint** `string` *optional*: The Solana public key of the Token mint used for payment, defaults to `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v` (USDC).
* **referrer\_key** `string` *optional*: The base58-encoded Solana public key of the registration referrer.

### Result <a href="#result" id="result"></a>

The result will be an RPCResponse JSON object with field:

* **result** `string`: The base64-encoded Solana Transaction object.

[<br>](https://sns.guide/sns-quicknode/sns_getFavouriteDomain.html)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sns.id/dev/sns-api/sns-quicknode-api/sns_getregistrationtransaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
