Zylo Data Dictionary

Complete reference of all fields available across Zylo resources for building queries and managing data.

Alerts

Resource name: alerts

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application this alert is associated with.	Yes	Yes	No
`contract_id`	UUID	Unique identifier for the contract this alert is associated with.	Yes	Yes	No
`id`	UUID	Unique identifier for an alert.	No	No	No
`last_processed_date`	datetime	Date and time the alert was last processed by the system.	Yes	No	No
`memo`	string	The alert memo. This is additional information included in the alert notification.	Yes	Yes	Yes
`method`	string	Alert delivery method. There are three methods for delivery; email, slack, and teams. Email is configured to work out of the box but the other two require additional setup.	Yes	No	No
`owner`	email	Email address of the Owner. The email must belong to a user in the Zylo system.	Yes	Yes	Yes
`settings`	object	Dynamic configuration for the alert, including recipients and type-specific settings.	Yes	Yes	Yes
`type`	string	Type of alert. There are three types of alerts; contract-renewal, renewal, and transaction.	Yes	Yes	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No
`zylo_user_account_id`	UUID		Yes	No	No

Application Budget Stats

Resource name: application_budget_stats

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for an application.	No	No	No
`current_fiscal_year_budget`	currency	Budget for fiscal year aggregated from Financial integration or uploaded financial data.	Yes	No	No
`id`	UUID	Unique identifier for an application budget.	No	No	No
`last_fiscal_year_budget`	currency	Budget for last fiscal year aggregated from Financial integration or uploaded financial data.	Yes	No	No
`next_fiscal_year_budget`	currency	Budget for next fiscal year aggregated from Financial integration or uploaded financial data.	Yes	No	No
`percent_budget_used_year_to_date`	percentage	Total percent of spend against the current fiscal year budgeted amount.	Yes	No	No
`two_years_ago_fiscal_year_budget`	currency	Budget for 2 years ago fiscal year aggregated from Financial integration or uploaded financial data.	Yes	No	No
`yoy_budget_change`	percentage	Budget change from last fiscal year to current fiscal year aggregated from Financial integration or uploaded financial data.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Application Budgets

Resource name: application_budgets

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for an application.	No	Yes	Yes
`budget_amount`	number	The budget amount for the fiscal year.	Yes	Yes	Yes
`id`	UUID	Unique identifier for an application budget.	No	No	No
`year`	number	The fiscal year for the budget.	Yes	Yes	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Application Licenses

Resource name: application_licenses

Field	Type	Description	Nullable	Can Add	Can Update
`active`	boolean	Whether the license is currently active.	Yes	No	No
`application_id`	UUID	The application this license is assigned to.	Yes	No	No
`external_user_id`	string	The user identifier from the external integration.	Yes	No	No
`id`	UUID	Unique identifier for an application license record.	No	No	No
`is_paid_license`	boolean	Whether this is a paid license.	Yes	No	No
`last_activity_date`	datetime	The date of the last activity for this license assignment.	Yes	No	No
`license_type`	string	The type of license (e.g., user, feature, permission_set, custom).	Yes	No	No
`name`	string	The name of the license.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No

Application Security

Resource name: application_security

Field	Type	Description	Nullable	Can Add	Can Update
`c5_germany`	boolean	Whether the vendor holds the BSI C5 attestation (Germany).	Yes	No	No
`category_name`	string	Application category from Netskope's catalog (e.g., Collaboration, CRM, HR).	Yes	No	No
`cci`	number	Cloud Confidence Index — a 0–100 score from Netskope. Higher is more trustworthy.	Yes	No	No
`ccl`	string	Cloud Confidence Level — bucketed risk tier derived from CCI. One of Low, Medium, High, Excellent.	Yes	No	No
`cobit`	boolean	Whether the vendor is COBIT aligned.	Yes	No	No
`confirmed`	boolean	Whether the match between the application and the Netskope catalog entry has been confirmed.	Yes	No	No
`cyber_essentials_uk`	boolean	Whether the vendor holds Cyber Essentials / Cyber Essentials Plus (UK).	Yes	No	No
`fedramp`	boolean	Whether the vendor is FedRAMP authorized.	Yes	No	No
`fisma`	boolean	Whether the vendor is FISMA compliant.	Yes	No	No
`gapp`	boolean	Whether the vendor adheres to GAPP (Generally Accepted Privacy Principles).	Yes	No	No
`hipaa`	boolean	Whether the vendor is HIPAA compliant.	Yes	No	No
`hitrust`	boolean	Whether the vendor holds a HITRUST certification.	Yes	No	No
`id`	UUID	Zybrary application id this security record describes. Join `applications.zybrary_id` against this field to attach security data to a company app.	No	No	No
`iso_27001`	boolean	Whether the vendor is ISO/IEC 27001 certified.	Yes	No	No
`iso_iec27018`	boolean	Whether the vendor is ISO/IEC 27018 certified.	Yes	No	No
`manually_matched`	boolean	Whether the Netskope catalog match was made manually (true) or by automated matching (false).	Yes	No	No
`netskope_application_domain`	string	Application domain as recorded in Netskope's catalog.	Yes	No	No
`netskope_application_name`	string	Application name as recorded in Netskope's catalog. Useful for verifying the match.	Yes	No	No
`nist_sp80053`	boolean	Whether the vendor follows NIST SP 800-53 controls.	Yes	No	No
`pci_dss`	boolean	Whether the vendor is PCI DSS compliant.	Yes	No	No
`privacy_mark_japan`	boolean	Whether the vendor holds the Japan Privacy Mark.	Yes	No	No
`privacy_shield`	boolean	Whether the vendor is Privacy Shield certified (note: framework status varies by jurisdiction).	Yes	No	No
`sas70_ssae16_ssae18`	boolean	Whether the vendor has SAS 70 / SSAE 16 / SSAE 18 attestations.	Yes	No	No
`soc_1`	boolean	Whether the vendor holds a SOC 1 attestation.	Yes	No	No
`soc_2`	boolean	Whether the vendor holds a SOC 2 attestation.	Yes	No	No
`soc_3`	boolean	Whether the vendor holds a SOC 3 attestation.	Yes	No	No
`trustarc`	boolean	Whether the vendor is TrustArc certified.	Yes	No	No
`zylo_created_at`	datetime	Date and time the security record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the security record was last modified in Zylo.	Yes	No	No

