Chapters

28 Chapters | 1:45:06 |

01

The REST API Tutorial

3:07
02

HTTP Basics

2:10
03

REST: Resources and Representations

3:12
04

Transitions and Client State

2:11
05

Project Routing

5:22
06

POST: Creation, Location Header and 201

4:53
07

GET’ing Resources, and Content-Type

4:36
08

Updating the Location Header

1:47
09

GET /programmers: A collection of Programmers

3:32
10

Fixing the Content-Type on POST

2:37
11

Testing your API with PHPUnit

2:34
12

Behat for Testing

4:35
13

Handling Data in Tests

3:57
14

PUT: Editing Resources

4:13
15

Debugging Tests

1:12
16

PUT: Killing Duplicated Code

2:12
17

GET Representation != POST Representation

2:46
18

PUT Versus POST

5:07
19

Deleting Resources

2:29
20

PATCH: The Other Edit

4:53
21

Handling Errors

5:41
22

The application/problem+json Content-Type

4:26
23

Enforcing Consistency with ApiProblem

5:13
24

Error in Invalid JSON

4:28
25

ApiProblemException and Exception Handling

5:38
26

Handling 404 Errors

6:17
27

Exposing more Error Details

4:56
28

What’s Next

1:02

This course is archived!

This tutorial uses a deprecated micro-framework called Silex. The fundamentals of REST are still valid, but the code we use can't be used in a real application.

> APIs > RESTful APIs in the Real World Course 1

Buy Access to Course

19.

Deleting Resources

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

Login or register to check out the script

2 Comments

Sort By

Login or Register to join the conversation

Daan Biesterbos 8 years ago

Hi there :-)

Usually when I get a DELETE request on a resource that does not exist (or a record that was soft deleted) I return a 404. You did not do this here. What is your opinion on handling that situation?

|

MolloKhan SFCASTS Daan Biesterbos 8 years ago edited

Hey Daan Biesterbos

I think it depends on the App and it's security, some guys would preffer to return the same response whether or not the resource was actually deleted, and some others may preffer to inform the client that the resource was not found.
If the answer to this question "Does a client needs to know when a resource is not found?" is yes, then yes, return a 404. If not, I would hide that information from the client and return a 204.

Cheers!

1 |

This tutorial uses a deprecated micro-framework called Silex. The fundamentals of REST are still valid, but the code we use can't be used in a real application.

Silex

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "silex/silex": "~1.0", // v1.3.2
        "symfony/twig-bridge": "~2.1", // v2.7.3
        "symfony/security": "~2.4", // v2.7.3
        "doctrine/dbal": "^2.5.4", // v2.5.4
        "monolog/monolog": "~1.7.0", // 1.7.0
        "symfony/validator": "~2.4", // v2.7.3
        "symfony/expression-language": "~2.4" // v2.7.3
    },
    "require-dev": {
        "behat/mink": "~1.5", // v1.5.0
        "behat/mink-goutte-driver": "~1.0.9", // v1.0.9
        "behat/mink-selenium2-driver": "~1.1.1", // v1.1.1
        "behat/behat": "~2.5", // v2.5.5
        "behat/mink-extension": "~1.2.0", // v1.2.0
        "phpunit/phpunit": "~5.7.0", // 5.7.27
        "guzzle/guzzle": "~3.7" // v3.9.3
    }
}

Previous Chapter

Next Chapter