---
id: config-v1
slug: /apis/config-v1
title: 'Configuration (config.v1)'
description: 'Read an instance''s effective configuration - attachment size limit, time zone, effort tracking - without authentication.'
sidebar_label: 'Configuration (config.v1)'
sidebar_position: 15
tags: ['api', 'configuration', 'instance']
---

Reports the instance's effective configuration — the settings an integration
would otherwise have to hardcode or guess. Like [`meta.v1`](/apis/meta-v1), it
requires **no authentication**; unlike most of the API, it speaks only XML and
accepts only `GET`.

```text
GET ~/config.v1
```

```xml
<Configuration version="26.2.4.30" source="cbafd139d9">
	<Setting key="EffortTracking" value="True" />
	<Setting key="StoryTrackingLevel" value="Off" />
	<Setting key="DefectTrackingLevel" value="On" />
	<Setting key="MaximumAttachmentSize" value="4194304" />
	<Setting key="CapacityPlanning" value="Off" />
	<Setting key="Scorecard" value="True" />
	<Setting key="ScorecardSelectiveBreakdown" value="True" />
	<Setting key="Scorecard.Charts.Query.Timeout" value="120000" />
	<Setting key="TimeZoneId" value="Eastern Standard Time" />
	<Setting key="TimeZoneDisplayName" value="(UTC-05:00) Eastern Time (US &amp; Canada)" />
	<Setting key="TimeZoneName" value="Eastern Daylight Time" />
</Configuration>
```

The root element's `version` and `source` attributes identify the build the
instance is running — the quickest way to answer "what version is this
instance?" programmatically. (A local development build reports `0.0.0.0` and
`unknown`, because dev assemblies are not version-stamped.)

## The Settings

| Key | Meaning |
| --- | --- |
| `EffortTracking` | Whether effort (Actuals) tracking is enabled on the instance |
| `StoryTrackingLevel` / `DefectTrackingLevel` | Where effort detail is tracked for the type: at the workitem itself (`On`), at its child tasks and tests (`Off`), or both (`Mix`) |
| `MaximumAttachmentSize` | The upload limit in **bytes** — the size behind an [attachment upload's `413`](/apis/attachments#size-limits-are-a-server-setting) |
| `CapacityPlanning` | The instance's capacity-planning level |
| `Scorecard`, `ScorecardSelectiveBreakdown` | Whether the scorecard features are visible |
| `Scorecard.Charts.Query.Timeout` | Scorecard chart query timeout, in milliseconds |
| `TimeZoneId` | The instance time zone (Windows time-zone ID) |
| `TimeZoneDisplayName` | Its display form, with UTC offset |
| `TimeZoneName` | The name currently in effect — daylight or standard, depending on the date |

Two of these answer questions this documentation repeatedly tells you not to
hardcode:

- **`MaximumAttachmentSize`** — discover the real upload limit instead of
  handling `413` blind.
- **The time-zone keys** — local timestamps such as `ChangeDate` are in the
  instance's time zone; this is where you learn which one that is. (For
  filtering and incremental loads, still
  [prefer the `…UTC` twins](/concepts/attributes).)

## Related Topics

- [Attachments](/apis/attachments) — where the size limit bites
- [Attributes](/concepts/attributes) — local vs UTC date attributes
- [Meta API](/apis/meta-v1) — the other anonymous discovery endpoint