App Samurai · Authentication Profile

App Samurai Authentication

Authentication

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

CompanyMobileAdvertisingUser AcquisitionApp MarketingAttributionMonetizationMobile SDKProgrammatic
Methods: apiKey Schemes: 1 OAuth flows: API key in: path

Security Schemes

apiKeyPath apiKey
· in: path (api_key)

Source

Authentication Profile

app-samurai-authentication.yml Raw ↑ 
generated: '2026-07-17'
method: searched
source: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
docs: https://help.appsamurai.com/en/collections/12520260-campaign-spend-api-documentation
summary:
  types: [apiKey]
  api_key_in: [path]
  oauth2_flows: []
  notes: >-
    The App Samurai Campaign Spend API authenticates with a static per-customer
    API key that is embedded directly in the request path segment
    (/api/customer-pull/spent/{api_key}). The key is issued by the customer's
    account manager; there is no OAuth, no self-service key rotation portal, and
    no documented scope model. Mobile SDKs (Ads / Storyly / attribution) use
    per-app tokens configured at SDK init, out of band from this REST API.
schemes:
  - name: apiKeyPath
    type: apiKey
    in: path
    parameter: api_key
    description: >-
      Unique per-customer API key provided by the App Samurai account manager,
      passed as the final path segment of the Campaign Spend endpoint.
    sources: [https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api]