Firefox Add Ons
Use Firefox Add-ons data APIs through OpenAny to retrieve extension metadata and published compatibility or distribution details. For addon, provide source record ID (id); refine the result with language code (lang). Other available operations include collection, versions. The resource profile places release and distribution information beside the description and compatibility data published for that extension, helping distinguish a usable catalogue record from the extension's executable installation package. Inspect extension features and compatibility metadata, compare release information and assess the published requirements before installation. Each API page provides supported parameters, request and response examples, and usage pricing.
- Endpoints
- 3In this collection
- Providers
- 1Unique providers
- Requests
- —Loading...
- Success rate
- —Loading...
- Response P50
- —Loading...
Available APIs
Firefox Add-ons collection API
Use the Firefox Add-ons collection API to retrieve a curated collection's metadata and its public extension entries. Provide source user (user), source-page slug (slug); refine the result with result sort mode (sort), language code (lang). Collection entries retain the curator's public notes alongside the referenced add-ons, so the reason for grouping extensions can be inspected separately from each add-on's own compatibility or release details. Review a curated add-on collection, inspect the curator's notes and identify extensions worth comparing individually. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
Firefox Add-ons versions API
Use the Firefox Add-ons versions API to retrieve published package or extension versions and release metadata. Provide source record ID (id); refine the result with language code (lang). Version entries retain the release number and any date, platform or prerelease details supplied by that ecosystem, so a historical release can be selected before its own package metadata is retrieved. Compare published release numbers and dates, identify prereleases where provided and choose a version for a compatibility review. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
Firefox Add-ons addon API
Use the Firefox Add-ons addon API to retrieve extension metadata and published compatibility or distribution details. Provide source record ID (id); refine the result with language code (lang). The resource profile places release and distribution information beside the description and compatibility data published for that extension, helping distinguish a usable catalogue record from the extension's executable installation package. Inspect extension features and compatibility metadata, compare release information and assess the published requirements before installation. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
Common questions
How are Firefox Add Ons APIs priced?
Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.
How do I authenticate Firefox Add Ons requests?
Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.
Are all implementations interchangeable?
No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.
Use Firefox Add Ons with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.