TextUs

​

Quickstart

curl "https://api.nango.dev/proxy/accounts" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"

import { Nango } from '@nangohq/node';

const nango = new Nango({ apiKey: '<NANGO-API-KEY>' });

const res = await nango.get({
    endpoint: '/accounts',
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>'
});

console.log(res.data);

​

TextUs integration guides

• How do I link my TextUs account? Generate a TextUs API token and connect it to Nango

​

API gotchas

• TextUs’s API tokens never expire and are scoped to the single user that created them, with full access to every feature available in that user’s account. There is no way to narrow a token’s scope.
• The API requires content negotiation: send both Accept: application/vnd.textus+jsonld and Content-Type: application/vnd.textus+jsonld on every request. Standard application/json headers are rejected. Nango’s proxy sets these by default for this integration.
• The API is Hydra/JSON-LD based — list responses come back as hydra:Collection objects (with hydra:member and hydra:totalItems) rather than a bare array, and paging follows hydra:PartialCollectionView.
• Most endpoints are scoped under an account slug in the path, e.g. /{account}/contacts, /{account}/campaigns. A few resource-by-ID endpoints (e.g. /contacts/{contact}/notes, /groups/{group}/contacts) omit the account prefix since the ID itself is already unique. Copy the exact path from the endpoint’s docs page rather than assuming every endpoint follows the same pattern.
• GET /accounts lists every account the connected user has a membership in (including via account hierarchies) — use it to discover the account slug(s) to use in scoped endpoint paths, since TextUs’s own docs never state a fixed one.

​

Pre-built syncs & actions for TextUs