Help center › Data Feed Reference › Reference data

Calendars and holidays · calendar 1.1

Calendars and holidays. Holidays per calendar. The scheduler skips them; feed business dates and T-1 tokens follow them. Calendar US is built in for 2026 and 2027; FIRM is your own. Key: calendar + holiday.

Namespace: urn:vestoris:feed:calendar:1.1
Schema: calendar-1.1.xsd
Also accepted: urn:vestoris:feed:calendar:1.0 (calendar-1.0.xsd)
Key (upsert): calendar + holiday: a record with an existing key updates it; a new key inserts.
Start-of-day step: Calendars
File name: F00012_CALENDAR_20261023_001.xml
Modes: delta (action="delete" removes a record); full behaves as delta for this format

The <feed> root #

Attribute	Use	Type	Meaning
`businessDate`	required	`xs:date`	The business date the data is for (YYYY-MM-DD).
`firm`	required	`xs:string`	Your firm code, shown on Data › Feeds (e.g. F00012).
`source`	optional	`xs:string`	Who produced the file (vendor or system name).
`generated`	required	`xs:dateTime`	When the file was produced (UTC).
`recordCount`	required	`xs:nonNegativeInteger`	The number of record elements. A file whose count does not match is refused (F004): it was probably cut short.
`mode`	optional (default delta)	`xs:string`	delta: only the records in the file change, and action="delete" removes one. full: the file is complete (this data set has no inactivation: full behaves as delta).

The <record> elements #

upsert (insert or update by key) or delete (removes the record; a security or account is inactivated, never deleted). Elements may appear in any order; an element that is left out keeps its current value.

Element	Required	Type	Meaning	Codes
`calendar` key #	yes	`xs:string` pattern [A-Z0-9][A-Z0-9_.\-]{0,19}	Calendar code, e.g. US or FIRM. Part of the key. A code: letters, digits, "_", "." or "-", up to 20. Part of the key. Example: `FIRM`	`R101` `R111`
`holiday` key #	yes	`xs:date`	The date the calendar is closed. Part of the key. An ISO date, YYYY-MM-DD. Part of the key. Example: `2026-12-24`	`R101` `R102`
`name` #	no	`xs:string` ≤ 120 chars	What the holiday is. Text, up to 120 characters. Example: `Office closed`	`R114`

Validation #

No DOCTYPE or entity declaration (F002); well-formed UTF-8 (F001).
The namespace and version are published (F007), and the file matches the XSD (F003).
Header: firm is your firm code (F006), businessDate a business day (F005), recordCount the number of records (F004).
Each record: the field checks in the table above, references to records that exist (R109), no key twice in a file (R110). A rejected record does not stop the rest of the file.

Codes this format can return: F001 F002 F003 F004 F005 F006 F007 F008 R101 R102 R109 R110 R111 R114

Sample #

An annotated file: the comment lines explain the header; drop them or keep them, comments are allowed.

<?xml version="1.0" encoding="UTF-8"?>
<!-- businessDate: the date the data is for. firm: your firm code. recordCount: how many <record> elements follow. -->
<feed xmlns="urn:vestoris:feed:calendar:1.1" businessDate="2026-10-23" firm="F00012" source="ExampleVendor" generated="2026-10-23T22:05:00Z" recordCount="1" mode="delta">
  <record action="upsert">
    <calendar>FIRM</calendar>
    <holiday>2026-12-24</holiday>
    <name>Office closed</name>
  </record>
</feed>

Download the sample Download the XSD Validate a file

Version history #

1.0 (2026-10-26): First published version.
1.1 (2026-10-26): Adds the optional <udfs> element (up to ten <udf slot="1..10" name="...">value</udf>) to the reference formats that carry user-defined fields: security, issuer, account, accountgroup, broker, model, benchmark and list. Additive: every valid 1.0 file is still accepted under its 1.0 namespace.