Application Users

Resource name: application_users

Field	Type	Description	Nullable	Can Add	Can Update
`active`	boolean	If user has activity within the application activity threshold.	Yes	No	No
`application_data`	object	Application specific data related to the application user. Varies per integration type.	Yes	No	No
`application_id`	UUID	Unique identifier for an application.	Yes	No	No
`days_active`	number	Number of days the user has been active within the application activity threshold.	Yes	No	No
`email`	email	Email for the application user.	Yes	No	No
`external_user_id`	string	The unique identifier for the application user in the external system.	Yes	No	No
`first_name`	string	First name of the application user.	Yes	No	No
`full_name`	string	Full name of the application user.	Yes	No	No
`id`	UUID	Unique identifier for an application user.	No	No	No
`integration_type`	string	The type of integration that the application user is associated with.	Yes	No	No
`is_paid_user`	boolean	If the application user's license is considered paid.	Yes	No	No
`last_activity_date`	date	The date of the last activity for the application user.	Yes	No	No
`last_name`	string	Last name of the application user.	Yes	No	No
`license_names`	array	The license names from the application associated with the application user.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Applications

Resource name: applications

Field	Type	Description	Nullable	Can Add	Can Update
`activity_threshold`	number	Threshold in days compared against a user's last activity to determine whether the user is Active. 90 days by default and editable on Subscription details page.	Yes	Yes	Yes
`app_label`	string	The label for the application.	Yes	Yes	Yes
`app_name`	string	The name of the application.	Yes	No	No
`application_owner_user_email`	email	Manually selected email address of the Application Owner.	Yes	Yes	Yes
`business_goals`	string	Business goals of the application.	Yes	Yes	Yes
`business_owner_user_email`	email	Manually selected email address of the Business Owner.	Yes	Yes	Yes
`business_unit`	string	Manually selected team that primarily owns the management of the application.	Yes	Yes	Yes
`category`	string	Zylo-managed or internally-managed Category of the application.	Yes	Yes	Yes
`custom_fields`	object	Values for custom fields associated with this Application.	Yes	No	No
`holds_pii`	boolean	Manually selected field to identify which applications contain Personally Identifiable Information (PII) on users.	Yes	Yes	Yes
`id`	UUID	Unique identifier for an application.	No	No	No
`is_cloud`	boolean	Manually selected field to indicate if application is cloud delivered or on-premises.	Yes	No	No
`is_direct_integration`	boolean	Field to indicate if application has an available direct integration.	Yes	No	No
`is_price_benchmarks`	boolean	Field to indicate if application has an available Zylo Price Benchmark.	Yes	No	No
`is_saml`	boolean	Field to indicate if application is SAML capable.	Yes	No	No
`it_owner_user_email`	email	Manually selected email address of the IT Owner.	Yes	Yes	Yes
`it_supported`	boolean	Manually selected field to indicate if supported internally by IT.	Yes	Yes	Yes
`last_processed_date`	datetime	The last date the application was processed by its data source.	Yes	No	No
`launch_url`	string	The URL to launch the application.	Yes	No	No
`next_action`	string	Manually selected pick list field to identify what action needs to be taken next on an application.	Yes	Yes	Yes
`payment_method`	string	Approved method in which the vendor is compensated as entered in contract details for the application.	Yes	No	No
`source`	array	The sources of all data on an Application, including payments, imports and integrations	Yes	No	No
`sso_enforced`	boolean	Manually selected field to identify which applications are enforced behind Single Sign On provider.	Yes	Yes	Yes
`status`	string	Status of the application. Active includes any application not cancelled, expired or deleted. Expired includes any application where the Contract End Date is in the past. Cancelled include any application that is manually cancelled via the Subscription details page.	Yes	Yes	Yes
`subcategory`	string	Zylo-managed or internally-managed Subcategory of the application.	Yes	Yes	Yes
`supplier_id`	UUID	The id for the supplier associated with the application, if applicable.	Yes	No	No
`tags`	array	Custom tags that have been applied to an Application.	Yes	Yes	Yes
`true_up`	boolean	Manually selected field to indicate if true-ups are required by the application supplier.	Yes	Yes	Yes
`zybrary_id`	UUID	The sources of all data on an Application, including payments, imports and integrations	No	Yes	No
`zylo_created_at`	datetime	Date the application was added to Zylo, via Discovery from financial data, an Integration or mannually added.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Company

