See hexpm/hex_core#45.

The readme says, "To host a repository only the CDN endpoint has to be implemented." I don't see anything called the CDN endpoint in the documentation.

This would be an optional endpoint that a repository might implement. It would be used by e.g. mix hex.docs fetch foo 1.0.0 --repo acme to download the docs tarball. (Note, we don't yet have --repo on mix hex.docs.)

Another option would be for mix hex.docs fetch --repo to instead use the HTTP API /packages/:name/releases/:version/docs endpoint for custom repos but that doesn't seem ideal either.

For example what is needed for mix deps.get or what is needed for mix hex.publish.

Ref: hexpm/hexpm#454 (comment)

Currently it looks like List all Packages and Fetch a Package endpoints have the same shape, however for the search we want to return less data for releases (just version and url) keys.

(Edit: I've updated issue description to point to the exact endpoints)

https://gist.github.com/ericmj/36bf9e64c0566dfad277

The new registry format file size is 33% of the ets file and 60% of the size when gzipped (with a registry built from hex.pm on 2016-03-12).

/cc @hexpm/contributors @hexpm/rebar3

Hello! I've been using the remove key endpoint and it seems to return 200, while the documentation says it should be 204. Are the docs out of date?

Currently HEX API requires authorization: <token> as api header, it should support normal Bearer token as other API's will do.

eg

curl --include \
     --header "Accept: application/json" \
     --header "Authorization: Bearer <token>" \
  'https://private-anon-d3fb121a9d-hexpm.apiary-mock.com/packages?sort=&search='

• renovatebot/renovate#11028
• renovatebot/renovate#11168
• https://datatracker.ietf.org/doc/html/rfc7235#appendix-C

no longer needs authentication

There appears to be another special key '$$installs2$$' which probably needs documentation as it's unclear how to interpret it.

Hi. I spotted that there are some properties in the Hex API responses that aren't in the documentation:

• latest_stable_version (string)
• latest_version (string)
• configs (object)
• retirements (object)

appear in the API responses but not in the corresponding docs

The JSON data (application/vnd.hex+json) delivered by

• https://hex.pm/api/packages/NAME
• https://hex.pm/api/packages/NAME/releases/VERSION

is not documented.

While most of the fields delivered can be guessed, some are not obvious. Some examples:

• (package url vs. html_url vs doc_html_url
• (package) meta -> elixir
• (release) meta -> app
• (release) meta -> elixir (also: what does null mean here)
• (release) inserted_at vs.updated_at
• (release) url vs. html_url (seems to be the same in many cases)

Beside a description of the fields, it would be nice to have a specification one can rely on.

(FYI: I'm building a importer from hex.pm packages into guix, for which I need to query this data.)