Wabode
Base URI
not needed for /auth actions, must start with "Bearer " followed by the token
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
X-XSRF-TOKEN
Body
These credentials do not match our records.
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
{id}
{id}
{id}
{id}
{id}
{id}
/ratings{id}
/ratingRequest headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
an actual file, not a string. can be one of .jpg,.jpeg,.png
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
Path variables
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
number
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
Path variables
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
{id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request parameters
stripe token of a card, acquired through stripe.js
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
{id}
Path variables
payment_method.id
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request parameters
payment_method.id
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
{id}
/ratingsPath variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/ratingPath variables
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
{id}
{id}
/item{id}
/item/{item_id}
{id}
/item/{item_id}
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
Path variables
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/itemPath variables
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/item/{item_id}
Path variables
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/item/{item_id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
- Can only pay a single order, either partially or entirely
- Cannot overpay
Request parameters
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
a buyers request for a property
{id}
{id}
{id}
/feature/{feature_id}
{id}
/feature/{feature_id}
{lead_id}
/score/{property_id}
{lead_id}
/offer/{property_id}
{id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Create a lead if you dont already have an open one and you are a buyer
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Request body
must be one of (‘buy’, ‘rent’, ‘lease’, ‘short term’)
Responses
Body
{id}
Create a lead if you dont already have an open one and you are a buyer
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Request body
Responses
Body
buyer api call to get all leads they have created (should only be 1 open lead)
Notes
speca wont save the sample output, sample output as defined below: { “sucess”: true, “code”: 200, “data”: [ { “id”: 4, “property_type”: “residential”, “purchase_type”: “rent”, “min_price”: 500, “max_price”: 1450, “building_type”: “any”, “min_square_feet”: 400, “max_square_feet”: 900, “bedrooms”: 2, “comments”: “my comment”, “km_radius_to_seach”: 5, “lat”: “43.798545”, “lng”: “-79.448767”, “status”: “open”, “features”: [ { “id”: 5, “feature”: { “name”: “Swimming Pool”, “isResidential”: “Yes”, “isCommercial”: “No” } } ], “properties”: [ { “id”: 1, “score”: 65, “created_at”: “2015-06-29 21:14:58”, “updated_at”: “2015-06-29 21:14:58”, “deleted_at”: null, “accepted_at”: null, “property”: { “building_type”: “House”, “square_feet”: 2200, “bathrooms”: 3, “bedrooms”: 4, “price”: “835000.00”, “sold_on”: null, “purchase_type”: “buy”, “isFinished”: 0, “comments”: “great house in a great area”, “address”: { “id”: 3, “nickname”: “”, “address”: “22 troyer court”, “address_line_2”: “”, “city”: “thornhill”, “state”: “on”, “zip”: “l4jsm7”, “country”: “Canada”, “lat”: “43.798545”, “lng”: “-79.448767” }, “features”: [ { “id”: 1, “feature”: { “name”: “Fireplace”, “isResidential”: “Yes”, “isCommercial”: “No” } }, { “id”: 2, “feature”: { “name”: “Air Conditioning”, “isResidential”: “Yes”, “isCommercial”: “Yes” } } ] } } ] } ] }
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/feature/{feature_id}
add a feature to your lead, use the get featues call to find all features and then use this call to add it by id, if you add it twice nothing will happen. an error is thrown if you add a residential only feature to a commercial lead and vice versa
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
{id}
/feature/{feature_id}
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
returns paginated list of leads that are still open and within your (the brokers) requested area
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
{lead_id}
/score/{property_id}
get the score with its breakdown for a given property. You must own the property and the lead must be open. this call can be made regardless of an offer existing for this proerty on this lead
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{lead_id}
/offer/{property_id}
get the score with its breakdown for a given property. You must own the property and the lead must be open. this call can be made regardless of an offer existing for this property on this lead
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
A property is only visible to the broker who created it and to a buyer once its been suggested for their lead
{id}
{id}
/feature/{feature_id}
{id}
/feature/{feature_id}
{id}
/photo{id}
/photo/{photo_id}
Request parameters
1 for yes, 0 for no
0 or 1
details about the property
latitude
longitude
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
you must repost all fields even if just changing 1
Path variables
Request parameters
1 for yes, 0 for no
0 for no (broker), 1 for yes
details about the property
latitude
longitude
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/feature/{feature_id}
Path variables
property id
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/feature/{feature_id}
Path variables
property id
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/photoPath variables
property id
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
{id}
/photo/{photo_id}
Path variables
property id
must belong to the property
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
photo deleted message
a property being offered for a lead, this is the entity that holds the score and status
{id}
{id}
{id}
{id}
Decline an offer presented to your lead from a broker. this can be done right away or after some conversation with the broker
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
{id}
intent to buy the property
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
{id}
intent to buy the property
Path variables
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
conversation between a broker and a buyer when a lead is connected to a property
{id}
{id}
{id}
id is the leadProperty id, it can be found in the properties array for a lead (for buyers) or the leads array for a property (for brokers)
this call can also be used for polling, just set page_size to 1
Path variables
Request parameters
remember its in descending order
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
paginated response in descending order with a default of 50 messages per page
Body
{id}
Path variables
the lead property id (id from leads in get properties or property in get leads)
Request parameters
the message you wish to send
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
update (or create) a broker profile
Request parameters
id of brokerage company, if left out will be set to NULL. there is an api call to get all available options
0 for no, 1 for yes
0 for no, 1 for yes
0 for no, 1 for yes
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
get your own broker profile
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
Request headers
not needed for /auth actions, must start with "Bearer " followed by the token
Responses
Body
must be one of (‘buy’, ‘rent’, ‘lease’, ‘short term’)
123