Get Funding Rate History

API Description

Retrieves historical funding rate data for perpetual contracts. This endpoint provides funding rate information including long and short funding rates at different timestamps, which is crucial for understanding the cost of holding positions in perpetual futures.

HTTP Request

GET /v4/public/mm/funding/history

Request Parameters

Parameter
Type
Required
Description

chainId

uint64

Yes

Chain ID (e.g., 143 for Monad mainnet)

symbol

string

Yes

Trading pair symbol (e.g., BTCUSDC)

startTime

uint64

No

Start time in Unix timestamp (seconds)

endTime

uint64

No

End time in Unix timestamp (seconds)

limit

uint32

No

Number of records to retrieve (default: 200, max: 200)

Important: Use symbol (singular) as the parameter name. startTime, endTime, and limit are optional.

Response Parameters

Parameter
Type
Description

timestamp

uint64

Funding rate timestamp (Unix timestamp in seconds)

long

string

Long position funding rate

short

string

Short position funding rate

Request Example

Python (requests)

Note: This endpoint requires API authentication. See Quick Start Guide for signature generation details.

Response Example

Success Response

Error Response

Notes

  • This endpoint requires API authentication (see Quick Start Guide)

  • Important: Use symbol (singular) as the parameter name

  • Only chainId and symbol are required; startTime, endTime, and limit are optional

  • If limit is not provided, it defaults to 200

  • startTime and endTime are in Unix timestamp format (seconds, not milliseconds)

  • Maximum limit is 200

  • Returns funding rates at 1-hour intervals

  • long: Funding rate for long positions (positive means longs pay shorts)

  • short: Funding rate for short positions (negative means shorts pay longs)

  • timestamp: Unix timestamp in seconds when the funding rate was applied

  • Funding rates are typically applied every 8 hours (00:00, 08:00, 16:00 UTC), but this endpoint returns hourly data

  • Rate limit: 120 requests per minute

  • Success response has code: 0 (not 200)

Common Errors

"invalid request parameters"

  • Ensure you're using symbol (singular) as the parameter name

  • chainId and symbol are required; other parameters are optional

  • startTime and endTime must be Unix timestamps in seconds (not milliseconds) if provided

Last updated