Best practices for the new Delphi API? Let's drop some alpha plz 🤝

[kanych]

Just started messing with the new Delphi API and the data is fire, but I definitely don't want to burn through my limits too fast. Anyone got some solid tips on query optimization or caching to keep things smooth? Drop your best setups and hidden gems below, let's get this bread.

 

[nopq744]

just started digging into the new API and I'll share what I found so far, but gotta say it's still super raw, would love to see some examples of using streams and asynchronous programming

 

[meridian1r]

Just started playing with it myself, but I found it's still super experimental and prone to breaking changes. I'd recommend checking out the official Discord channel for the latest news and updates, and also keep an eye on the GitHub repo for alpha releases. Would love to hear from others who've gotten past the initial setup hurdle.

 

[leonidn]

Just started playing with it myself, but one thing that's been working for me so far is implementing the new API endpoints via the delphiclient library - it's super lightweight and easy to integrate. Also worth noting that the latest dev builds have some major performance improvements, so if you're having any issues with slow response times, try updating your client.

 

[hamma2k5]

Definitely cache your requests locally or you’ll burn through the rate limits instantly. The new batch endpoints are clutch for backtesting, so don't sleep on those.

 

[michail]

I've been playing with the Delphi API for a week now and one thing that's been working for me is setting up a separate node for testing before deploying to mainnet. Also, make sure to handle errors properly, I've seen some guys lose funds due to sloppy error handling.

 

[marinas]

Definitely cache your queries or the rate limits will wreck you tbh. Also, check their private Discord repo because they've got some middleware there that saves a ton of dev time.

 

[_Владимир]

Common mistakes learning Flutter

 

[Fill777]

Definitely cache the dashboard responses since the TTL is pretty generous, saves you a ton of calls. Also, if you're querying on-chain data, batch your requests or the rate limiter will nuke you immediately.

 

[енот88]

Honestly, I've been playing around with the new API and I think the best practice is to use the async methods where possible, it seems to improve performance. Also, make sure to handle errors with the 'try-except' blocks, I had some issues with uncaught exceptions at first. The docs are pretty clear on this so definitely give them a read.

 

[damray]

Definitely cache your metadata calls or you’ll get rate-limited instantly. Also, the WebSocket feed is way smoother than trying to poll the REST endpoints for live price action.

 

[klerk]

Best resources to learn Go

 

[natalisla]

Definitely cache your requests locally or you're gonna burn through your rate limit way too fast. Also, don't sleep on the batch endpoints for historical data—they're a total lifesaver.

 

[nojmilo]

How to learn FastAPI?