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 Geoservices API

The Geoservices API from Skedulo — 1 operation(s) for geoservices.

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

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

This API exposes 1 operation across 1 path, and defines 7 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.

1 operations 1 paths 7 schemas 1 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 Geoservices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Authorization).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Geoservices 1
POST
/geoservices/travel-time
Determine travel time for many resources, across work or activities they have been assigned
/geoservices/travel-time body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SchedulingOptions (10 properties), TravelTimeNode (6 properties), TravelTimeBody (3 properties), TravelTimeResource (3 properties). Each schema is shown below with its type and property counts.

TravelTimeNode
object
6 properties 4 required
Coordinates
object
Geocoordinates of the activity/job/resource
2 properties 2 required
SchedulingOptions
object
10 properties
TravelTimeResponse
object
1 property
TravelTimeResource
object
3 properties
TimeStamp
string
Can be either ISO8601 date time string or Unix timestamp number ( in milliseconds ). Always returned in ISO8601 format.
TravelTimeBody
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

skedulo-geoservices-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 Geoservices 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.