Actions290
- Action Actions
- Agent Actions
- Appointment Actions
- Approval Process Actions
- Approval Process Rule Actions
- Asset Actions
- Attachment Actions
- Automation Actions
- Canned Text Actions
- Category Actions
- Client Actions
- Contract Actions
- Contract Rule Actions
- Contract Schedule Actions
- Contract Schedule Plan Actions
- Custom API Call Actions
- Feed Actions
- Field Info Actions
- Holiday Actions
- Invoice Actions
- Invoice Payment Actions
- Item Actions
- Knowledge Base Actions
- Lookup Actions
- Notification Actions
- Opportunity Actions
- Outcome Actions
- Product Branch Actions
- Product Component Actions
- Project Actions
- Purchase Order Actions
- Quotation Actions
- Raynet Actions
- Raynet Detail Actions
- Recurring Invoice Actions
- Release Actions
- Release Note Group Actions
- Reporting Actions
- Sales Order Actions
- Secure Secret Link Actions
- Security Check Actions
- Site Actions
- Supplier Actions
- Survey Actions
- Tag Actions
- Team Actions
- Ticket Actions
- Ticket Approval Actions
- Ticket Status Actions
- Ticket To-Do Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Top Level Actions
- Transcription Actions
- User Actions
- Webhook Actions
- Webhook Event Actions
Client → Get by ID
AI-generatedSummary
Retrieve detailed information about a client by its ID, optionally including additional data such as domain filters, ticket types, activity, details, periods, and prepay information.
Inputs
- Client ID (required) — The ID of the client to retrieve.
- Additional Fields — Optional parameters to customize the response, including domain filtering, whether to include available ticket types, customer ticket activity, extra detailed objects, pre-pay periods, pre-pay information, and filtering by ticket type ID.
Output shape
A single client record with included details according to specified additional fields.
The response shape depends on the specified additional fields; for example, including ticket types or activity data will alter the returned data structure accordingly.
Examples
Example 1: Fetch client data by ID with default fields only.
Set 'Client ID' with the target client ID; leave additional fields empty.
Example 2: Fetch client data including available ticket types and detailed information.
Set 'Client ID' and in 'Additional Fields' enable 'Get Available RTs' and 'Include Details'.