generated: '2026-07-17'
method: searched
source: https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api
api: Campaign Spend API
conventions:
  authentication:
    style: api-key-in-path
    detail: Static per-customer key as the final path segment; see authentication/app-samurai-authentication.yml
  base_url: https://api.appsamurai.com
  transport: REST over HTTPS
  http_methods: [GET]
  request_format: query-string filters on a keyed GET
  response_format: JSON (campaign metadata + daily spend object keyed by date)
  filtering:
    style: query-parameter
    params:
      - {name: start_date, type: string, format: "YYYY-MM-DD"}
      - {name: end_date, type: string, format: "YYYY-MM-DD"}
      - {name: campaign_id, type: string}
      - {name: bundle_id, type: string}
      - {name: platform, type: string, values: [ios, play]}
      - {name: campaign_name, type: string}
      - {name: country, type: string, format: "ISO 3166-1 alpha-2"}
  date_windowing:
    default: If end_date is omitted, the API returns the last 30 days of spend data.
  pagination:
    supported: false
    note: No pagination documented; results are scoped by date/campaign filters.
  idempotency:
    supported: false
    note: Read-only GET surface; provider documents no idempotency-key contract.
  versioning:
    scheme: none-documented
    note: No API version prefix beyond /api/customer-pull/.
  rate_limiting:
    documented: false
  error_envelope:
    style: http-status
    note: Standard HTTP status codes (400/401/404/500); see errors/app-samurai-problem-types.yml
cross_links:
  errors: errors/app-samurai-problem-types.yml
  authentication: authentication/app-samurai-authentication.yml