Resource name: company

Field	Type	Description	Nullable	Can Add	Can Update
`currency`	string	The default currency used by the company (e.g., USD, EUR).	Yes	No	No
`employee_roster`	string	The employee roster source for the company.	Yes	No	No
`employee_roster_integration_id`	UUID	The integration ID of the employee roster.	Yes	No	No
`fiscal_year_settings`	object	The fiscal year configuration settings for the company.	Yes	No	No
`id`	UUID	Unique identifier for the company.	No	No	No
`name`	string	The name of the company.	Yes	No	No
`timezone`	string	The timezone preference for the company (e.g., America/New_York).	Yes	No	No

Company Documents

Resource name: company_documents

Field	Type	Description	Nullable	Can Add	Can Update
`byte_size`	string	File size in bytes.	Yes	No	No
`content_type`	string	MIME type of the uploaded file (e.g., application/pdf, image/jpeg).	Yes	No	No
`description`	string	Description of the uploaded document.	Yes	No	No
`external_document_id`	string	External ID for the document if fetched from an external system (e.g., Coupa).	Yes	No	No
`filename`	string	Name of the uploaded file.	Yes	No	No
`id`	UUID	Unique identifier for the company document.	No	No	No
`status`	string	Processing status of the document. U = Uploading, A = Active (processed), E = Error.	Yes	No	No
`zylo_created_at`	datetime	Date and time the document was created.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the document was last modified.	Yes	No	No
`zylo_user_account_id`	UUID	ID of the Zylo user account who created this document.	Yes	No	No

Contract Line Items

Resource name: contract_line_items

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application associated with the contract line item.	Yes	Yes	Yes
`company_app_id_manually_set`	boolean		Yes	No	Yes
`contract_id`	UUID	Unique identifier for the contract associated with the contract line item.	No	Yes	No
`end_date`	date	Contract line end date; If null, contract is ongoing.	Yes	Yes	Yes
`id`	UUID	Unique identifier for a contract line item.	No	No	No
`license_name`	string	The optional label given to the contract line item license.	Yes	Yes	Yes
`license_type`	string	The type of licenses associated with the contract line item.	Yes	Yes	Yes
`line_description`	string	Identifier for the contract line item.	Yes	Yes	Yes
`native_currency`	string	Currency code of the currency the contract value is in.	Yes	Yes	Yes
`native_unit_price`	currency	Unit price for the line item in the value of the native_currency.	Yes	Yes	Yes
`quantity`	number	Quantity of the contract line item.	Yes	Yes	Yes
`source`	string	Source system of the contract line.	Yes	No	No
`start_date`	date	Contract line item start date.	Yes	Yes	Yes
`total_price`	currency	Total quantity multiplied by the unit_price.	Yes	No	No
`unit_of_measure`	string	The unit of measurement for the contract line item.	Yes	Yes	Yes
`unit_price`	currency	Unit price for the line item. Currency is converted if the Native Currency is different than the global currency set in Zylo. Zylo uses the currency exchange rate of the line item start_date.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Contracts

Resource name: contracts

