Tindie · Authentication Profile

Tindie Authentication

Authentication

Tindie secures its APIs with apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyMarketplaceHardwareElectronicsMakereCommerceOpen Source HardwareOrders
Methods: apiKey Schemes: 3 OAuth flows: API key in: query, header

Security Schemes

apiKeyQuery apiKey
· in: query (api_key)
usernameQuery apiKey
· in: query (username)
authorizationHeader apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/tindie-openapi.yml
docs: https://www.tindie.com/help/
summary:
  types: [apiKey]
  api_key_in: [query, header]
  oauth2_flows: []
  note: >-
    Tindie uses Django Tastypie ApiKeyAuthentication. Authenticated calls to the
    order and orderitem resources require an API key issued from the seller's
    account settings, passed as `api_key` + `username` query parameters or the
    header `Authorization: ApiKey <username>:<api_key>`. The product resource is
    public and requires no authentication. Verified live: /order/ and
    /orderitem/ return HTTP 401 without credentials; /product/ is open.
schemes:
  - name: apiKeyQuery
    type: apiKey
    in: query
    parameter: api_key
    sources: [openapi/tindie-openapi.yml]
  - name: usernameQuery
    type: apiKey
    in: query
    parameter: username
    sources: [openapi/tindie-openapi.yml]
  - name: authorizationHeader
    type: apiKey
    in: header
    parameter: Authorization
    format: 'ApiKey <username>:<api_key>'
    sources: [openapi/tindie-openapi.yml]