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

Skedulo Location API

The Location API from Skedulo — 4 operation(s) for location.

Skedulo Location API is one of 67 APIs that Skedulo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Location. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 4 base URLs: https://api.skedulo.com/auth, https://api.uk.skedulo.com/auth, https://api.ca.skedulo.com/auth, https://api.au.skedulo.com/auth.

4 operations 4 paths 8 schemas 3 GET1 POST

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.skedulo.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Skedulo Location API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Authorization).

Paths & Operations 4

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

Location 4
GET
/location/latest
Latest locations
locationLatest 1 param → 200400default
GET
/location/history
Location history
locationHistory 6 params → 200default
POST
/location/update
Location Update
locationUpdate body → 200default
GET
/location/resources_within_distance
Locate resources with a set distance
locationResourcesWithinDistance 6 params → 200default

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Location (8 properties), DistanceFromLocation (5 properties), Paging (3 properties), PagedResultLocationHistory (2 properties). Each schema is shown below with its type and property counts.

Location
object
8 properties 3 required
Paging
object
3 properties 3 required
LatestLocationResult
object
LocationHistory
array
ResourceDistanceFromLocationResult
object
Map resource ids to their distance from a location
DistanceFromLocation
object
Position and Distance from a location
5 properties 4 required
PagedResultLocationHistory
object
2 properties 2 required
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

skedulo-location-api-openapi.yml Raw ↑

Other APIs Skedulo publishes across the network.

Skedulo Admin API
Skedulo api-controller API
Skedulo Api User API
Skedulo Async Job Management API
Skedulo Attachment API
Skedulo Attachments API
Skedulo Autocomplete API
Skedulo Availability API
Skedulo Avatar API
Skedulo Batch API
Skedulo Config API
Skedulo Device Notification Information and Registration API
Where this information came from

This is an independent, third-party profile of Skedulo Location 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.