Fluxir Concepts
This page defines key terms and concepts that appear across Fluxir's API and trip flow. Understanding these concepts will help you navigate the system, build integrations, and interpret workflow behavior.
Core Concepts
| Concept | Description |
|---|---|
| Service Intent | A service that the user might be eligible for, based on trip parameters. |
| Trip | The journey context used to scope services, documents, and applications. |
| Document Schema | Describes the required documents and input fields per service. |
| Context | Structured metadata from the user, trip, or identity documents. |
| Merge Fields | Strategy for auto-populating form fields from context or extracted sources. |
| Service Application | A user-specific submission for a selected travel service. |
Related Concepts
Traveler
A person associated with the account for whom the trip and services are being requested.
Identity Document
A government-issued ID (e.g., passport) that may be uploaded and parsed to extract user data.
Field Type
The expected input format for a field (e.g., string, date, file).
How These Concepts Work Together
The Fluxir platform builds dynamic, data-driven workflows based on these concepts:
- Each service has a document schema that outlines what you need to provide.
- Data is collected via context, identity documents, and direct input.
- These values are merged into a service application before submission.