Export a campaign as JSON, CSV, or TXT
Same data as GET /api/v1/campaigns/{id}, served as a downloadable attachment. Content-Disposition filenames use only the resolved campaign key, never a domain and never the raw identifier supplied by the caller.
For an archived key (see GET /api/v1/campaigns/{id}), only format=json has an honest answer - it serves the same ArchivedCampaign object as an attachment. format=csv and format=txt stay 404 for an archived key: both promise live enrichment (URL, status, relationship score) that an archived snapshot's last-known member set does not retain, and a silently thinner export under the same content-type contract would be worse than an honest 404.
Request
- Base URL: https://phishunt.io
- URL: https://phishunt.io/api/v1/campaigns/{id}/export
- Auth: none declared
Path parameters
Stable campaign key (preferred, e.g. 0c1b79ab9b24) or the legacy numeric cluster id, which is resolved for the last 180 days.
Query parameters
Export format.
Response
Campaign data as an attachment. CSV columns are uuid,domain,url,company,status,first_seen,relationship_score,evidence_types,registrable_domain (semicolon-joined signal ids for evidence_types; registrable_domain is appended last so existing column offsets never shift); TXT is one member URL per line. format=json on an archived key returns the ArchivedCampaign shape instead.
Changes
No recorded changes to this operation across all 1 revision of this API.