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
Mosey

Mosey Locations API

The Locations API from Mosey — 7 operation(s) for locations.

Documentation Provider Profile APIs.io OpenAPI GitHub

Mosey Locations API is one of 12 APIs that Mosey publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

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

Requests are made against a single base URL, https://api.mosey.com.

7 operations 7 paths 37 schemas 5 GET1 PATCH1 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://api.mosey.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Mosey Locations API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2PasswordBearer) using the password flow.

Paths & Operations 7

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

Locations 7
GET
/locations
List Locations
list_locations_handler_locations_get → 200
PUT
/locations/{location_public_id}
Add Location
add_location_handler_locations__location_public_id__put 1 param body → 200422
PATCH
/locations/{region_platform_public_id}
Update Location Configuration
update_location_handler_locations__region_platform_public_id__patch 1 param body → 200422
GET
/locations/{region_platform_public_id}/tasks
List Tasks for Location
list_location_tasks_handler_locations__region_platform_public_id__tasks_get 6 params → 200422
GET
/locations/{location_public_id}/logins
List Account Logins for Location
list_account_logins_for_location_locations__location_public_id__logins_get 1 param → 200422
GET
/locations/{region_platform_public_id}/mail
List Mail by Location
get_legal_entity_mail_handler_for_location_locations__region_platform_public_id__mail_get 3 params → 200422
GET
/locations/{region_platform_public_id}/agency_accounts
List Agency Accounts for Location
get_agency_accounts_for_legal_entity_and_location_locations__region_platform_public_id__agency_accounts_get 1 param → 200422

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are AccountTask (16 properties), AccountTaskDefinition (7 properties), PlatformMail (6 properties), app__api__platform__models__PlatformAgencyAccount (6 properties). Each schema is shown below with its type and property counts.

AccountTaskResolutionAutomate
object
4 properties 3 required
ActionField
object
4 properties 4 required
AccountTaskDefinition
object
7 properties 6 required
AccountLegalEntityLocation
object
1 property 1 required
AccountTaskResolutionManualStep
object
5 properties 5 required
AccountTaskAutomationFormSpec
object
LocationRef
object
3 properties 3 required
AccountLegalEntityLocationRef
object
2 properties 2 required
LocationConfig
object
2 properties
FeeRange
object
3 properties 2 required
AccountTaskStatus
string
AccountTaskEstimation
object
3 properties 3 required
HTTPValidationError
object
1 property
AccountManagedProvider
object
2 properties 2 required
AccountTaskResolutionRedirect
object
2 properties 1 required
ETAUnit
string
PlatformMail
object
6 properties 4 required
PlatformAgencyAttributeAndValue
object
3 properties 3 required
AccountTaskResolutionAction
object
6 properties 5 required
ValidationError
object
3 properties 3 required
MailType
string
CreateLocationRequest
object
1 property
FeeVariable
object
2 properties 1 required
PlatformLegalEntityAccountLogin
object
5 properties 5 required
AccountTaskCriteria
object
3 properties 2 required
TaskContextLegalEntity
object
2 properties 1 required
AccountTaskResolutionManual
object
2 properties 1 required
TaskContextEmployee
object
2 properties 1 required
TaskDefinitionType
string
AccountTaskResolutionManualStepPath
object
3 properties 2 required
AccountTask
object
16 properties 8 required
FeeFixed
object
2 properties 1 required
UpdateLocationRequest
object
1 property
app__api__platform__models__PlatformAgencyAccount
object
6 properties 6 required
TaskPriority
string
AccountTaskETA
object
3 properties 1 required
PlatformAgency
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mosey-locations-api-openapi.yml Raw ↑

Other APIs Mosey publishes across the network.

Mosey Accounts API
AE Profile APIs.io
Mosey Agency Accounts API
AE Profile APIs.io
Mosey Auth API
AE Profile APIs.io
Mosey Documents API
AE Profile APIs.io
Mosey Handbook API
AE Profile APIs.io
Mosey Legal Entity API
AE Profile APIs.io
Mosey Logins API
AE Profile APIs.io
Mosey Mail API
AE Profile APIs.io
Mosey Regions API
AE Profile APIs.io
Mosey Signup API
AE Profile APIs.io
Mosey Tasks API
AE Profile APIs.io
#Locations
← Back to M APIs
API Details
ID
mosey:mosey-locations-api
Base URL
https://api.mosey.com
Docs
https://docs.mosey.com/api-reference/introduction
Provider
Mosey
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=mosey-locations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mosey-locations-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 Mosey Locations 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.