laravel4cookbook

API 133
1 curl -X POST -d "name=foo&description=a+day+of+foo&started_at=2013-10-03+09:00&en\
2 ded_at=2013-10-03+12:00" http://dev.tutorial-laravel-4-api:2080/event
..now, when we request the index() action, we should see the new event has been added. We can
retrieve this event individually with a request similar to this:
1 curl http://dev.tutorial-laravel-4-api:2080/event/1
There’s a lot going on here. Remember how we bound the model to a specific parameter name (in
app/routes.php)? Well Laravel 4 sees that ID value, matches it to the bound model parameter and
fetches the record from the database. If the ID does not match any of the records in the database;
Laravel will respond with a 404 error message.
If the record is found; Laravel returns the model representation to the action we specified, and we
get a model to work with.
Let’s update this event:
1 curl -X PUT -d "name=best+foo&description=a+day+of+the+best+foo&started_at=2013-1\
2 0-03+10:00&ended_at=2013-10-03+13:00" http://dev.tutorial-laravel-4-api:2080/even\
3 t/1
Notice how all that’s changed is the data and the request type — even though we’re doing something
completely different behind the scenes.
Lastly, let’s delete the event:
1 curl -X DELETE http://dev.tutorial-laravel-4-api:2080/event/1
.
Feel free to set the same routes and actions up for categories and sponsors. I’ve not covered them
here, for the sake of time, but they only differ in terms of the fields.
Authenticating Requests
So far we’ve left the API endpoints unauthenticated. That’s ok for internal use but it would be far
more secure if we were to add an authentication layer.
We do this by securing the routes in filtered groups, and checking for valid credentials within the
filter: