Skip to content

Publish a grouped time-series service

A grouped service presents related time series behind one catalogue entry and one query contract. Consumers choose a member series as an input, then receive the same output shape for any member.

When to group series

Use a grouped service when the series differ by subject or indicator but share the same query fields. Examples include economic indicators by country or market data by instrument. Keep a series standalone when its inputs or outputs are materially different.

Create the service

  1. Open Provision → Data services → Add data service.
  2. Enter the service identity, owner, access policy, classifications, availability, and freshness target.
  3. Select a time-series service contract. It must accept the required string input series and declare the output fields every member will provide.
  4. Save the service. A saved service exposes Add member time series.
  5. Create or attach each member series. Use the same response keys and compatible types and units across all members.
  6. Publish each member and wait for delivery.
  7. Return to the data service, clear its readiness blockers, preview it, and publish it.

Publishing the group before its members, mixing incompatible output fields, or omitting the series input blocks publication.

Check member discovery

Open the published service from Catalog → Data services. Its member directory supports search and catalogue filters. The query form uses an autocomplete control for the series input so consumers select a labelled member instead of copying an identifier.

The API detail includes:

  • seriesCount and seriesUrl in the service profile;
  • a runnable example with a member selected; and
  • a contract shared by every member.

Query it

Find the group with GET /v1/catalog/services?type=timeseries, inspect detailUrl, and send an example to queryUrl. Change only the series input to query another member. The member value is the canonical series URL returned by the member directory.

The result identifies both the grouped service and selected member. If members use different delivery modes, the group reports mixed; each query still follows the selected member's published source binding.