How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Locus

Locus TeamMaster API

The TeamMaster API from Locus — 2 operation(s) for teammaster.

Documentation Provider Profile APIs.io OpenAPI GitHub

Locus TeamMaster API is one of 16 APIs that Locus publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include TeamMaster. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://oms.locus-api.com/v1.

3 operations 2 paths 10 schemas 1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://oms.locus-api.com/v1
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Locus TeamMaster API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (locusauth). An API key is passed in the header as Authorization (apiKeyAuth).

  • locusauth — HTTP Basic Authentication

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

TeamMaster 3
GET
/client/{clientId}/team-master/{teamId}
Get a team
getTeam 3 params → 200
PUT
/client/{clientId}/team-master/{teamId}
Create a team
createTeam 3 params body → 200
POST
/client/{clientId}/team-master/{teamId}/status
Update status for a specific team
updateTeamStatus 2 params body → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are BusinessUnit (9 properties), BusinessUnitId (2 properties), EntityStatusUpdateRequest (1 property), CityId (1 property). Each schema is shown below with its type and property counts.

EntityStatusUpdateRequest
object
Wrapper for entity status update request
1 property 1 required
BusinessUnitId
object
2 properties 2 required
IndustryType
object
EntityDefinition
object
BusinessUnitStatusEnum
string
Operational status of the business unit
EntityStatus
object
Team
Team entity
BusinessUnit
object
Business unit of the client
9 properties 6 required
CityId
object
An id for a city
1 property 1 required
CreateTeamRequest
Team entity create request

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

locus-sh-teammaster-api-openapi.yml Raw ↑

Other APIs Locus publishes across the network.

Locus HomebaseMaster API
AE Profile APIs.io
Locus LocationMaster API
AE Profile APIs.io
Locus Order API
AE Profile APIs.io
Locus OrderServiceability API
AE Profile APIs.io
Locus PersonnelMaster API
AE Profile APIs.io
Locus Rider API
AE Profile APIs.io
Locus RiderPersona API
AE Profile APIs.io
Locus Roster API
AE Profile APIs.io
Locus ServiceType API
AE Profile APIs.io
Locus ServiceTypeConfiguration API
AE Profile APIs.io
Locus ShiftTag API
AE Profile APIs.io
Locus SKUMaster API
AE Profile APIs.io
#TeamMaster
← Back to L APIs
API Details
ID
locus-sh:locus-sh-teammaster-api
Base URL
https://oms.locus-api.com/v1
Docs
https://docs.locus.sh/?model=https://docs.locus.sh/apis/locus-oms/v1/order-management.json&host=https://oms.locus-api.com/v1
Provider
Locus
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=locus-sh-teammaster-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/locus-sh-teammaster-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Locus TeamMaster API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.