Sorry this took so long to get to! It’s possible we could take that URL-based approach, but I wanted to provide a way to authenticate with the API that would work in a wide array of situations, so I think the key-based approach makes the most sense. And that’s ready now!
You can now go to a special Application Keys page on your account to find your key, @dino. It’ll also explain how to integrate that into your apps.
The key should be kept secret, so if you’re making the backend code public, it’d be best to make this value configurable. Then individual users can add their own key (if you need one, reach out privately to @support, and we’ll generate one for you).