# Burn Chip

{% hint style="info" %}
Burns (destroys) a specified amount of in-game chips from a user.
{% endhint %}

**Endpoint:** `/game/chip/burn`\
**Method:** POST

{% tabs %}
{% tab title="Request Parameters" %}

```typescript
{
    chips: string[];    // Array of chip token addresses
    plyrIds: string[];  // Array of PLYR IDs to burn chips from
    amounts: number[];  // Array of amounts to burn
}
```

{% endtab %}

{% tab title="Success Response" %}

```typescript
{
	taskId: string;
	data: {
		transactionHash: string; // The hash of the burn transaction
	}
	status: string;
}
```

{% endtab %}

{% tab title="Error Response" %}

```typescript
{
  error: string;
  details?: any;
}
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
The \`chips\`, \`plyrIds\`, and \`amounts\` arrays must have the same length. Each index represents a burn operation.
{% endhint %}

## Example Usage

```javascript
// Setup request parameters
const timestamp = Date.now().toString();
const body = {
	chips: ['0x1234567890123456789012345678901234567890'], // Array of chip token addresses
	plyrIds: ['player123'], // Array of PLYR IDs to burn chips from
	amounts: [50] // Array of amounts to burn
};

// Generate HMAC signature
const hmac = generateHmacSignature(timestamp, body, secretKey);

// Make the API request
const response = await axios.post(apiEndpoint + '/game/chip/burn', body, {
	headers: {
		apikey: apiKey,
		signature: hmac,
		timestamp: timestamp
	}
});

// Process the response
console.log('Burn Task ID:', response.data.taskId);
console.log('Transaction Hash:', response.data.data.transactionHash);
```


---

# 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://dev.plyr.network/api-reference/assets/tokens-erc-20/in-game-chips-overview/burn-chip.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.