Teams and the team slug
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /concepts/teams.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
A team is one shop in YoPrint: its customers, orders, jobs, settings and members. Every request works on exactly one team, named by its team slug in the path:
https://secure.yoprint.com/v1/api/store/your-team/customer ^^^^^^^^^Find your team slug
Section titled “Find your team slug”In YoPrint, open Profile. The API Access card shows it as Team ID.
The slug is a short text name, such as your-team. Use the slug itself: YoPrint doesn’t accept a team’s number or hash id in its place.
One key, several teams
Section titled “One key, several teams”Your API key belongs to you, not to a team. If you’re a member of several teams, the same key works on each one whose plan includes API access (Pro or higher). On others, requests answer 403 with api_access_not_in_plan. Change the slug to change the team.
- Your API keyWho you are
- Team slug in the pathWhich team, such as
your-team - The requestRuns as you, with your role on that team
On each team, the key has the role you have on that team. You might be able to change settings on one team and only view orders on another.
Data stays in its team
Section titled “Data stays in its team”- Every id belongs to one team. An id from team A doesn’t find anything on team B, even with the same key.
- A list or filter returns only that team’s records.
- A webhook, export or import belongs to the team whose slug you used.
When the slug is wrong
Section titled “When the slug is wrong”| Situation | Status |
|---|---|
| The key is missing or wrong (whatever the slug) | 401 |
| No team has that slug | 404 |
| The team exists, but you’re not a member | 404 |
Both slug cases look the same. If you get 404 on every call, check the slug against Team ID in Profile before anything else.