Field	Type	Description	Nullable	Can Add	Can Update
`account_number`	string	The account number associated with the contract.	Yes	Yes	Yes
`application_id`	UUID	The application associated with the contract. This is only set for single-application contracts. When a contract has line items, each application is associated through its line items instead, and this field is empty.	Yes	Yes	Yes
`billing_frequency`	string	Billing frequency for the contract.	Yes	Yes	Yes
`can_have_contract_lines`	boolean	Indicates if the contract can have lines added	Yes	Yes	Yes
`cancellation_policy`	string	Cancellation policy for the contract.	Yes	Yes	Yes
`contract_term`	string	The term of duration of the contract.	Yes	Yes	Yes
`contract_value_year`	array[number]	Contract values by year for the contract.	Yes	No	No
`current_year_contract_value`	currency	Contract Year value that best relates to the Current Year.	Yes	No	No
`end_date`	date	End date of the contract. This is required unless the contract field `month_to_month` is `true`.	Yes	Yes	Yes
`external_id`	string	Identifier of the contract in its source system.	Yes	No	No
`external_source_link`	string	External link to contract data source.	Yes	No	No
`has_contract_lines`	boolean	Indicates if the contract can have lines added	Yes	No	No
`id`	UUID	Unique identifier for a contract.	No	No	No
`month_to_month`	boolean	Indicates if the contract is auto-renewing.	Yes	Yes	Yes
`name`	string	The contract name.	No	Yes	Yes
`native_contract_value_year`	array[number]	Total native value of the contract as entered in the contract record.	Yes	Yes	Yes
`native_currency`	string	Currency code of the currency the contract value is in.	Yes	Yes	Yes
`native_total_contract_value`	currency	Total native value of the contract as entered in the contract record.	Yes	Yes	Yes
`notification_period`	string	Length of notice required to submit contract termination to supplier.	Yes	Yes	Yes
`number`	string	Contract Number from source system.	No	Yes	Yes
`owner`	string	Name of the primary contact for the contract.	Yes	Yes	Yes
`owner_manually_set`	boolean	The owner was set manually.	Yes	No	Yes
`payment_method`	string	Payment method of the contract.	Yes	Yes	Yes
`payment_term`	string	The terms of payment for the contract.	Yes	Yes	Yes
`price_protection`	boolean	Is there price protection built into the contract.	Yes	Yes	Yes
`purchase_order_number`	array	Purchase Order Number associated to this contract.	Yes	Yes	Yes
`remit_to_address`	string	Remittance address for this contract.	Yes	Yes	Yes
`renewal_state`	string	Next steps for renewal of this contract.	Yes	Yes	Yes
`reseller`	string	Reseller name for the contract.	Yes	Yes	Yes
`source`	string	Source system of the contract.	Yes	No	No
`start_date`	date	Start date of the contract.	Yes	Yes	Yes
`status`	string	Status of the contract based on the current date and the contract start and end dates. "Active" indicates the contract is currently valid, "Expired" indicates the contract has ended, and "Inactive" indicates the contract has not yet started.	No	No	No
`supplier_id`	UUID	Supplier is the publisher of the Application(s) associated with this Contract. Please note that this may not represent the supplier you purchase from if your contract is through a reseller.	Yes	Yes	Yes
`supplier_manually_set`	boolean	The supplier was set manually.	Yes	No	Yes
`supplier_name`	string	Supplier is the publisher of the Application(s) associated with this Contract. Please note that this may not represent the supplier you purchase from if your contract is through a reseller.	Yes	No	No
`total_contract_value`	currency	Total value of the contract as entered in the contract record. Currency is converted if the Native Currency is different than the global currency set in Zylo. Zylo uses the currency exchange rate of the Contract Start Date.	Yes	No	No
`total_licenses`	number	The total licenses for the contract.	Yes	No	No
`type`	array	The type of contract recorded.	Yes	Yes	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Custom Fields

Resource name: custom_fields

Field	Type	Description	Nullable	Can Add	Can Update
`description`	string	The custom field description.	Yes	Yes	Yes
`id`	UUID	Unique identifier for a custom field.	No	No	No
`is_enabled`	boolean	Indicates whether the custom field is enabled or not.	Yes	Yes	Yes
`is_key`	boolean	Indicates whether the custom field is a key field or not.	Yes	No	No
`name`	string	The custom field name.	No	Yes	No
`options`	object	The options of the custom field.	Yes	Yes	No
`position`	number	The position of the custom field.	Yes	Yes	Yes
`section`	string	The custom field section.	No	No	No
`type`	string	The type of the custom field.	No	Yes	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Functionalities

Resource name: functionalities

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application associated with the functionality.	No	No	No
`functionality_name`	string	The functionality name.	Yes	No	No
`id`	UUID	Unique identifier for a functionality.	No	No	No
`is_active`	boolean	Whether or not the functionality is active.	Yes	No	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Integrations

Resource name: integrations

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application associated with the integration.	Yes	No	No
`application_name`	string	The name of the application associated with the integration.	Yes	No	No
`error_message`	string	The error message for the integration.	Yes	No	No
`external_organization_id`	string	The unique ID of the instance in the third party provider.	Yes	No	No
`id`	UUID	Unique identifier for an integration.	No	No	No
`last_fetch_date`	date	The last date integration data was fetched.	Yes	No	No
`last_processed_date`	date	The date in which the integration was last processed.	Yes	No	No
`mapped_apps_failed_count`	number	Only applicable for SSO integrations. The number of mapped applications that failed to run.	Yes	No	No
`mapped_apps_running_count`	number	Only applicable for SSO integrations. The number of mapped applications that are currently running.	Yes	No	No
`mapped_apps_succeeded_count`	number	Only applicable for SSO integrations. The number of mapped applications that have succeeded.	Yes	No	No
`mappings`	array	The mapping for the integration, only available for Usage Connect.	Yes	No	No
`status`	string	The status of the integration.	Yes	No	No
`type`	string	The type of integration.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Payment Imports

Resource name: payment_imports

