Survey API funding and exports

The external signed survey campaign API and the dashboard-session funding API are different interfaces. A successful POST /api/v1/campaigns/create creates a draft; it does not pay for or launch it. Complete redirects and quota setup first, then review the exact cost and account balance in the dashboard.

Interface	Method and path	Authentication	Result
External survey API	GET /api/v1/campaigns/downloadresponses	X-Api-Key plus enc signature.	Downloadable campaign response data, subject to account and query context.
External survey API	GET /api/v1/campaigns/invoices	X-Api-Key plus enc signature.	Invoice data from the legacy advertiser endpoint.
Dashboard finance	GET /performance-marketing/v2/billing/balance	Advertiser dashboard bearer token.	Shared available, reserved, and spent balance.
Dashboard finance	GET /performance-marketing/v2/billing/allocations	Advertiser dashboard bearer token.	Existing allocations as {items}.
Dashboard finance	POST /performance-marketing/v2/billing/survey-campaigns/{campaignId}/allocate	Advertiser dashboard bearer token.	Allocation for an eligible owned DRAFT or PENDINGAPPROVAL campaign.

The allocation service checks that the survey campaign belongs to the authenticated advertiser (unless an administrator acts), that it is in an eligible status, that estimated total cost is positive, and that sufficient shared balance exists. The allocation is idempotent per campaign. A survey already paid outside this wallet is rejected rather than charged twice. Check the allocation result and campaign payment state before submitting for review.

Funding methods, billing profile, and payment captures are documented in the shared billing API reference. That page describes dashboard financial routes used by both product lines; it does not change the survey campaign navigation or credential rules. Never put a dashboard bearer token into the external signed API request or the external API key into a finance request.