Tugboat Yards · Authentication Profile

Tugboat Yards Authentication

Authentication

Tugboat Yards secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyMediaPublishingCrowdfundingAudience FundingPaymentsDefunct
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

X-Tugboat-Auth apiKey
· in: header (X-Tugboat-Auth)

Source

Authentication Profile

tugboat-yards-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://web.archive.org/web/20150524035220id_/https://tugboatyards.com/developer/api/sources/authentication.txt
docs: https://web.archive.org/web/20150207051224/https://tugboatyards.com/developer/api/authentication.html
x-status: historical
note: Tugboat Yards is defunct and its API is offline. This profile is recovered
  verbatim from the provider's own developer documentation as archived by the
  Wayback Machine in 2015. Nothing here is live.
summary:
  types: [apiKey]
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: X-Tugboat-Auth
  type: apiKey
  in: header
  parameter: X-Tugboat-Auth
  description: Publisher API key sent on every request as the X-Tugboat-Auth
    header (format "app_id%token", e.g. "XXXXX%YYYYYYYYYYYYY" in the docs'
    placeholders). Keys were generated by publishers at
    https://tugboatyards.com/settings/page/api after emailing
    api@tugboatyards.com for API access. GET /key-check validated a token.
  sources:
  - https://web.archive.org/web/20150524035220id_/https://tugboatyards.com/developer/api/sources/authentication.txt
verification:
  endpoint: GET /key-check
  success_response: '{"success": true}'
  error_response: '{"error": "invalid app_id"}'