All integrations

Retently

MARKETING · MARKETING

NPS campaigns, customers, companies, scores, and feedback in the account they connected.

Connecting Retently in practice

Retently treats its date filters as an exact UTC instant rather than a day, so endDate=2024-12-31 excludes everything after 00:00:00 UTC on 31 December, and a timestamp sent in milliseconds is not detected and resolves to a far-future date. The API allows 150 requests a minute, and a read-only key gets 403 Forbidden on every POST or DELETE.

Scopes that draw scrutiny

  • API key with Write permission Retently’s own permission level. It is required for POST /api/v2/customers, /survey, /import, /response/tags, /response/topics and for the customer deletes, so it can send surveys to real people on the account’s credits.
  • API key with Read permission GET only. Enough for dashboards and reporting, including feedback text and NPS scores, and the right default for an agent that only reads.
  • X-Api-Key header versus api_key query parameter Both authenticate. Retently marks the query-parameter form "not recommended" because keys in URLs are logged by browsers, proxies and servers.

Rate limits

  • 150 requests per minute against https://app.retently.com.
  • List endpoints default to 20 items and accept limit up to 1,000.
  • POST /api/v2/import accepts up to 200 historical feedback responses per request, synchronously.

Worth knowing

  • Every request is scoped to the account that owns the key, and a resource that is missing, deleted or owned by another account all return an identical 404 — so an agent cannot distinguish "gone" from "not yours".
  • Imported feedback counts toward the NPS score and trend but is excluded from delivery and funnel stats, consumes no send quota, and never triggers webhooks or reminders.
  • GET /api/v2/ping is the cheap way to read the plan, the survey credit balance for the current period and the usage counters before spending any of them.
  • The legacy Authorization: api_key=YOUR_KEY form is still fully supported, so older code keeps working and never gets nudged toward the header form.

Checked against Retently CX API (v2) reference (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

retently_delete_api_v2_customersWRITE

Delete delete customers via DELETE /api/v2/customers

api
retently_delete_api_v2_feedbackWRITE

Delete delete feedback records via DELETE /api/v2/feedback

api
retently_delete_api_v2_outboxWRITE

Delete delete outbox records via DELETE /api/v2/outbox

api
retently_delete_api_v2_suppressions_domains_by_idWRITE

Delete remove suppressed domain via DELETE /api/v2/suppressions/domains/{id}

api
retently_delete_api_v2_suppressions_emails_by_idWRITE

Delete remove suppressed email via DELETE /api/v2/suppressions/emails/{id}

api
retently_get_api_v2_by_metric_scoreREAD

Retrieve get latest score via GET /api/v2/{metric}/score

api
retently_get_api_v2_campaignsREAD

Retrieve get campaigns via GET /api/v2/campaigns

api
retently_get_api_v2_companiesREAD

Retrieve get companies via GET /api/v2/companies

api
retently_get_api_v2_companies_by_companyidREAD

Retrieve get company by id via GET /api/v2/companies/{companyId}

api
retently_get_api_v2_customersREAD

Retrieve get customers via GET /api/v2/customers

api
retently_get_api_v2_customers_by_customeridREAD

Retrieve get customer by id via GET /api/v2/customers/{customerId}

api
retently_get_api_v2_feedbackREAD

Retrieve get feedback via GET /api/v2/feedback

api
retently_get_api_v2_feedback_by_feedbackidREAD

Retrieve get feedback by id via GET /api/v2/feedback/{feedbackId}

api
retently_get_api_v2_nps_campaignsREAD

Retrieve get campaigns deprecated via GET /api/v2/nps/campaigns

api
retently_get_api_v2_nps_customers_responseREAD

Retrieve get responses deprecated via GET /api/v2/nps/customers/response

api
retently_get_api_v2_nps_templatesREAD

Retrieve get templates deprecated via GET /api/v2/nps/templates

api
retently_get_api_v2_outboxREAD

Retrieve get outbox via GET /api/v2/outbox

api
retently_get_api_v2_pingREAD

Retrieve get account status via GET /api/v2/ping

api
retently_get_api_v2_reportsREAD

Retrieve get campaign reports via GET /api/v2/reports

api
retently_get_api_v2_suppressions_domainsREAD

Retrieve get suppressed domains via GET /api/v2/suppressions/domains

api
retently_get_api_v2_suppressions_emailsREAD

Retrieve get suppressed emails via GET /api/v2/suppressions/emails

api
retently_get_api_v2_templatesREAD

Retrieve get templates via GET /api/v2/templates

api
retently_get_api_v2_templates_by_templateidREAD

Retrieve get template by id via GET /api/v2/templates/{templateId}

api
retently_get_api_v2_trendsREAD

Retrieve get trend groups via GET /api/v2/trends

api
retently_get_api_v2_trends_by_groupidREAD

Retrieve get trends of a group via GET /api/v2/trends/{groupId}

api
retently_post_api_v2_customersWRITE

Create or update create or update customers via POST /api/v2/customers

api
retently_post_api_v2_customers_resubscribeWRITE

Create or update resubscribe customers via POST /api/v2/customers/resubscribe

api
retently_post_api_v2_customers_unsubscribeWRITE

Create or update unsubscribe customers via POST /api/v2/customers/unsubscribe

api
retently_post_api_v2_importWRITE

Create or update import feedback via POST /api/v2/import

api
retently_post_api_v2_nps_customers_response_tagsWRITE

Create or update update feedback tags deprecated via POST /api/v2/nps/customers/response/tags

api
retently_post_api_v2_response_tagsWRITE

Create or update add feedback tags via POST /api/v2/response/tags

api
retently_post_api_v2_response_topicsWRITE

Create or update add feedback topics via POST /api/v2/response/topics

api
retently_post_api_v2_suppressions_domainsWRITE

Create or update add suppressed domain via POST /api/v2/suppressions/domains

api
retently_post_api_v2_suppressions_emailsWRITE

Create or update add suppressed email via POST /api/v2/suppressions/emails

api
retently_post_api_v2_surveyWRITE

Create or update send transactional survey via POST /api/v2/survey

api
retently_post_api_v2_sync_attributesWRITE

Create or update sync customer attributes via POST /api/v2/sync-attributes

api

Put Retently behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.