Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

53 lines (39 sloc) 1.847 kB

Accesses

Get accesses

  • GET /projects/1/accesses.json will return all the people with access to the project.
  • GET /calendars/1/accesses.json will return all the people with access to the calendar.
[
  {
    "id": 149087659,
    "name": "Jason Fried",
    "email_address": "jason@37signals.com",
    "updated_at": "2012-03-22T16:56:48-05:00",
    "url": "https://basecamp.com/999999999/api/v1/people/149087659-jason-fried.json"
  },
  {
    "id": 1071630348,
    "name": "Jeremy Kemper",
    "email_address": "jeremy@37signals.com",
    "updated_at": "2012-03-22T16:56:48-05:00",
    "url": "https://basecamp.com/999999999/api/v1/people/1071630348-jeremy-kemper.json"
  }
]

Grant access

  • POST /projects/1/accesses.json will grant access to the project for the existing ids of people already on the account or new people via email_addresses. (Same goes for calendars with /calendars/ instead)
{
  "ids": [ 5, 6, 10 ],
  "email_addresses": [ "someone@example.com", "someoneelse@example.com" ]
}

You can get the ids of existing people on the account from the people API.

This will return 204 No Content if the access was granted successfully. If the authenticated user does not have access to this project, 404 Not Found will be returned.

Revoke access

  • DELETE /projects/1/accesses/1.json will revoke the access of the person who's id is mentioned in the URL. (Same goes for calendars with /calendars/ instead)

This will return 204 No Content if the revoke was a success. If the user does not have access to revoke access from the project, 403 Forbidden will be returned. If the authenticated user does not have access to this project, 404 Not Found will be returned.

Jump to Line
Something went wrong with that request. Please try again.