For the searching, use querystrings. This is perfectly RESTful:
/cars?color=blue&type=sedan&doors=4
An advantage to regular querystrings is that they are standard and widely understood and that they can be generated from form-get.
More Related Contents:
- What exactly is RESTful programming?
- Best practices for API versioning? [closed]
- If REST applications are supposed to be stateless, how do you manage sessions?
- Free Rest API to retrieve current datetime as string (timezone irrelevant) [closed]
- Design RESTful query API with a long list of query parameters [closed]
- Security of REST authentication schemes
- How to make remote REST call inside Node.js? any CURL?
- How to understand “RESTful API is stateless”?
- Best practice for partial updates in a RESTful service
- API pagination best practices
- How to use cURL to send Cookies?
- Querystring in REST Resource url
- How to construct a REST API that takes an array of id’s for the resources
- Spring @ExceptionHandler does not work with @ResponseBody
- Why the slow WADL uptake? [closed]
- Azure Websites Kudu REST API – Authentication
- How to format Swagger 2.0 text descriptions?
- Update an entire resource collection in a REST way
- What are the best/common RESTful url verbs and actions?
- How should the header X-DocuSign-Authentication be used for REST and SOAP?
- Restful way for deleting a bunch of items
- Swagger documentation with JAX-RS Jersey 2 and Grizzly
- How one could use server side sorting and paging with Azure Mobile Services
- Call a Server-side Method on a Resource in a RESTful Way
- RESTful – What should a DELETE response body contain
- Place API key in Headers or URL
- Curl retry mechanism
- The MAC signature found in the HTTP request ‘…’ is not the same as any computed signature
- Response status code for searches in REST APIs
- Status code when deleting a resource using HTTP DELETE for the second time