Adds three new endpoints to the API; create, update, and delete Savings Events.

Added

Savings Events

Create a Savings Event

• Savings Events can now be created. These will always show as custom in the application.

Update a Savings Event

• Savings Events metadata can now be updated.

Delete a Savings Event

• Savings Events can now be deleted. Non-custom Savings Events will not be able to be deleted.

Various improvements and fixes for Contracts resource.

Added

Contracts

• Added better documentation around billing_frequency to the Contracts resource to indicate what values are valid.

Fixed

Contract Line Items

• Moving forward application_id is no longer able to be set to null.

Removed

Contracts

• The external_source_link is no longer able to be modified.

This update includes new operations to the "Application Budgets" resource.

Added

Application Budgets

Get Application Budgets

• Retrieve a list of all application budgets.

Get Application Budget Stats

• Retrieve aggregates stats for the budgets related to each application.

Create an Application Budget

• Create an application budget by year.

Update an Application Budget

• Update an application budget by year.

Delete an Application Budget

• Delete an application budget by year.

Adds two new endpoints to the API; get a list of Savings Events and get a Savings Event by Id.

Added

Savings Events

Get list of Savings Events

• An endpoint to get a list of Savings Events from your Zylo instance. This includes the metadata for the Savings Events.

Get A Savings Event by Id

• An endpoint to get a single Savings Event from your Zylo instance by its id. This includes the metadata for the Savings Events.

Various improvements and fixes for Contracts resource.

Added

Contracts

• Added can_have_contract_lines to the Contracts resource to indicate if the contract can have contract line items added.
• Contracts that have can_have_contract_lines as false will have an application_id associated to it on the Contract resource.
• Contracts that have can_have_contract_lines as true will not have an application_id associated to it on the Contract resource, but will have Contract Line Items attached.

Fixed

Contracts

• An end_date is now required when month_to_month is false.
• The field native_currency is now required.

There have been several endpoints added to the Views resource that allow for more flexibilty in managing the View.

Added

Views

Create a View

• Views can now be created. Dynamic Views cannot be created at this time.

Update a View

• View metadata, such as name, can now be updated. There are specific endpoints available to add/delete Zylo Users and Applications from the View.

Add Zylo User to a View

• Zylo Users can now be added to Views. To get the ID for a Zylo User, check out the "Zylo Users" resource.

Delete Zylo User from a View

• Zylo Users can now be deleted from a View. To get the ID for a Zylo User, check out the "Zylo Users" resource.

Add Application to a View

• Applications can now be added to Views. To get the ID for an Application, check out the "Applications" resource.

Delete Application from a View

• Applications can now be deleted from a View. To get the ID for an Application, check out the "Applications" resource.

There is now an option to create Usage Connect integrations programmatically. The details for creating this Usage Connect integration can be found in the Create Usage Connect documentation.

Added

Usage Connect

Create Usage Connect Integration

• A new endpoint to create a Usage Connect integration. Follow the Create Usage Connect documentation for a step-by-step on how to create an integration.

Improved

Integrations

Get Integrations

Get Integrations by Id

• There is now a mappings array that can be returned for usageconnect type integrations. This will show the mappings for the Usage Connect integration.

Changes to the GET query for contracts when filtering on application_id. This should now match the information about a contract when view the same record in app.

Fixed

Contracts

• When trying to filter contracts on a specific application_id the query was not handling the relationship a contract has to contractLineItems if a contract originally did not include lines items but then was changed to have line items.

Small improvements to the query requirements for applicationUsers and the response from zybrary.

Improved

Application Users

• The applicationId is no longer required for the GET request.
• The application_data object is only returned when here is an applicationId filter.

Zybrary

• The supplier_id is now returned on a Zybrary object response.
• The "Get Zybrary" operation now requires one of the following query parameters: search, app_domain, id, app_name.

Three new endpoints have been added to manage Zylo Users in the Zylo application.

Zylo Users are users who have an account within Zylo and can log into the application.

Added

Zylo Users

Get Zylo Users

• An endpoint to get "Zylo Users" from your Zylo instance.

Get Integration by Id

• An endpoint to retrieve a single "Zylo User" by its id.

Create Zylo User

• An endpoint to add a new "Zylo User" to your Zylo application.
• Currently, only companies that have SAML enabled can add a new Zylo User programmatically.

Update Zylo User by Id

• An endpoint to update a "Zylo User" by its id.
• Important note, when updating the permissions of a Zylo User, the new permissions will overwrite the existing permissions.

Delete Zylo User by Id

• An endpoint to delete a "Zylo User" by its id.