--- title: "Obtaining the scope and codes of imported calendars" slug: "obtaining-the-scope-and-codes-of-imported-calendars" updated: 2024-10-23T11:18:59Z published: 2024-10-23T11:18:59Z canonical: "support.lusid.com/obtaining-the-scope-and-codes-of-imported-calendars" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.lusid.com/llms.txt > Use this file to discover all available pages before exploring further. # Obtaining the scope and codes of imported calendars Each Copp Clark calendar has a *code* in LUSID that, together with the scope, uniquely identifies it. You can use the code of an imported calendar in [various business operations](/v1/docs/using-calendars-in-lusid) and expect LUSID to automatically factor market holidays into outcomes. Note all Copp Clark calendars share the same scope: `CoppClarkHolidayCalendars`. You can view the codes of the Copp Clark calendars available in your LUSID domain by calling the `ListCalendarsInScope` API with the `CoppClarkHolidayCalendars` scope: ```json curl -X GET "https://.lusid.com/api/api/calendars/generic/CoppClarkHolidayCalendars" -H "Authorization: Bearer " ``` This API call returns all the calendar codes you can use in various LUSID operations. As you can see, by default there are two different calendar codes loaded for each currency, for example: - The `AUD__C` calendar is a *qualified* calendar, where `__C` refers to the Copp Clark Currency FX Market calendar type. We recommend using qualified calendars wherever possible in LUSID business operations. - The `AUD` calendar is an *unqualified* calendar, which means it may originate from one of the other Copp Clark calendar types, for example Payment Systems. [Find out more about this](/v1/docs/configuring-horizon-copp-clark-to-import-calendars-using-the-integrations-dashboard#appendix-a-qualified-and-unqualified-calendar-codes). ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/e891e2e1-32e4-4bdb-bd4e-865f36bbef2c.png)