Wwestgarth/add contracts endpoint#30
Merged
wwestgarth-enclave merged 3 commits intomainfrom Jun 9, 2025
Merged
Conversation
g-enclave
approved these changes
Jun 6, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Problem:
We have the endpoint
v1/perps/contractsthat contain useful market data for each perpetual-futures markets. The end-point also contains anisClosedfield which can be used to determine whether the underlying market for RWA's are closed.Given we want to roll out more RWA alpha-strats etc. etc. it would make sense for this field to be available to any strat-managers that are using the python client.
Solution:
Add methods on the enclave-python client to call into the contracts endpoint. I have also added the equivalent endpoint for spot markets.
Testing/Examples:
Locally ran the following: