Apps/API

This page contains all of the important details for the Marketplace Submission API.

Elevator Pitch

The goal of the Marketplace Submission API is to:

• provide individual developers with a way to push single apps to the marketplace.
• provide app workshops with a way to push many apps to the marketplace, on behalf of their customers.

Overview

• Prod URL: TBD
• Stage URL: TBD
• Code Repo: https://github.com/mozilla/zamboni
• Code: Python / Django
• Dev Team: andym (Marketplace side); zalun (dev ecosystem side)
• IRC Channel: #amo on irc.mozilla.com

Meetings

• Kickoff meeting, 5/3/2012

Status

Submission API version 1 done on Marketplace side.

Next steps:

• zalun to implement client API in Python

Previously:

• define necessary API calls and their order of implementation (fwenzel, andym)
  • file implementation bugs accordingly (fwenzel)
• implement said API calls (andym)
• document them on MDN (andym + ?)
• implement client API (reference AMO's client API) (zalun)

Target time frame:

• 2 weeks for very simple, initial API

Specs / Useful Links

• andym's brainstorming
  • https://etherpad.mozilla.org/apps-api
• morgamic's brainstorming
  • Examples and Inspiration
    • http://developer.github.com/v3/
    • https://dev.twitter.com/docs/api
    • https://developers.facebook.com/docs/reference/api/
  • Accessors
    • Search
    • Developer Data (keyed or auth)
  • Mutators
    • Submission
    • Trusted Submission (keyed)

Bugs

Bugs are tracked on AMO's Bugzilla product.

• File a Bug in AMO::API. Might want to prefix bug titles with [Apps] or so.
• Open AMO API bugs