Skip to content

Commit 4dd30b5

Browse files
committed
Zapier changes
1 parent 700c67f commit 4dd30b5

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

pages/versioning/versioning.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,19 @@
1-
## Zapier is currently not functional with Version 2 of the Roles API. We are working on a fix for this and will update this page when it is resolved.
1+
## Zapier is now functional with Version 2 of the Roles API. To use them both together you will need to use the TutorCruncher (3.0.0) in zapier
2+
3+
### Zapier changes
4+
Mostly things should be just about the same, some IDs may look different inside Zapier but the data should be the same.
5+
This should appear as IDs being required to Update a user and the User layer in requests and responses being removed.
6+
7+
For moving from V1 to V2 of API, the best practice is to follow the following steps.
8+
9+
1. Clone an existing zap
10+
2. Update to use the TutorCruncher(3.0.0) app
11+
3. Switch API key to a Demo branch API key for testing
12+
4. Check the create and update zaps are correct, check for data where it can no longer be retrieved from previous zaps
13+
5. Test each step of the zap to ensure it is working correctly with the demo branch before moving back to live
14+
15+
16+
### Version 2 API changes
217

318
Version 2 of the Roles API is on its way. The changes are mostly in the backend and to improve speed and set us up for better developments going forward.
419
We will be removing Version 1 of the Roles API on the 3rd July 2025 so please update your API integrations as needed before then.

0 commit comments

Comments
 (0)