Creating REST Web Services: 9. Conclusion (2015)

Creating REST Web Services: 1. An Overview of REST and RPC (2015)

Creating REST Web Services: 2. Defining the Web Service (2015)

Creating REST Web Services: 3. Authorization and CORS (2015)

Creating REST Web Services: 4. First an RPC Web Service (2015)

Creating REST Web Services: 5. Defining the REST API (2015)

Creating REST Web Services: 6. Supporting HTTP POST (2015)

Creating REST Web Services: 7. Supporting HTTP PUT (2015)

Creating REST Web Services: 8. Supporting HTTP DELETE (2015)

Article by aaronkoning · Oct 08, 2015 at 07:14 PM · edited · Nov 16, 2018 at 05:12 PM

Article created with FME Server 2015.0

This article has been depreciated, for current information on working with FME and REST, see the FME Server REST API Training course.

You did it! You used FME Server to create a REST Web Service and API for managing parks data. Where do you go from here? Here are two ideas:

You might try to add another capability to the REST service on your own. For example, the ability to provide a single park based on name or you could switch the data format from JSON to XML.
The workspace is not setup to deal with errors such as trying to add the same park twice. So you could handle this case and provide feedback to the user as a JSON message.

Let us know where you go from here and how we can help:

web rest http

Add comment

10 |4000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 4.0 MB each and 4.0 MB total.