Closed Bug 1025153 Opened 11 years ago Closed 11 years ago

API key for the bug bounty Hall of Fame application

Categories

(Participation Infrastructure :: API Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: abiyani, Assigned: williamr)

Details

I am in process of developing a hall of fame application for the Mozilla web bug bounty program. One of the requirements is that only the bug reporters who belong to a curated mozillian group should be given recognition. As such I need an access to the Mozillian api key. The application is not yet deployed and hence I am unable to give the url of the application.
How long does it usually take to get approved?
OS: Mac OS X → All
Hardware: x86 → All
Sorry for the delay. To get approved for an API key, we just need to confirm two things. 1. Read the API data guidelines and let me know your application will follow those guidelines: http://mozillians.readthedocs.org/en/latest/api/api.html#using-api-data 2. Will your app be hosted on Mozilla infrastructure? That is a requirement for a 'reviewed'-level API key that lets your app know who belongs to a curated mozillians group. The Bug Bounty Hall of Fame application is a great way to use the mozillians API. Looking forward to seeing it!
Assignee: nobody → williamr
Status: NEW → ASSIGNED
Summary: Need api access for the bug bounty Hall of Fame application → API key for the bug bounty Hall of Fame application
No worries :) 1. Yes, I have read and understand that HoF application will follow these guidelines. 2. Yes, HoF would be hosted on Mozilla Infrastructure.
(In reply to abiyani from comment #3) > 1. Yes, I have read and understand that HoF application will follow these > guidelines. > 2. Yes, HoF would be hosted on Mozilla Infrastructure. Great! I have created an API key and sent it to you by email. Let me know if you have any questions, and please add a comment this bug with a link to the application when it's live.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.