GET /v1/activity
HTTP Verb: GET
Available statuses: 200 OK, 204 No Content, 404 Not Found
Object: Event
Location: n/a
Formats: XML, JSON
Get user activity stream, filtered by date or not.
Params
| Param | Description |
|---|---|
| space_id | Filter events by a space, acceptable value is a space ID. |
| to | Return events before a specified date and time. Valid date format is yyyy-mm-dd hh:mm. |
| from | Return events after a specified date and time. Valid date format is yyyy-mm-dd hh:mm. |
| page | Parameter to specify which page to request, see per_page to determine how many items per page. |
| per_page | Specify the number of activities fetched per one page, default is 50. |
from and to params can be combined in one query to get a time range.
NOTE: Only events from the last 60 days are available.
Examples
Request XML, using cURL utility:
curl -H "Authorization: Bearer _token" https://api.assembla.com/v1/activity.xml
Response
HTTP/1.1 200 OK
Server: nginx/0.8.55
Date: Wed, 22 Aug 2012 13:42:29 GMT
Content-Type: application/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 200
<?xml version="1.0" encoding="UTF-8"?>
<events type="array">
<event>
<object>User</object>
<url>https://www.assembla.com/user/best_profile/bCNpRYfqGr4yCaadbNA33N</url>
<space-id>b89TL8MYWr4id7adbNA33N</space-id>
<date type="datetime">2012-08-22T13:26:59+00:00</date>
<author-id>bgnP_qA1Gr2QjIaaaHk9wZ</author-id>
<operation>invited</operation>
<title>John</title>
</event>
...
</events>
Request JSON, using cURL utility:
curl -i -H "Authorization: Bearer _token" https://api.assembla.com/v1/activity.json
Response
HTTP/1.1 200 OK
Server: nginx/0.8.55
Date: Wed, 22 Aug 2012 13:43:28 GMT
Content-Type: application/json; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 200
[
{
"object":"User",
"url":"https://www.assembla.com/user/best_profile/bCNpRYfqGr4yCaadbNA33N",
"space_id":"b89TL8MYWr4id7adbNA33N",
"date":"2012-08-22T13:26:59+00:00",
"author_id":"bgnP_qA1Gr2QjIaaaHk9wZ",
"operation":"invited",
"title":"John"
},
...
]
JSON is formatted here for readability, in a real response JSON body is inline with no indentation.
Description for each field: Event object fields reference