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
Outdoorsy

Outdoorsy Users API

The users API from Outdoorsy — 9 operation(s) for users.

Documentation Provider Profile APIs.io OpenAPI GitHub

Outdoorsy Users API is one of 62 APIs that Outdoorsy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 10 operations across 9 paths, and defines 61 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

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

10 operations 9 paths 61 schemas 9 GET1 PATCH

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 Users 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).

Paths & Operations 10

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

users 10
GET
/autosuggestions
Returns a breakdown of previous rentals, bookings or pending reviews.
getAutosuggestions 1 param → 200401404
GET
/confirm
Confirm new or changed user email
confirmEmail 2 params → 204400401
GET
/users
Return list of users
listUsers → 200401404default
GET
/users/logout
Log user out by invalidating authorization token
logoutUser → 204401
GET
/users/me
Returns currently logged in user.
usersMe → 200401404default
GET
/users/mini_me
Returns currently logged in user with minimal info.
getMiniMe → 200401404default
GET
/users/todays-activities
Returns today's activities for the owner
getTodaysActivities → 200401default
GET
/users/{id}
Return requested user model
getUserById 1 param → 200401404default
PATCH
/users/{id}
Update a user
updateUser 1 param body → 200400401404
GET
/users/{id}/owner-report-card
Returns statistics about the owner
ownerReportCard 3 params → 200401404default

Schemas 61

The contract defines 61 schemas that model the data the API accepts and returns. The most detailed are User (142 properties), Profile (39 properties), RentalItem (37 properties), Location (34 properties). Each schema is shown below with its type and property counts.

Verifications
object
4 properties
Locale
object
9 properties
Action
string
TaxRate
object
11 properties
GpsDevicesData
object
9 properties
RolePermission
object
11 properties
LocAvailabilityInfo
object
3 properties
PaymentProcessorName
string
ineligibleRental
object
3 properties
OwnerActivity
object
7 properties
ProStatus
object
13 properties
NotificationBrowser
object
1 property
SocialSlice
array
SpecialHour
object
─────────────────────────────────────────────────────────────────────────── Special Hours ─────────────────────────────────────────────────────────────────────…
13 properties
License
object
License holds driver's license information for a user
IMap
object
AutoSuggestionsResponse
object
5 properties
analyticsReport
object
5 properties
MSI
object
NotificationMobile
object
1 property
NotificationEmail
object
2 properties
UserSecurity
object
3 properties
BookingRestrictions
object
7 properties
LocAvailability
object
1 property
User
object
A user is the security principal for this application. A user can be an owner, renter, agent or admin.
142 properties
DBMSISlice
array
DBMSISlice is a []string with database conversion methods
LocAvailabilityDay
object
2 properties
BookingOptions
object
29 properties
PaymentProcessingInfo
object
32 properties
Role
object
8 properties
DBIntSlice
array
DBIntSlice is a []int with database conversion methods
LocationLocale
object
1 property
SpecialHourDropoff
object
3 properties
Address
object
Address holds address information for a user
7 properties
SSO
object
4 properties
PaymentProcessor
object
Typically this object is composed into a struct, but embedded into the same table using the db:",embed" struct tag.
4 properties
DBBoolMap
object
DBBoolMap is a map[string]boold with database conversion methods
Business
object
24 properties
Location
object
34 properties
Bio
object
bio holds additional information about a user
4 properties
NotificationSettings
object
4 properties
SpecialHourPickup
object
3 properties
EarnedCredit
object
19 properties
PaymentAddress
object
6 properties
TOS_Acceptance
object
5 properties
NullTime
object
NullTime represents a time.Time that may be null. NullTime implements the sql.Scanner interface so it can be used as a scan destination, similar to sql.NullStr…
2 properties
NullFloat64
object
NullFloat64 implements the [Scanner] interface so it can be used as a scan destination, similar to [NullString].
2 properties
ownerReport
object
18 properties
rentalReport
object
22 properties
NotificationSMS
object
4 properties
DBStringSlice
array
DBStringSlice is a []string with database conversion methods
DBInterfaceMap
object
DBInterfaceMap is a map[string]interface{} with database conversion methods
Profile
object
profile holds all profile information for a user
39 properties
Social
object
4 properties
RentalItem
object
37 properties
Tracking
object
6 properties
Driver
object
23 properties
Resource
object
Note that any of the optional keys will be omitted if a value is not provided. For more information, see the specification at: http://jsonapi.org/format/docume…
6 properties
Relationships
object
http://jsonapi.org/format/document-resource-object-relationships
Links
object
http://jsonapi.org/format/document-links
Relationship
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

outdoorsy-users-api-openapi.yml Raw ↑

Other APIs Outdoorsy publishes across the network.

Outdoorsy Admin API
AE Profile APIs.io
Outdoorsy Amenities API
AE Profile APIs.io
Outdoorsy Announcements API
AE Profile APIs.io
Outdoorsy Auth API
AE Profile APIs.io
Outdoorsy Banks API
AE Profile APIs.io
Outdoorsy Booking Bundles API
AE Profile APIs.io
Outdoorsy Booking Items API
AE Profile APIs.io
Outdoorsy Booking Proposals API
AE Profile APIs.io
Outdoorsy Bookings API
AE Profile APIs.io
Outdoorsy Booking Services API
AE Profile APIs.io
Outdoorsy Booking Transactions API
AE Profile APIs.io
Outdoorsy Breadcrumbs API
AE Profile APIs.io
#User
← Back to O APIs
API Details
ID
outdoorsy:outdoorsy-users-api
Base URL
https://api.outdoorsy.com/v0
Docs
https://developers.outdoorsy.com/api
Provider
Outdoorsy
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=outdoorsy-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/outdoorsy-users-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 Outdoorsy Users 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.