Manage service versions and effective dates
In Spark, each service version has effective start and effective end dates. Spark can serve the different service versions of one service based upon a transaction date input.
Define effective from and effective until dates for a service version
In any action that leads to a new service version, you can set the Effective from and Effective until dates for the service version.
By default, Effective from is set to the upload date and time. Effective until date is set
100 yearsinto the future.Dates and times are defined in your local time. Check the detected time zone in the User menu.
You can also change the dates for an existing service version inEdit a service property.
Resolve service versions

Execute API (v3) uses the request_meta transaction_date.
If a specific
versionorversion_idis being called, the API will ignore thetransaction_date.If the
transaction_dateis specified and no version is specified, it will use the latest version that applies at the time of thetransaction_date.The Execute API always resolves the
version_idparameter first,service_idparameter second, and theservice_urilast. It is possible that within an API request, these three parameters may refer to different services, however Spark will resolve the reference in the same order.This functionality cannot be tested within the API Tester as it is service version specific. You must use an external application to make the API request.
version_id
has no impact on version resolution
Version specified by the API call.
service_id or service_uri
none provided
Latest version that applies where the transaction_date equals the current time.
service_id or service_uri
included in the API request
Latest version that applies at the transaction_date.
If the transaction_date is outside of the effective from or effective until dates for any service versions, then no calculation will be returned.
Last updated
