StayingAPI · Authentication Profile
Stayingapi Authentication
Authentication
StayingAPI runs two distinct auth surfaces. The REST API at api.stayingapi.com/v1 uses a Bearer API key with an environment-encoding prefix (stay_test_ = deterministic sandbox, stay_live_ = live). The hosted MCP server at mcp.stayingapi.com/mcp uses OAuth 2.1 with PKCE (S256) and dynamic client registration, advertised through RFC 8414 authorization server metadata and RFC 9728 protected-resource metadata. Both draw on the same account and the same single credit balance.
StayingAPI secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
TravelHospitalityaccommodation-datahotel-apiVacation RentalShort-Term RentalAirbnbBooking.comVrbogoogle-hotelscross-ota-price-comparisonAvailabilityReviewsRESTMCPagent-nativeOpenAPI
Methods: http, oauth2
Schemes: 2
OAuth flows: authorizationCode
API key in: header
Security Schemes
bearerAuth http
mcpOAuth oauth2
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.