Legacy API retirement: migrate before 1 May 2027

We are retiring our legacy API services on 1 May 2027. If your organisation uses a custom integration connected to the old Fixi or Gamz API endpoints, please arrange its migration to the new REST API before that date.

This notice is for customers, developers and integration providers who connect their own websites, scoreboards, reporting tools or other systems to Gamz.

Which endpoints are being retired?

The retirement covers the legacy API endpoints hosted at:

• api.fixionline.com.

• The legacy services on api.gamzapp.com outside the new /rest/ application.

This includes the old SOAP services and legacy HTTP endpoints such as those under MobService.svc. Existing connections using these services need to move to the new REST routes.

The new REST API at https://api.gamzapp.com/rest/ is not being retired. The address https://api.gamzapp.com/ remains the home of the current developer documentation.

What replaces the legacy services?

The new Gamz REST API provides the same core integration capabilities through standard HTTPS requests and JSON responses, including calendar matches, bookings, competition fixtures and ladders, and team payment recording. It also provides documented public reads and private operational endpoints.

Private requests use bearer-token authentication. Your integration signs in with an eligible API user account and the venue’s ApplicationId, then uses the returned token for subsequent private calls. Public read endpoints are identified separately in the guide.

What you need to do

1. Identify your existing connections. Ask your developer or provider to check for calls to api.fixionline.com and legacy services on api.gamzapp.com, including .svc addresses.

2. Review the new REST API documentation. Match each operation your integration uses to its REST equivalent and check the required parameters and response format.

3. Update the integration. Replace the legacy requests with the documented REST routes and JSON payloads, and add bearer-token sign-in where required. Changing the base URL alone is not enough.

4. Test and switch over before 1 May 2027. Verify the reads and writes your integration depends on, token expiry and error handling, then update your production configuration.

The new API works with your existing Gamz data. The migration is about updating the connection your software uses to access it.

Please allow time for testing

Start planning now, particularly if a third-party supplier maintains your integration. Completing the change early gives your team time to check the new requests and resolve any issues before the legacy services are removed.

From 1 May 2027, integrations still relying on the retired endpoints will no longer be able to use those services. The new /rest/ endpoints will remain available.

Need a hand?

Please share this notice and the Gamz API documentation with whoever manages your integration. If you are unsure whether your connection is affected or need help finding the right REST endpoints, contact the Gamz team.