# Derivatives

Provides functionality to fetch details across **derivative** protocol.

Following are the common functions implemented for **derivative**:- 

| Name                  | Type | Description                                                                                                         |
| --------------------- | ---- | ------------------------------------------------------------------------------------------------------------------- |
| getorders             | Read | Users can fetch details for all orders corresponding to the specified address and the specified sub-account number. |
| getorder              | Read | Users can fetch details for a specific order using the specified order id.                                          |
| getfills              | Read | Users will be able to fetch the fill details of the order.                                                          |
| getassets             | Read | Users will be able to fetch a list of their assets deposited in dYdX.                                               |
| gethistoricalpnl      | Read | Users will be able to fetch their historical profit and loss.                                                       |
| getperpetualpositions | Read | Users will be able to fetch the position of an user.                                                                |
| getsubaccounts        | Read | Users will be able to fetch the details of a subaccount of a user.                                                  |
| gettransfers          | Read | User will be able to fetch the details of the transfer transaction.                                                 |


---

# 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.expand.network/integrations/derivatives.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.