In the interest of providing a more robust, efficient response to the API Key approval process, I'm trialing a backend process that - if successful - should result in lower average wait times with any other impacts (resource utilization, et al) being invisible to most users.
To that end, potential API users should confirm their key issuance status here, and are strongly encouraged to check the Announcements forum on a regular basis to ensure compliance with any changes or updates.
Here's hoping this keeps us on a productive track for the foreseeable future.
Original Topic: Regarding Public Projects
As many of you may have noticed, we've changed the way we handle key issuance, to prevent excessive mirroring without artificially limiting end users. To that end, our developers are still tweaking key restrictions, but a few things should be noted.
- First and foremost, key pairs are being issued solely to developers going forward.
- End users should not be requesting keys on this forum, as legacy keys are no longer directly supported.
- Keys are issued in private/public combinatons.
- Private keys should be used once to mirror the entire dataset and should not be disclosed to the general public, as they are invalidated once they limit out.
- Public keys need not be obfuscated at all, as requests made using those are distinguished by true IPs.
- When in doubt - or in testing - run your codebase against an extremely limited set of data using your public key to check core functionality before mirroring with your private key. Legitimately malfunctioning code may be grounds for an adjustment, but excessive adjustments may lead to negative corrective measures. Please do your part to avoid this by resisting the urge to test on your private key.
Thank you for your time and consideration in this matter.