Field	Type	Description	Nullable	Can Add	Can Update
`id`	UUID	The payment id.	No	No	No
`import_type`	string	The source and expense type of file that was uploaded.	Yes	No	No
`original_file`	string	The original name of the uploaded file.	Yes	No	No
`row_error`	number	Count of errored rows in file. This count is only ever populated when the file comes from an integration connection.	Yes	No	No
`row_match`	number	Count of matched rows in file. This count is only ever populated when the file comes from an integration connection.	Yes	No	No
`row_unmatch`	number	Count of unmatched rows in file. This count is only ever populated when the file comes from an integration connection.	Yes	No	No
`status`	string	Current status of the uploaded file. Possible values include: "U" (Uploaded), "P" (Processing), "C" (Completed), "E" (Error).	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Software Charges

Resource name: payments

Field	Type	Description	Nullable	Can Add	Can Update
`amount`	currency	Line item amount of the payment, mapped from financial data source.	Yes	No	No
`application_id`	UUID	Threshold in days compared against a user's last activity to determine whether the user is Active. 90 days by default and editable on Subscription details page.	Yes	No	No
`associated`	string		Yes	No	No
`cost_center`	string	Cost center of the payment, mapped from financial data source.	Yes	No	No
`email`	email	User responsible for expense transaction mapped from financial data source.	Yes	No	No
`email_domain`	string		Yes	No	No
`expense_type`	string	Expense type of the payment (e.g. Software & Subscriptions), mapped from financial data source.	Yes	No	No
`external_po_number`	string	Purchase Order Number as identified by the financial source system.	Yes	No	No
`id`	UUID	The payment id.	No	No	No
`metadata`	object	Raw financial data and fields in addition to standard payment detail.	Yes	No	No
`payment_date`	date	Date the payment occurred (e.g. Paid Date or Transaction Date), mapped from financial data source.	Yes	No	No
`payment_description`	string	Description of the transaction, mapped from financial data source.	Yes	No	No
`payment_name`	string	Name of payment, vendor, or supplier, mapped from financial data source.	Yes	No	No
`payment_type`	string	Zylo's classification of the payment, AP (accounts payable) or Expense, based on the financial data source.	Yes	No	No
`po_line_item_id`	UUID	The ID for the PO Line Item associated to this Payment.	Yes	No	No
`purchase_order_id`	UUID	The ID for the Purchase Order associated to this Payment.	Yes	No	No
`reseller`	string	Reseller the payment was processed through.	Yes	No	No
`source`	string	Financial source of the payment.	Yes	No	No
`supplier_name`	string	Name of the supplier, mapped from financial data source.	No	No	No
`transaction_id`	string	Unique transaction ID of the payment, mapped from financial data source if available, or a Zylo-generated unique ID.	Yes	No	No
`zybrary_supplier_id`	UUID	The id for the Zybrary supplier. Found on the "Zybrary" resource	No	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Pending Contract Line Items

Resource name: pending_contract_line_items

Field	Type	Description	Nullable	Can Add	Can Update
`app_name`	string	Name of the application associated with this line item.	Yes	No	No
`application_id`	UUID	The application associated with this line item.	Yes	No	No
`end_date`	date	Ending date of the pending contract line item. May be null for ongoing contracts.	Yes	No	No
`id`	UUID	Unique identifier for the pending contract line item.	No	No	No
`license_name`	string	The name of the license.	Yes	No	No
`license_type`	string	The type of license for this pending contract line item.	Yes	No	No
`line_description`	string	Description of the product the licenses represent.	Yes	No	No
`line_item_number`	number	Ordinal number for this line item as it appears in the contract (1-based).	Yes	No	No
`native_currency`	string	Native currency the pending contract line item was made out for.	Yes	No	No
`native_unit_price`	currency	Unit price in the native currency.	Yes	No	No
`pending_contract_id`	UUID	The parent pending contract this line item belongs to.	No	No	No
`quantity`	string	Quantity of licenses on the line item.	Yes	No	No
`start_date`	date	Beginning date of the pending contract line item.	Yes	No	No
`total_price`	currency	Estimated total price over the life of the pending contract line.	Yes	No	No
`unit_of_measure`	string	Unit of measure for the license quantity.	Yes	No	No
`unit_price`	currency	Price per license.	Yes	No	No
`zylo_created_at`	datetime	Date and time the line item was created.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the line item was last modified.	Yes	No	No

Pending Contracts

Resource name: pending_contracts

