API Key Updates

This is where you can request API access. Please be sure to mention what your use case is and if possible a link to the project.
Please provide a basic overview of your proposed use of the API.
Any request lacking this information will be denied pending an appropriate response.
Forum rules
API Keys (unique userpage)
Usergroups (request API Users access here after posting a new topic below)

Please provide a basic overview of your proposed use of the API.
Any request lacking this information will be denied pending an appropriate response.

Please do not request keys as end users of another project, as those projects should request and properly implement their own keys. Key requests of this nature will be removed in the interest of more efficiently handling project requests. Assistance may be available upon contact for projects experiencing issues utilizing the current API.
Locked
Leo_Pride
Posts: 630
Joined: Mon Apr 23, 2018 2:10 am

API Key Updates

Post by Leo_Pride »

Update: API Approvals
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
Hi all!

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.
Additionally, it's worth noting that application developers like Faith and CyberFox put a lot of heart and soul into their projects, so please respect that and let them know first when there seems to be an issue with keys, and we'll work something out with them to minimise interruptions.

Thank you for your time and consideration in this matter.
We're curious to see how new projects use TGDB API.
If you have a new public project, please provide a link to it so we can highlight cool new applications! 8-)

Locked