Issue #3439 new

unauthenticated repo api results lack essential repo data even if the repo is public (BB-3459)

Jakub Zalewski
created an issue

example of fetching data for a public repo

{{{ $ curl --user zalew:password https://api.bitbucket.org/1.0/repositories/zalew/django-inbox/ { "scm": "hg", "has_wiki": true, "last_updated": "2011-09-13 14:24:35", "created_on": "2010-06-25 21:31:58", "owner": "zalew", "logo": null, "email_mailinglist": "", "is_mq": false, "size": 21657, "read_only": false, "fork_of": null, "mq_of": null, "state": "available", "utc_created_on": "2010-06-25 19:31:58+00:00", "website": "", "description": "Messages between Users.", "has_issues": true, "is_fork": false, "slug": "django-inbox", "is_private": false, "name": "django-inbox", "language": "", "utc_last_updated": "2011-09-13 12:24:35+00:00", "email_writers": true, "main_branch": "default", "no_public_forks": false, "resource_uri": "/api/1.0/repositories/zalew/django-inbox" } }}}

{{{ $ curl https://api.bitbucket.org/1.0/repositories/zalew/django-inbox/ { "website": "", "scm": "hg", "name": "django-inbox", "followers_count": 1, "owner": "zalew", "logo": null, "resource_uri": "/api/1.0/repositories/zalew/django-inbox", "slug": "django-inbox", "description": "Messages between Users." } }}}

is there a reason why created, last update, information if it's a fork, etc, are not shown? this data is public anyway.

Comments (9)

  1. Dylan Etkin

    Hi Jakub,

    We have opened an bug for this. I am not sure when we will get to fixing it so for now you should hit the API as an auth'ed user if you can.

    Thanks for reporting,

    Dylan

  2. Log in to comment