Field	Type	Description	Nullable	Can Add	Can Update
`billing_frequency`	string	How often billing occurs (e.g., monthly, annually).	Yes	No	No
`cancellation_policy`	string	The cancellation policy for the pending contract.	Yes	No	No
`company_document_id`	UUID	The company document associated with this pending contract.	No	No	No
`contract_term`	string	Contract term type (Fixed, Auto-renewed, or Perpetual).	Yes	No	No
`created_by`	string	Who uploaded the contract document.	Yes	No	No
`end_date`	date	Pending contract end date. May be null for ongoing contracts.	Yes	No	No
`id`	UUID	Unique identifier for the pending contract.	No	No	No
`is_reviewed`	boolean	Whether the AI-extracted data has been reviewed by a human.	Yes	No	No
`month_to_month`	boolean	Whether this is a recurring payment contract.	Yes	No	No
`name`	string	Name of the pending contract, typically derived from the uploaded document filename.	Yes	No	No
`native_currency`	string	Currency the pending contract was made out for.	Yes	No	No
`native_total_contract_value`	currency	Estimated total value of the pending contract in native currency.	Yes	No	No
`notification_period`	string	Required notification period before contract changes.	Yes	No	No
`number`	string	Pending contract number extracted from the document.	Yes	No	No
`owner`	string	Person responsible for administering the pending contract.	Yes	No	No
`source`	string	The source of the contract data (e.g., API, manual upload).	Yes	No	No
`start_date`	date	Pending contract start date.	Yes	No	No
`supplier_id`	UUID	The supplier associated with this pending contract.	Yes	No	No
`zylo_created_at`	datetime	Date and time the pending contract was created (upload date).	Yes	No	No
`zylo_modified_at`	datetime	Date and time the pending contract was last modified.	Yes	No	No

PO Line Items

Resource name: po_line_items

Field	Type	Description	Nullable	Can Add	Can Update
`amount`	currency	The amount of allocated spend for the PO line item.	Yes	No	No
`application_id`	UUID	Unique identifier for the application associated with the purchase order line item.	Yes	No	No
`commodity_category`	string	Commodity category of the PO Line Item.	Yes	No	No
`commodity_name`	string	Commodity Type of the PO Line Item.	Yes	No	No
`department_name`	string	Department name of the PO Line Item.	Yes	No	No
`description`	string	The description provided for this PO Line Item.	Yes	No	No
`expense_type`	string	Expense type of the PO Line Item.	Yes	No	No
`external_created_at`	datetime	The date the source system reported as the creation date of the purchase order line item.	Yes	No	No
`id`	UUID	Unique identifier for a purchase order line item.	No	No	No
`is_saas`	boolean	Is this PO Line Item related to SaaS spend (Included).	Yes	No	No
`order_line_number`	string	PO Line Order Number.	Yes	No	No
`percent_spend_against`	percentage	Percentage of spend made against the approved purchase order line amount.	Yes	No	No
`purchase_order_id`	UUID	Unique identifier for the purchase order associated with the purchase order line item.	Yes	No	No
`remaining_spend_against`	currency	Remaining amount of associated spend against the purchase order line item.	Yes	No	No
`requestor_name`	string	Requestor name of the PO Line Item.	Yes	No	No
`source`	string	Source system of the PO Line Item.	Yes	No	No
`supplier_account_number`	string	Supplier account number of the PO Line Item.	Yes	No	No
`supplier_name`	string	Supplier name of the PO Line Item.	Yes	No	No
`supplier_number`	string	Supplier number of the PO Line Item.	Yes	No	No
`supplier_order_number`	string	Supplier order number of the PO Line Item.	Yes	No	No
`total_spend_against`	currency	Total amount on the related charge.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Purchase Orders

Resource name: purchase_orders

Field	Type	Description	Nullable	Can Add	Can Update
`account_number`	string	The account number associated with the purchase order.	Yes	No	No
`amount`	currency	Total approved amount of the purchase order.	Yes	No	No
`contract_message`	string	Details of the contract creation.	Yes	No	No
`external_closed_at`	date	The date the source system reported as the close date of the purchase order.	Yes	No	No
`external_created_at`	date	The date the source system reported as the creation date of the purchase order.	Yes	No	No
`id`	UUID	Unique identifier for a purchase order.	No	No	No
`metadata`	object	Raw source system data.	Yes	No	No
`number`	string	The number of the purchase order.	Yes	No	No
`percent_spend_against`	percentage	Total percent of associated spend against the purchase order's approved amount.	Yes	No	No
`remaining_spend_against`	currency	Remaining amount of associated spend against the purchase order.	Yes	No	No
`requisition_number`	string	The requisition number associated with the purchase order.	Yes	No	No
`source`	string	Source system of the purchase order.	Yes	No	No
`status`	string	The status of the purchase order.	Yes	No	No
`supplier_id`	UUID	The unique identifier for the supplier associated with the purchase order.	Yes	No	No
`total_spend_against`	currency	Total associated spend against the purchase order.	Yes	No	No
`vendor_name`	string	The name of the vendor associated with the purchase order.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Report Jobs

Resource name: report_jobs

Field	Type	Description	Nullable	Can Add	Can Update
`error_message`	string	The error message associated with the report job, if any.	Yes	No	No
`id`	UUID		No	No	No
`query`	object	The query used to generate the report.	Yes	No	No
`rows`	number	The number of rows in the generated report.	Yes	No	No
`status`	string	The current status of the report job. "E" - The job has errored and will be not be available for download. "P" - The job is currently processing. "C" - The job has completed and is available for download.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No

Savings Events

