GolfNow API 2.1 was designed to be more organized, faster and easier to use than ever before. To Accomplish this, we have implemented the following improvements
Utilize Industry Terminology – We removed a lot of the GolfNow specific terminology (owners, courses vs facilities, etc) throughout the application and replaced them with terminology used by the golf industry to help reduce the amount of domain knowledge our developers need to acquire.
Publish Improved Documentation – Documentation of the API has been updated and revised to give more detailed descriptions of resources and parameters. API documentation has been made interactive so you can now look at all the code samples and schemas in one easy to use page.
Maximize Performance – The performance of each method was reviewed and fixed with a target completion time of under 500ms.
Incorporate Expanded Properties – Also new in API 2.1, expanded properties allows you to configure what data gets returned to you for supported resource methods. For example, if you are getting a list of facilities, you can request that 5 tee times are returned for each facility.
Sorting and Paging – Sorting and paging are being implemented throughout the API in order to provide faster timing on connection limited devices.
Reorganize REST Structure – The rest structure has been organized into four segments: Customers, Inventory Channel, System and Lookups.
Revamp Client Authentication - Client authentication scheme has been revisited in API 2.1. The concept of an ownerToken has been completely removed and as a result, you now have one less call to make.
Provide Better Errors – The input validation engine and error handling has been completely revamped to use http status codes and provide more specific information about issues with requests.
Stateless Design – All concepts of session state were removed from the API in order to provide a more consistent experience and improve scalability.
Implement API Versioning – We now support API versioning in order to ease the transition between each minor version and reduce the issues caused by contract changes. Each version will have a url-based endpoint that will be deprecated after all the clients have been upgraded. In addition, each version will be supported until its deprecation date.