Send us an e-mail to api@irlconnect.com with the following information:
We will respond to your request within 48 hours on workdays.
Creates a new IRL user. A confirmation e-mail will be send to the provided e-mail address. Also a user API key will be created and returned, to be used for authentication of future API calls.
type=GET, or POST both OK
(Note: KEY should be block letter)
The format of location is "Amsterdam, Netherlands"(location name) or "9.86784 23.45663"(lat, lng) or "610000"(zip code).
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
201 |
Invalid_username |
invalid username |
202 |
Invalid_password |
invalid password |
203 |
Invalid_email |
invalid email |
204 |
Email_taken |
email have been taken, please change to another emaill address. |
Format:
{success: {message: "User added successfully.", username: "username", userapikey: "userapikey", email :"email ", nickname: "nickname"}}
Need to remember userapikey for later API call.
A user API key will be created and returned, to be used for authentication of future API calls.
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
101 |
bad_request |
The request is invalid, e.g., missing some required fields. |
102 |
internal_error |
Internal Error |
103 |
credentials_not_found |
the username is not known |
104 |
bad_credentials |
the password doesn't match |
Format:
{success: {message: "User's ApiKey found.", username: "username", userapikey: "userapikey"}}
Need to remember userapikey for later API call.
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
101 |
bad_request |
The request is invalid, e.g., missing some required fields. |
102 |
internal_error |
Internal Error |
103 |
credentials_not_found |
the username is not known |
Format:
[{"status": "great location for dinner blab la bla", "name": "user name", "avatar": "url", "location":{"lat":"42.34343","lon":"2.4545"}}]
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
101 |
bad_request |
The request is invalid, e.g., missing some required fields. |
102 |
internal_error |
Internal Error |
103 |
credentials_not_found |
the username is not known |
Format:
{"status": "user status", "avatar": "url", "name": "user name", "location":{"lat":"43.5454","lon":"2.3434"}}
Updates the status message for a specific user.
type=GET, or POST both OK
(Note: KEY should be block letter)
The format of location is "Amsterdam, Netherlands"(location name) or "9.86784 23.45663"(lat, lng) or "610000"(zip code)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
101 |
bad_request |
The request is invalid, e.g., missing some required fields. |
102 |
internal_error |
Internal Error |
403 |
credentials_not_found |
The User API key is not valid. |
404 |
bad_credentials |
API for this user was disallowed. |
Format:
{success: {message: "Status updated successfully"}}
Or
{success: {message: "Status updated successfully, Location updated successfully"}} If the location is found and the location is 2km> from old location.
Creates a media item in the talk stream. This item is clickable and the content will be shown on the map.
type=GET, or POST both OK
<object id="bplayer" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="320" height="276"><embed name="bplayer" src="http://bambuser.com/r/player.swf" type="application/x-shockwave-flash" flashvars="[---FLASHVARS---]" width="320" height="276" allowfullscreen="true"></embed><param name="movie" value="http://bambuser.com/r/player.swf"></param><param name="flashvars" value="[--- FLASHVARS---]"></param><param name="allowfullscreen" value="true"></param></object>
(Note: KEY should be block letter)
One of the two parameters, "url" or "html", should be provided.
The format of location was "Amsterdam, Netherlands"(location name) or "9.86784 23.45663"(lat, lng) or "610000"(zip code)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
101 |
bad_request |
The request is invalid, e.g., missing some required fields. |
102 |
internal_error |
Internal Error |
403 |
credentials_not_found |
The User API key is not valid. |
404 |
bad_credentials |
API for this user was disallowed. |
301 |
url or html required |
url or html required |
302 |
invalid url |
invalid url |
303 |
title required |
title required |
304 |
invalid html |
invalid html |
Format:
{success: {message: "Media updated successfully"}}
Or, if a location was provided and the distance between the old and new location is more then 2 km.:
{success: {message: "Media updated successfully, Location updated successfully"}}
Moves a user to a new location.
type=GET, or POST both OK
(Note: KEY should be block letter)
The format of location is "Amsterdam, Netherlands"(location name) or "9.86784 23.45663"(lat, lng) or "610000"(zip code)
At least one of the two parameters ("lat lng" and "location") should be provided, else throw a 106 error.
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
100 |
key_not_valid |
The API key is not valid |
101 |
bad_request |
The request is invalid, e.g., missing some required fields. |
102 |
internal_error |
Internal Error |
403 |
credentials_not_found |
The User API key is not valid. |
404 |
bad_credentials |
API for this user was disallowed. |
106 |
location required |
location required |
107 |
lat and lng required |
lat and lng required |
Format:
{success: {message: "Location updated successfully."}}
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
| 100 | key_not_valid | The API key is not valid |
| 101 | bad_request | The request is invalid, e.g., missing some required fields. |
| 102 | internal_error | Internal Error |
| 403 | credentials_not_found | The User API key is not valid. |
Format:
{"status": "ok", "count": "count of events", "events": [{"originator": "originator ", "type": "EventType", "timestamp": {"ctime": "Fri May 8 09:41:51 2009", "isoformat": "2009-05-08T09:41:51.906000"}, "appversion": "0.9.0.270", "location": {"lat": 60.222831, "lon": 21.372218}, "appid": 1, "message": {"default": "Default message", "key": "irlconnect.event.login"}, "data": {"IrlUser": {"guid": "guid", "name": "nickname"}}}], "timestamp": "2009-05-08T09:41:56.187000", "size": "1"}
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages:
| ID | String | Description |
|---|---|---|
| 100 | key_not_valid | The API key is not valid |
| 101 | bad_request | The request is invalid, e.g., missing some required fields. |
| 102 | internal_error | Internal Error |
| 403 | credentials_not_found | The User API key is not valid. |
Format:
{"status": "ok", "count": "count of events", "events": [{"originator": "originator ", "type": "EventType", "timestamp": {"ctime": "Fri May 8 09:41:51 2009", "isoformat": "2009-05-08T09:41:51.906000"}, "appversion": "0.9.0.270", "location": {"lat": 60.222831, "lon": 21.372218}, "appid": 1, "message": {"default": "Default message", "key": "irlconnect.event.login"}, "data": {"IrlUser": {"guid": "guid", "name": "nickname"}}}], "timestamp": "2009-05-08T09:41:56.187000", "size": "1"}
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
| 100 | key_not_valid | The API key is not valid |
| 101 | bad_request | The request is invalid, e.g., missing some required fields. |
| 102 | internal_error | Internal Error |
| 403 | credentials_not_found | The User API key is not valid. |
Format:
{"status": "ok", "count": "count of events", "events": [{"originator": "originator ", "type": "EventType", "timestamp": {"ctime": "Fri May 8 09:41:51 2009", "isoformat": "2009-05-08T09:41:51.906000"}, "appversion": "0.9.0.270", "location": {"lat": 60.222831, "lon": 21.372218}, "appid": 1, "message": {"default": "Default message", "key": "irlconnect.event.login"}, "data": {"IrlUser": {"guid": "guid", "name": "nickname"}}}], "timestamp": "2009-05-08T09:41:56.187000", "size": "1"}
type=GET, or POST both OK
(Note: KEY should be block letter)
Format:
{error: {id: int, msg: "string"}}
We support the following error messages
| ID | String | Description |
|---|---|---|
| 100 | key_not_valid | The API key is not valid |
| 101 | bad_request | The request is invalid, e.g., missing some required fields. |
| 102 | internal_error | Internal Error |
| 403 | credentials_not_found | The User API key is not valid. |
Format:
{"status": "ok", "count": "count of events", "events": [{"originator": "originator ", "type": "EventType", "timestamp": {"ctime": "Fri May 8 09:41:51 2009", "isoformat": "2009-05-08T09:41:51.906000"}, "appversion": "0.9.0.270", "location": {"lat": 60.222831, "lon": 21.372218}, "appid": 1, "message": {"default": "Default message", "key": "irlconnect.event.login"}, "data": {"IrlUser": {"guid": "guid", "name": "nickname"}}}], "timestamp": "2009-05-08T09:41:56.187000", "size": "1"}