# Parameters

#### GET /api/parameters

**Parameters:**

* **wallet (required) (query param)** → the wallet address of the user, who connected their wallet on the claim-portal
* **distributionId (required) (query param)** → id of the particular distribution to claim as returned in the allocation details response
* **hookId (optional) (query param)** → UUID of the claim hook. Required if the default hook is deactivated.

**Bad Responses:**

* 400 → returned if the wallet is not provided
* 400 → returned if the distributionId is not provided
* 400 → the claim window is not active
* 404 → the provided distribution is not found

**Ok Response:**

The valid response contains parameters that can directly be sent to the wallet for a signature. It contains:

* **from (string)** → signature wallet (should be the same as the provided wallet above)
* **to (string)** → address of the contract to execute against
* **data (string)** → data to send in the transaction

Example:

```json
{
	"from": "0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266",
	"to": "0xf03dfeecbafc5147241cc4c4ca20b3c9dfd04c4a",
	"data": "0x...."
}
```

Once the transaction is signed & submitted, TX status can be monitored and relayed to the end user per project’s own implementation and flows.

If you have any questions or need assistance - reach out the the Magna team!