As announced previously we have completely overhauled our Public API (V1) to now run locally from each site (V2).

There are some huge benefits to this including performance/reliability but also it now means you will be able to expand the API and build your own endpoints for each site. This is a big step forwards and we have exciting plans for API V2. There are some new endpoints we’ve been wanting to release for a while including a Pages endpoint which opens up lots of possibilities for connecting with 3rd party tools, automating workflows and integrating AI.

We have also updated our Zapier integration to use the new Site API which is firstly aimed to overcome any previous reconnection issues but also leverages the Instant Zaps feature (no more waiting 5-15 minutes with the ‘polling’ method).

The new Site API docs are available here:
https://docs.siteglide.com/en/developer-tools/site-api

We do still have the Portal API endpoints here:
https://api.siteglide.co.uk/docs/

The old (V1) API docs are still available here:
https://api.siteglide.co.uk/v1/docs/

What happens to my existing integrations?

They will continue to work as normal, nothing has changed, the new API is completely separate.

We will be encouraging customers to migrate across to the new API and at some point the old API will be deprecated. We will give significant warning and most importantly be working with you to migrate. This applies to Zapier in exactly the same way.

Zapier V2

The new V2 API version is available right now in Zapier. We recommend migrating to V2 asap as it helps overcome any potential reconnection issues.

When you select Siteglide as a trigger or action it will default to V2 (it will simply show as Siteglide) and if you click the dropdown you will see 1.1.3 (the previous version) is available but we advise against using this as it will be deprecated down the line (there is no reason to use 1.1.3).

Note. As we release updates to V2 you’ll see previous 2.x.x versions appear in the list, we recommend always using the latest version which will show as default without a version number.

Here is a video showing how to migrate Zaps easily to V2, you simply update the Auth (App Connection) and it can update all Zaps that run from the one App Connection (per site):

Youtube link: https://youtu.be/KdLZ-KeB6KA

Instant Zaps Demo

https://youtu.be/WKliXkf5xfk?feature=shared

Feedback/Questions?

As always reach out via Discord or Live Chat if you have any questions or issues. Please feel free to submit feedback requests to the Roadmap so that we can keep improving the product.