Get Splitter Version
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
The ID of the splitter.
Example: "spl_Xj8mK2pL9nR4vT7qY5wZ"
The version to retrieve. Accepts any of the following:
"draft"— returns the current draft version"latest"— returns the latest published version (falls back to draft if none published)- A version number (e.g.
"0.1","1.0") — returns that specific published version - A version ID (e.g.
"splv_QYk6jgHA_8CsO8rVWhyNC") — returns that specific version by ID
Headers
API version to use for the request. If you’re using an SDK, you can ignore this parameter. If you are not using an SDK and do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.
The workspace ID to target. Required when using an organization-scoped API key; optional for workspace-scoped keys (the key is already tied to a workspace). See Authentication for details on API key scopes.
Response
The type of object. Will always be "splitter_version".
The unique identifier for this version of the splitter.
Example: "splv_xK9mLPqRtN3vS8wF5hB2cQ"
A description of this version of the splitter.
Example: "Updated split rules for multi-invoice packets"
The version number or identifier for this specific version of the splitter. The draft version will have version=“draft”.
Examples: "1.0", "2.1", "draft"
The ID of the splitter that this version belongs to.
Example: "spl_Xj8mK2pL9nR4vT7qY5wZ"
The time (in UTC) at which the object was created. Will follow the RFC 3339 format.
Example: "2024-03-21T16:45:00Z"
The actor that created this resource.
user— the resource was created via the studio by a logged-in user. The user’semailis exposed.api_key— the resource was created via the API using an API key. The key’snameis exposed.
May be null for resources created before attribution.

