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

Outdoorsy Locations API

The locations API from Outdoorsy — 3 operation(s) for locations.

Outdoorsy Locations API is one of 62 APIs that Outdoorsy 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 and API documentation.

This API exposes 6 operations across 3 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, /v0.

6 operations 3 paths 12 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://api.outdoorsy.com/v0
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Outdoorsy Locations API declares 2 security schemes for authenticating requests. An API key is passed in the header as API-Key (API-Key). An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

Paths & Operations 6

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

locations 6
GET
/locations
List dealer locations
listLocations 11 params → 200400401
POST
/locations
Create dealer location
createLocation body → 200400401404
GET
/locations/{id}
Retrieve location by id
getLocationByOwner → 200400401404
DELETE
/locations/{id}
Delete dealer location
deleteLocation 1 param → 204401404
PATCH
/locations/{id}
Update dealer location details
updateLocation 1 param body → 200400401404
GET
/locations/{owner_id}/for-pro-page
List dealer locations for his pro page (locations with connected bank account, ordered by having the most rentals desc). Provide falback in the form of city and state with most bookable rentals
getLocationsByOwnerID 1 param → 200400

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Location (34 properties), SpecialHour (13 properties), TaxRate (11 properties), SpecialHourPickup (3 properties). Each schema is shown below with its type and property counts.

TaxRate
object
11 properties
LocAvailabilityInfo
object
3 properties
SpecialHour
object
─────────────────────────────────────────────────────────────────────────── Special Hours ─────────────────────────────────────────────────────────────────────…
13 properties
ProPageFallback
object
2 properties
LocAvailability
object
1 property
LocAvailabilityDay
object
2 properties
LocationLocale
object
1 property
SpecialHourDropoff
object
3 properties
Location
object
34 properties
SpecialHourPickup
object
3 properties
ProPageResponse
object
2 properties
DBStringSlice
array
DBStringSlice is a []string with database conversion methods

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

outdoorsy-locations-api-openapi.yml Raw ↑

Other APIs Outdoorsy publishes across the network.

Outdoorsy Admin API
Outdoorsy Amenities API
Outdoorsy Announcements API
Outdoorsy Auth API
Outdoorsy Banks API
Outdoorsy Booking Bundles API
Outdoorsy Booking Items API
Outdoorsy Booking Proposals API
Outdoorsy Bookings API
Outdoorsy Booking Services API
Outdoorsy Booking Transactions API
Outdoorsy Breadcrumbs API
Where this information came from

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