TAP's public API (version 2.0) gives a university's own systems direct access to its TAP data: prospects, chat transcripts, ambassadors, content posts and live streams. It is mostly read-only, with one write operation: updating a prospect's admissions journey stage, so a CRM can keep TAP in step with application outcomes. The API is included in the annual platform licence fee.
Full technical reference, including request formats, field definitions and examples: TAP API documentation.
What the API can do
Prospects (read). List with date filters and sorting, get one prospect in full, or pull a feed of recently updated prospects.
Journey stage (read and write). Read each prospect's admissions stage, and set it. This is the only write operation.
Chat transcripts (read). List prospects with their chats and messages, or pull a feed of recent chat activity.
Ambassadors (read). List with search, or get one ambassador.
Posts (read). List image and video posts with search and filters, or get one post.
Live streams (read). List events by status, and list the prospects registered for an event and whether they watched.
The API returns data only for the university whose credentials are used. It has 13 operations in total.
Data available
Prospects. Name, email, nationality, country, academic level, study start, admissions stage, application ID, marketing preference, registration, last updated and last active dates, UTM acquisition data (source, medium, campaign, landing page), answers to the University's sign-up questions, university SSO attributes, number of chats and an engagement score.
Prospect detail. Everything above, plus subjects, interests and an engagement history covering chats, group chats, live streams, posts and FAQs, with the ambassador involved and any feedback score.
Chat transcripts. For each prospect, every chat (type, name, start and last activity) and every message (text, sender name, sender role as prospect, ambassador or admin, and timestamp). Closed chats only by default, or all chats on request.
Ambassadors. Name, email, description, introduction, profile (student or staff type, subject, course, year of study, interests, location), tags, registration and activity dates, and which features they are active for (feed, chat, content, FAQ).
Posts. Type (image or video), caption, tags, author, media links, publication status, and share, like and view counts.
Live streams. Name, description, start and end times, status (upcoming, in progress, completed, cancelled, on demand) and archive status. For each event, the registered prospects and whether each watched live or on demand.
Journey stage values
The journey stage write accepts one of five stages, matching the stages prospects can select on the platform:
Researching options
Applied
Received an offer
Accepted an offer
Enrolled
A stage update does not notify the prospect. It is recorded in the prospect's stage history, and the response confirms whether the stage changed or was already set.
Keeping systems in sync
The API offers two ways to pull data on a schedule.
Paged lists with filters. Request records page by page (up to 100 per page), filtered by registration, last active or last updated date, and sorted by most fields. Best for initial loads and full syncs.
Feeds. One request returns every prospect updated, or every prospect with chat activity, in the last 1 to 168 hours (up to 1,000 records per request). Best for simple recurring jobs and tools that cannot page through results, such as many no-code connectors.
For chat transcripts, the API also supports incremental sync. After an initial full load, each later run requests only prospects with new chat activity and only the messages created since the last run. Message IDs are stable, so repeated messages can be removed reliably.
The feeds are designed for overlap: running a job with a window slightly longer than its schedule ensures a late or failed run misses nothing.
Common use cases
CRM sync of prospects. Pull new and updated prospects into Microsoft Dynamics, Salesforce, Slate or another CRM, including UTM data, sign-up answers and SSO attributes for matching against applicant records.
Two-way admissions stage sync. Read the stage prospects report on TAP, and write the CRM's stage back to TAP when an application is received, an offer is made or a student enrols.
Conversation records in the CRM. Import chat transcripts so admissions teams can see what each prospect discussed with ambassadors.
Event follow-up. List who registered for each live stream and whether they watched live or on demand, to target follow-up communications.
Content and ambassador reporting. Pull post performance (views, likes, shares) and ambassador activity into a data warehouse or BI tool.
Access, security and limits
Authentication
Every API call is made on behalf of one university. TAP issues each university its own API key, available in TAP under Settings → Integrations → API Access. The key is the institution's credential: the prospects, transcripts, ambassadors, posts and live streams returned all belong to that university. It should be treated as a secret, sent only in a request header or body, and stored with the integration's other credentials.
The key can be used in either of two ways:
API key on every request. Send the key in the X-API-Key header, with no login step. Best for scheduled jobs and tools that can only store a fixed header.
Bearer token. Exchange the key once for a token (a JWT valid for 24 hours), then send Authorization: Bearer <token>. When the token expires, log in again; there is no refresh token. Best for integrations that prefer short-lived credentials on each call.
Use one method per request. If both are sent, only the bearer token is checked, so an expired or invalid token fails the request even when a valid key is also present.
Integration label. The optional X-CRM-Name header names the calling integration (for example, the CRM product). It is not a credential, does not change what the API returns, and is read only when the API key is used. The login call carries the same label in its required crm_name field.
Getting a token. POST /v2/public/auth/login takes three required JSON fields and no credential header:
email: the university's CRM integration user, not a prospect's or ambassador's email.
api_key: the university API key.
crm_name: the name of the integration partner, for example ExampleCRM.
A successful login returns the token in data.token. Login is limited to 10 requests per minute.
Responses to authentication problems.
400: the login body was rejected before credentials were checked, for example an invalid email format.
401 Invalid credentials.: the login email and key were not accepted.
401 User is not authorized.: a missing, wrong or expired key or token on a data request.
429: more than 10 login requests in a minute.
Code examples for both methods are in the TAP API documentation.
Security and limits
Data scope. Every request returns only the authenticated university's data.
Encryption. All API traffic is encrypted in transit using TLS. Data is hosted in AWS London, United Kingdom.
Rate limits. 10 requests per minute per endpoint, and 60 per minute for journey stage updates.
Formats. JSON over HTTPS. All timestamps are ISO 8601 in UTC.
What the API does not do
It does not create or delete prospects, ambassadors, posts or live streams, or edit any data other than a prospect's journey stage.
It does not push data out. There are no webhooks, so integrations pull data on a schedule using the feeds or filtered lists.
It does not expose platform configuration or Admin Dashboard analytics reports. These remain available as exports from the Admin Dashboard.
If the University needs something outside this scope, TAP can review the requirement case by case.