> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/api-v1-reference/settings-advanced-employee-capacity/get-advanced-employee-capacity-settings-for-the-department-shop-level.md).

# Get Advanced Employee capacity settings for the department/shop-level

Advanced Employee Eapacity (Forecasting settings → Business rules) defines how many visitors or customers one employee is expected to serve per working hour, as a tier ladder (the capacity changes with how busy the hour is), per weekday and hour, valid within a dated period. It refines the regular Employee capacity tiers: hours covered by an advanced ladder use it, every other hour uses the regular tiers. When SameSystem calculates recommended hours, the forecasted traffic of an hour is divided by the capacity value of the tier that traffic falls into, which gives the number of employees needed in that hour.

This endpoint will return all department/shop-level settings.

```json
{"openapi":"3.0.0","info":{"title":"SameSystem API V1","version":"1.1.3"},"servers":[{"url":"https://api.samesystem.com/api/v1/","description":""}],"paths":{"/{clientToken}/settings/shop/advanced_employee_capacity":{"get":{"tags":["Settings - Advanced Employee Capacity"],"summary":"Get Advanced Employee capacity settings for the department/shop-level","description":"Advanced Employee Eapacity (Forecasting settings → Business rules) defines how many visitors or customers one employee is expected to serve per working hour, as a tier ladder (the capacity changes with how busy the hour is), per weekday and hour, valid within a dated period. It refines the regular Employee capacity tiers: hours covered by an advanced ladder use it, every other hour uses the regular tiers. When SameSystem calculates recommended hours, the forecasted traffic of an hour is divided by the capacity value of the tier that traffic falls into, which gives the number of employees needed in that hour.\n\nThis endpoint will return all department/shop-level settings.","operationId":"get-clientToken-settings-shop-advanced_employee_capacity","parameters":[{"name":"clientToken","in":"path","description":"Token in a form of \"c\\<clientId\\>\".","required":true,"schema":{"type":"string"}},{"name":"shop_id","in":"query","description":"Department/shop id. Must belong to the client, otherwise 404. Add use_custom_id=1 to pass the department’s custom (external) id instead of the SameSystem id.","required":true,"schema":{"type":"string"}},{"name":"use_custom_id","in":"query","description":"1= Pass the department’s custom (external) id instead of the SameSystem id.","required":false,"schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/SettingsAdvancedEmployeeCapacity"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"status":{"type":"string","default":"unauthorized"},"description":{"type":"string"}}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"status":{"type":"string","default":"not_found"},"description":{"type":"string"}}}}}}}}}},"components":{"schemas":{"SettingsAdvancedEmployeeCapacity":{"required":["periods"],"type":"object","properties":{"periods":{"type":"array","items":{"required":["target"],"type":"object","properties":{"target":{"type":"string","description":"Can be \"visitors\" or \"customers\". Each target has an independent timeline.","enum":["visitors","customers"],"default":"visitors"},"start_date":{"type":"string","description":"Start date of period.","format":"date"},"end_date":{"type":"string","description":"End date of period. Can be null, omittet or \"\" if open-ended.","format":"date","nullable":true},"values":{"type":"array","description":"Flat list of tier rows. Rows sharing the same (wday,hour) form that hour's tier ladded, so a pair may repeat.","items":{"required":["starting_quantity"],"type":"object","properties":{"wday":{"maximum":7,"minimum":1,"type":"integer","description":"ISO weekday. 1= Monday...7=Sunday"},"hour":{"maximum":23,"minimum":0,"type":"integer","description":"0..23"},"starting_quantity":{"type":"integer","description":"Lower bound of the traffic band. null and \"\" wil count as 0."},"ending_quantity":{"type":"integer","description":"Uppper bound of the band. Must be >= starting_quantity. null, omittet or \"\" = no upper limit. Always returned as null for the top tier.","nullable":true},"value":{"type":"number","description":"Vistors/customers that one employee can serve per hour while the traffic is inside the band. Returned as decimal."}}}}}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.samesystem.dev/api-v1-reference/settings-advanced-employee-capacity/get-advanced-employee-capacity-settings-for-the-department-shop-level.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.