Resource name: savings_events

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application related to the savings event.	Yes	Yes	Yes
`description`	string	Description of the savings event.	Yes	Yes	Yes
`event_type`	string	Type of the savings event.	Yes	Yes	Yes
`exclude_from_event_total`	boolean	If checked, event will be excluded from aggregated event statistics and total event count.	Yes	Yes	Yes
`id`	UUID	Unique identifier for a savings event.	No	No	No
`is_custom`	boolean	Yes/No field to indicate if the event is custom or created by Zylo.	Yes	No	No
`monetary_value`	currency	Monetary value of the savings event.	Yes	Yes	Yes
`name`	string	Name of the savings event.	Yes	Yes	Yes
`notes`	string	Notes of the savings event.	Yes	Yes	Yes
`numerical_value`	string	The numerical value of the savings event. This must be not null if the unit of measure is not null.	Yes	Yes	Yes
`origin`	string	Indicates if the savings event is system or user generated.	Yes	No	No
`savings_per_unit`	number	Savings per unit for the savings event.	Yes	No	No
`transaction_date`	date	Date of the transaction for the savings event.	Yes	Yes	Yes
`unit_of_measure`	string	The unit of measure for the numerical value of the savings event. This must be not null if the numerical value is not null.	Yes	Yes	Yes
`user_override`	boolean	Whether or not the savings event has been overridden with data by the user.	Yes	No	Yes
`value_type`	string	The value type category for the savings event.	Yes	Yes	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Suppliers

Resource name: suppliers

Field	Type	Description	Nullable	Can Add	Can Update
`description`	string	The supplier description.	Yes	No	No
`domain`	string	The supplier domain.	Yes	No	No
`id`	UUID	The supplier id.	No	No	No
`name`	string	The supplier name.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Unmatched Payments

Resource name: unmatched_payments

Field	Type	Description	Nullable	Can Add	Can Update
`amount`	currency	Line item amount of the payment, mapped from payment data source.	Yes	No	No
`expense_type`	string	Expense type of the payment (e.g. Software & Subscriptions), mapped from payment data source.	Yes	No	No
`external_po_number`	string	Purchase Order Number as identified by the payment source system.	Yes	No	No
`id`	UUID	The unmatched payment id.	No	No	No
`payment_date`	date	Date the payment occurred (e.g. Paid Date or Transaction Date), mapped from payment data source.	Yes	No	No
`payment_description`	string	Description of the transaction, mapped from payment data source.	Yes	No	No
`payment_name`	string	Name of payment, vendor, or supplier, mapped from payment data source.	Yes	No	No
`payment_type`	string	Zylo's classification of the payment, AP (accounts payable) or Expense, based on the payment data source.	Yes	No	No
`po_line_item_id`	UUID	The ID for the PO Line Item associated to this payment.	Yes	No	No
`purchase_order_id`	UUID	The ID for the Purchase Order associated to this payment.	Yes	No	No
`reseller`	string	Reseller the payment was processed through.	Yes	No	No
`saas_confidence`	string	This score represents the confidence of Zylo's proprietary AI model in classifying a payment as SaaS spend. Higher scores indicate greater certainty in the classification.	Yes	No	No
`source`	string	Source of the payment.	Yes	No	No
`supplier_name`	string	Name of the supplier associated with this payment.	Yes	No	No
`transaction_id`	string	Unique transaction ID of the payment, mapped from payment data source if available, or a Zylo-generated unique ID.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No

Usage Connect

Resource name: usage_connect

Field	Type	Description	Nullable	Can Add	Can Update
`app_label`	string	The label for the application.	Yes	No	No
`application_id`	UUID	Unique identifier for the application associated with the usage connection.	No	No	No
`data_type`	string	The type of data imported through the connection.	Yes	No	No
`delivery_method`	string	The process in which the data is being imported.	Yes	No	No
`errored_rows`	number	Number of rows that had an error.	Yes	No	No
`file_name`	string	The display name on the imported file.	Yes	No	No
`id`	UUID	Unique identifier for the usage connection import job.	No	No	No
`import_status`	string	The state of the file import.	Yes	No	No
`integration_id`	UUID	Unique identifier for the integration associated with the usage connection.	No	No	No
`message`	string	This field contains information about the connection. It may contain error details or status updates.	Yes	No	No
`successful_rows`	number	Number of rows that successfully imported.	Yes	No	No
`upload_date`	datetime	The date the file was uploaded.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No

Users

Resource name: users

