Import an NPS response
Imports one NPS answer from another survey tool. Send one answer per request. Requires a secret key (gt_live_); a publishable key gets 403.
- Idempotent.
providerandexternalIdtogether identify the answer. Sending the same pair again updates the stored answer instead of adding a second one. The response is200either way. - Who answered. Send
contactId, or send bothaccountIdandemail. WithcontactId, the Company and email come from that Person. WithaccountIdandemail, GainTrace tries to match a Person at that Company and leavescontactIdnull when it cannot. - Category. GainTrace sets
categoryfromscore: 9-10 promoter, 7-8 passive, 0-6 detractor. - Stored with your other NPS. The answer is saved with
sourceset toapi:<provider>, next to answers collected by GainTrace surveys. Acommentis read for themes. - Webhook. A new answer fires
survey_response.created. A repeat of an answer you already imported firessurvey_response.updated. Imported answers havesurveyId: nullandchannel: import. - No outreach. The import does not send survey emails or follow-up messages.
Scope: write:surveys
Authorizations
Bearer API key. Secret server keys start with gt_live_; client-safe browser keys start with gt_pub_ (write-only, origin-pinned). Create and scope keys in Settings → API Keys.
Body
One NPS answer from another tool. Send contactId, or send both accountId and email. Fields not listed here are rejected.
The tool the answer came from, for example retently.
1 - 64^[a-zA-Z0-9_-]+$The answer's id in that tool. With provider, it makes the import idempotent.
1 - 2550 <= x <= 10ISO 8601 with a UTC offset.
The Company id.
The Person id. GainTrace takes the Company and email from this Person.
2545000255Response
The stored answer, whether it was new or an update.