Retrieve detailed information for a specific contract by its unique identifier.
Returns comprehensive contract data including basic information, customer details, contract phases with products and pricing, custom attributes, and timestamps.
Documentation Index
Fetch the complete documentation index at: https://docs2.zenskar.com/llms.txt
Use this file to discover all available pages before exploring further.
Contract retrieved successfully
Unique identifier for this contract
Human-readable name for the contract. Used for identification and reporting purposes.
Current status of the contract (e.g., active, draft, expired, terminated). System automatically updates to 'expired' when end_date is reached.
draft, active, paused, expired, disputed Three-letter ISO 4217 currency code for all monetary amounts in this contract (e.g., 'USD', 'EUR', 'GBP').
Timestamp when this contract was created in the system. Used for audit trails and reporting.
Timestamp of the last modification to this contract. Updates whenever any field or related entity changes.
Unique identifier of the customer who is party to this contract.
Complete customer details including name, contact information, and billing preferences. The customer who is party to this contract.
Detailed description of the contract terms, scope, or special conditions.
List of tags for categorizing and filtering contracts. Useful for reporting and segmentation.
Date when the contract became or will become active. Billing and revenue recognition calculations start from this date.
Date when the contract expires. Null indicates an indefinite contract that continues until manually terminated.
Organization-specific metadata stored as key-value pairs. Can include fields like sales_rep, deal_id, region, or any custom data needed for reporting and integrations.
Metadata about the originating system or process that created this contract. Used for integration tracking and audit trails.
Reference date for billing cycle calculations. When set, billing cycles align to this date regardless of contract start date.
When true, billing cycles always end on the last day of the month, adjusting for varying month lengths.
Reference to the plan template used to create this contract, if applicable.
Defines contract renewal behavior. Currently only 'do_not_renew' is supported—contracts must be manually renewed or replaced.
renew_with_default_contract, renew_with_existing, do_not_renew List of contract phases defining distinct periods with different terms, products, or pricing. Sorted chronologically by start date.
Customer details for the invoice payer, if different from the contract customer. Used when one entity uses services but another pays for them.
The contract phase that is currently active based on today's date. Null if no phase is active or contract hasn't started.
URL to external contract document, signed agreement, or related resource.
When true and customer has a parent relationship, invoices are sent to the parent customer instead.
Customer ID who will receive and pay invoices for this contract, if different from the contract customer.