Field	Type	Description	Nullable	Can Add	Can Update
`apps_owned`	number	Number of applications that the user has been set as one of the types of "owner" within Zylo: Application Owner, Business Owner, or IT Owner.	Yes	No	No
`date_disabled`	date	The date at which the user's status was marked as disabled.	Yes	No	No
`email`	email	A user's email via any direct, HR, or SSO integration.	Yes	No	No
`email_domain`	string	The email domain of the user's email.	Yes	No	No
`external_status`	string	User's external status as it comes in directly from your Employee Roster.	Yes	No	No
`full_name`	string	A user's full name via any direct, HR, SSO integration, or will be pulled from the Employee Roster if one is setup. Use the link below for setup steps.	Yes	No	No
`id`	UUID	A user's Zylo id.	No	No	No
`in_employee_roster`	boolean	Whether a non-disabled user's email is present in the Employee Roster.	Yes	No	No
`is_archived`	boolean	Marked as archived if Zylo account has been deleted from the Team page.	Yes	No	No
`notes`	string	Any notes a Zylo account has associated with a user.	Yes	Yes	Yes
`tags`	array	Any tags a Zylo account has associated with a user.	Yes	Yes	Yes
`user_data`	object	Data about the user from the Employee Roster. Any inner key can be referenced with dot notation (e.g. `user_data.department`).	Yes	No	No
`zylo_created_at`	datetime	Date and time the user was first added to Zylo, either by an admin or from an integration.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No
`zylo_status`	string	Whether a user is considered active or disabled based on your External Status from your Employee Roster.	Yes	No	No

View Applications

Resource name: view_applications

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for an Application.	No	Yes	Yes
`id`	string		Yes	No	No
`view_id`	UUID	Unique identifier for a view.	No	Yes	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No

View Zylo Users

Resource name: view_zylo_users

Field	Type	Description	Nullable	Can Add	Can Update
`id`	string		Yes	No	No
`view_id`	UUID	Unique identifier for a view.	No	Yes	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No
`zylo_user_id`	UUID	Unique identifier for a Zylo user.	No	Yes	Yes

Views

Resource name: views

Field	Type	Description	Nullable	Can Add	Can Update
`id`	UUID	Unique identifier for the view.	No	No	No
`is_dynamic`	boolean	Whether the view is dynamically adjusting applications within the view.	Yes	No	No
`name`	string	Name of the view. Must be unique.	Yes	Yes	Yes
`zylo_created_at`	datetime	Date and time the view was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the view was last modified in Zylo.	Yes	No	No

Workflow Responses

Resource name: workflow_responses

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application associated with the workflow response.	Yes	No	No
`email`	email	Email for the user responding to the workflow.	Yes	No	No
`id`	UUID	Unique identifier for a workflow response.	No	No	No
`response`	boolean	Whether the user responded to the workflow.	Yes	No	No
`response_at`	date	The date the user responded to the workflow.	Yes	No	No
`response_text`	string	The user's text response to the workflow.	Yes	No	No
`workflow_id`	UUID	Unique identifier for the workflow associated with the workflow response.	No	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Workflows

Resource name: workflows

Field	Type	Description	Nullable	Can Add	Can Update
`application_id`	UUID	Unique identifier for the application associated with the workflow.	Yes	No	No
`current_step`	string	The current step of the workflow.	Yes	No	No
`current_step_index`	number	The current step index of the workflow.	Yes	No	No
`id`	UUID	Unique identifier for a workflow.	No	No	No
`last_day_to_respond`	string	The last day to respond to the workflow.	Yes	No	No
`name`	string	The name of the workflow.	Yes	No	No
`status`	string	The status of the workflow.	Yes	No	No
`total_step_count`	number	The total step count of the workflow.	Yes	No	No
`users_actioned`	number	The number of users who have taken action on the workflow.	Yes	No	No
`users_qualified`	number	The number of users who have met the criteria for the workflow.	Yes	No	No
`users_responded`	string	The number of users who have responded to the workflow.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo. Uses the created date by default.	Yes	No	No

Zybrary

Resource name: zybrary

Field	Type	Description	Nullable	Can Add	Can Update
`app_description`	string	The application description.	Yes	No	No
`app_domain`	string	The application domain.	Yes	No	No
`app_name`	string	The application name.	Yes	No	No
`id`	UUID	Unique identifier for a Zybrary application.	No	No	No
`zybrary_supplier_id`	UUID	The supplier id associated with the application, if applicable.	Yes	No	No
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No

Zylo Users

Resource name: zylo_users

Field	Type	Description	Nullable	Can Add	Can Update
`email`	email	The email of the Zylo user.	Yes	Yes	No
`first_name`	string	The first name of the Zylo user.	Yes	Yes	No
`id`	UUID	Unique identifier for a Zylo user.	No	No	No
`in_view`	boolean	Whether the Zylo user is in a view.	Yes	No	No
`last_login`	datetime	The date and time of the last login for the Zylo user.	Yes	No	No
`last_name`	string	The last name of the Zylo user.	Yes	Yes	No
`permissions`	array	The permissions assigned to the Zylo user. Check out available permissions at Permissions.	Yes	Yes	Yes
`zylo_created_at`	datetime	Date and time the record was created in Zylo.	Yes	No	No
`zylo_modified_at`	datetime	Date and time the record was last modified in Zylo.	Yes	No	No
`zylo_user_account_id`	UUID		No	Yes	Yes

Field Type Reference

string: Text value
number: Numeric value (integer or decimal)
boolean: True/false value
date: Date in YYYY-MM-DD format
datetime: Date and time in ISO 8601 format
UUID: Universally unique identifier
email: Email address format
JSON: Complex JSON object or array
array: Array of values