<p>Turns out there was a bug with package names that contained <code>-</code>s. Just fixed that, so <code>/v1/package/craftcms/contact-form</code> works now.</p>

CC BY-SA 4.0
2020-07-10T09:10:32.907Z
Great, thanks Brandon!
Cole Henley
CC BY-SA 4.0
2020-07-09T23:16:43.083Z
2020-07-09T23:16:43.083Z
Brandon Kelly
<p>Does querying composer packages via the Craftnet API need authentication?
Ref <a href="https://docs.api.craftcms.com/packages.html" rel="nofollow noreferrer">https://docs.api.craftcms.com/packages.html</a></p>
<p>Querying the Craft CMS package itself is fine, eg <a href="https://api.craftcms.com/v1/package/craftcms/cms" rel="nofollow noreferrer">https://api.craftcms.com/v1/package/craftcms/cms</a>. However trying to query any plugins is throwing a 404, eg <a href="https://api.craftcms.com/v1/package/craftcms/contact-form" rel="nofollow noreferrer">https://api.craftcms.com/v1/package/craftcms/contact-form</a></p>

<plugin-development><composer><api>
Craftnet API package query
# Craftnet API package query

(Asked by: username_0 on 2020-07-09)

Does querying composer packages via the Craftnet API need authentication?
Ref <https://docs.api.craftcms.com/packages.html>

Querying the Craft CMS package itself is fine, eg <https://api.craftcms.com/v1/package/craftcms/cms>. However trying to query any plugins is throwing a 404, eg <https://api.craftcms.com/v1/package/craftcms/contact-form>

**Tags:** plugin-development, composer, api


---

## 1 answers

### Answer by username_1 on 2020-07-09. Score: 1 | Accepted answer

Turns out there was a bug with package names that contained `-`s. Just fixed that, so `/v1/package/craftcms/contact-form` works now.

> **Comments:**
> **username_0**: Great, thanks Brandon!  

---

