Official comment
Hello Antonio,
1. Generally API V2 is NOT fully backward compatible to API V1. There were some breaking changes. You can see here: https://success.clarizen.com/hc/en-us/articles/205711828-REST-API-Guide-Version-2#moving. Here is the quote from there:
Moving from v1.0 to V2.0
We maintain backward compatibility whenever possible between API versions. The following breaking changes have been applied in API v2:
- Authorization info should not be sent via cookies. Instead the Session ID must be sent in the standard Authorization header (See here for more information)
- The API for uploading and downloading files has been changed. See the reference guide for more details
- When creating a Milestone object, you must pass an existing parent (Previously it was possible to create a milestone and only later attach it to a parent)
- The Metadata API returns more detailed information about the different field types. Two new field types have been added: Multi-Pick list and Binary
- Paging was changed. Instead of transferring PageNumber and PageSize parameters, you now need to send the From and Limit parameters which allows more flexibility. If you followed the API best practices of taking the Paging object from a query result and pass it “as-is” to the next request, then no changes are required
2. As Roland already answered, there is no change in login/logout functionality. You can continue to use the same steps.
Regards.
Comment actions
