This documentation helps you implement the RESTful Wisembly API. This API uses a JSON format for output and is capable of handling CORS (Cross-Origin Resource Sharing) requests. The API is stateless – all requests are validated against an API token. The API token must be obtained manually from the authentication API.
Creating a session token
GET calls could be done without session token. But for every other calls (POST, PUT, PATCH) you'll need to be authentified. To generate a token, you'll need an app_id and app_secret to generate a hash allowing you to forge tokens. You could obtain these by sending an email to us explaining briefly what you want to do. We'll make sure to help you build great things on us!
Once you have these, to create an anonymous token you'll have to POST the authentication API with this data:
{"app_id":"your app_id", "hash":"generated hash"}
Where the generated hash is sha1($app_id.$app_secret);
Once you have these, to create a logged in user token you'll have to POST the authentication API with this data:
{"app_id":"your app_id", "hash":"generated hash", "email":"user email", "secret":"user password"}
Where the generated hash is sha1($email.$app_id.$app_secret);
All urls must be relative to the domain name
(http://api.wisembly.dev/app_dev.php/{this part}). Other urls will not
be recognized and will return a 400 instead.
So in the payload, as long as there is one request and at a most a
predefined number of requests (20 at the time of writing this
documentation), it will always return a 200, even if one or more
sub-request fails (they will have their proper status code).
When sending a body in a POST / PUT request, it must be encoded as a
string, and the appropriate header must be sent on that particular
request (see example above).
For the above payload, here is the expected response :
As you can see, the response has the body already encoded (so you will
need to decode it), like in a request where it has to be encoded
when sending a body.
This feature is closely following the batch api requests by facebook :
https://developers.facebook.com/docs/graph-api/making-multiple-requests
@ApiDoc(section="event",
resource=true,
description="Accept invitation",
output="Wisembly\ApiBundle\Response\ApiResponse",
statusCodes={200="Returned when everything went fine",
404="Returned on event not found",
401="Returned when not enough rights on the event"})
@ApiDoc(section="event",
resource=true,
description="Decline an invitation",
output="Wisembly\ApiBundle\Response\ApiResponse",
statusCodes={200="Returned when everything went fine",
404="Returned on event not found",
401="Returned when not enough rights on the event"})
Edit user's informations.
To edit the user's password, you must passed the new password in the parameter password and the current user's password in the parameter current_password.
Edit user's informations.
To edit the user's password, you must passed the new password in the parameter password and the current user's password in the parameter current_password.
Edit user's informations.
To edit the user's password, you must passed the new password in the parameter password and the current user's password in the parameter current_password.
Edit user's informations.
To edit the user's password, you must passed the new password in the parameter password and the current user's password in the parameter current_password.