Endpoint search
A vendor API is hundreds of operations, each with its own parameters and response shape. Plexara indexes every operation of a connected API by meaning. The assistant describes the data it needs, reads the matching call, and makes it. Sign-in is already done. Operations a role may not call never appear in the results.
Large APIs are organized into sections. The assistant sees the sections first and opens only the one it needs, so a catalog of 577 operations costs it no more attention than a catalog of 15.
What the agent calls. This is the exchange the agent has with Plexara on your behalf, shown for the technical reader. You ask in plain language; you never type any of it.
| Asked | API | First result |
|---|---|---|
| How much has a donor given over their lifetime? | Blackbaud Raiser's Edge NXT, 577 operations | GET /constituent/v1/constituents/{constituent_id}/givingsummary/lifetimegiving |
| Which customer records changed since yesterday? | Salesforce, 91 operations | GET /services/data/v67.0/sobjects/{sobject}/updated |
| Which card transactions settled yesterday? | Datacap, 44 operations | POST /V2/Credit/TransactionTotals |
How a connection signs in, who may call what, and where every call is logged is covered on the API Gateway page.
Knowledge pages
Vendor documentation describes the call. A knowledge page on the connection records how this organization uses it: the accounts, the fields, the reports finance trusts, and the traps that return a plausible wrong number. The assistant reads that page before it reports.
The notes below are behaviors teams recorded after hitting them. None of them appear in the vendor spec.
1
A monthly request still comes back as a row per day. Reach is stored under a different name than the one asked for, and daily unique reach cannot be summed into a monthly figure.
2
A property id with a typing error and a property the account cannot see return the same permission error. A site parameter is reportable only after it is registered as a custom dimension, and registration is not backfilled.
3
Every saved-query call needs two fixed product settings. Leave them out and the API answers as if the query does not exist.
4
Missing values arrive as a sentinel number or a dash, never as zero, and three of the public APIs report errors inside an ordinary success response.
Endpoint search finds the call. The knowledge page is why the number that comes back is reported correctly. How those pages are captured and applied is on Knowledge Capture.
In production
Plexara connects to any API with published documentation. These are the ones already running on customer deployments. Vendor names are nominative use only.
Where campaigns are published, bought, and measured: social management, web analytics, programmatic advertising, email, and text messaging.
| API | Operations | Access | What the assistant can reach |
|---|---|---|---|
| Sprout Social Sprout Social API v1 | 15 | Read | Owned-profile and post analytics, inbox messages, care cases, Listening topics, publishing posts, and account metadata. |
| Hootsuite Hootsuite Platform API v1 | 48 | Read and write | Scheduled and sent messages, message and comment approvals, media, social profiles, and organization, team, and member administration. |
| Google Analytics 4 Google Analytics Data API v1beta | 11 | Read | Standard, pivot, batch, and realtime reports, dimension and metric metadata, compatibility checks, and audience exports. |
| Display & Video 360 Display & Video 360 API v4 | 178 | Read and write | Partners, advertisers, campaigns, insertion orders, line items, creatives, targeting, and media. |
| Google Bid Manager Bid Manager API v2 | 7 | Read and write | Report queries for Display & Video 360: create, run, poll, and download. |
| Iterable Iterable API | 148 | Read and write | Campaigns and campaign metrics, templates, users, lists, events, experiments, catalogs, journeys, subscriptions, and data exports across email, SMS, push, in-app, and WhatsApp. |
| Texting123 Texting123 Reporting API v2 | 4 | Read | Sent SMS and MMS totals, opt-ins and opt-outs by campaign keyword, coupon issue and redemption totals, and contact counts by status. |
| YouTube YouTube Data API v3 and YouTube Reporting API | REST | Read | Video metadata, and channel reporting for each channel an organization owns. |
Systems of record for customers, donors, members, and guests, plus the sync tool that moves audiences between them.
| API | Operations | Access | What the assistant can reach |
|---|---|---|---|
| Salesforce Salesforce REST API v67.0 | 91 | Read and write | SOQL and SOSL queries, object metadata, record create, read, update, and upsert, composite calls, Bulk API 2.0, reports and dashboards, approvals, and flows. |
| Raiser's Edge NXT Blackbaud SKY API | 577 | Read, with a separate read and write connection | Constituents, gifts, fundraising hierarchy, memberships, events, opportunities, volunteers, consent, saved queries, and standard reports across 18 API sections. |
| zkipster Events zkipster Events API | 67 | Read and write | Events, guest lists, guests, sessions, and webhook subscriptions. |
| Hightouch Hightouch REST API | 37 | Read and write | Syncs and their run history, models, sources, and destinations. |
Card settlement reporting and the back-office system that holds customers and orders.
| API | Operations | Access | What the assistant can reach |
|---|---|---|---|
| Datacap Datacap Reporting API | 44 | Read | Card transaction detail, summaries, and totals by date range, plus billing reconciliation. |
| Sage X3 Sage X3 GraphQL API | GraphQL | Read | ERP customers, orders, and invoices, explored through the GraphQL schema. |
Government and open data joined to internal sales by geography: demographics, local economy, traffic, and weather.
| API | Operations | Access | What the assistant can reach |
|---|---|---|---|
| Census Data API Census Data API | 6 | Read | American Community Survey 5-year tables and profiles, County Business Patterns, Population Estimates, and variable discovery. |
| Census Geocoding Services Census Geocoding Services | 5 | Read | Street address to coordinates, and address or coordinates to state, county, tract, and block. |
| BEA Regional Data API BEA Regional Data API | 1 | Read | County personal income, per-capita income, population, and GDP by industry. |
| BLS Public Data API v2 BLS Public Data API v2 | 2 | Read | Monthly county unemployment and labor force series. |
| NWS API NWS API | 3 | Read | Active watches, warnings, and advisories by zone or point, and the official forecast. |
| Open-Meteo Open-Meteo Archive and Forecast APIs | 2 | Read | Daily and hourly weather for any coordinate back to 1940, and a 16-day forecast. |
| ArcGIS traffic counts ArcGIS feature services | 2 | Read | Annual average daily traffic counts for road segments near a point. |
Several connections at once
The questions below are asked of several connections in one session. They are already in use.
Did the spring membership campaign work, and which channel carried it?
The assistant reads what was bought, how the posts and videos performed, what reached the site, who opened the email, and which gifts and memberships followed, then reports them on one timeline.
APIs. Display & Video 360, Sprout Social, YouTube, Google Analytics 4, Iterable, Raiser's Edge NXT
Alongside. Broadcast ratings and streaming viewership in the warehouse
Is this address a good site for a seasonal store?
One geocoding call turns the address into coordinates and a county and tract code. Every other source keys off those: trade-area income and population, competitor counts, county retail GDP, unemployment, cars passing the corner, and whether past peak days were rained out.
APIs. Census Geocoding Services, Census Data API, BEA Regional, BLS LAUS, State DOT traffic, Open-Meteo, National Weather Service
Alongside. Ten years of per-location sales
What did last week's text campaign and posts do for store sales?
The assistant reads what was published and when, the opt-ins and coupon redemptions by keyword, and web sessions by channel, then sets those figures against daily sales by location.
APIs. Google Analytics 4, Texting123, Hootsuite
Alongside. Point-of-sale transactions
Which customers changed in the CRM but not yet in the ERP?
The assistant asks Salesforce for accounts updated in a window, looks up each customer number in the ERP, and lists the differences. Once the logic is settled it becomes a script that runs without a conversation.
APIs. Salesforce, Sage X3
Alongside. A managed script that runs the comparison on a schedule
Do yesterday's settled card totals match what the registers recorded?
The assistant pulls settled totals from the payment processor's reporting API and compares them with register totals by location, then lists the locations that disagree.
APIs. Datacap
Alongside. Point-of-sale transactions
The list above is what is connected today. An API with published documentation is connected the same way, and an admin on your team manages connections in the portal.
How a connection signs in, who may call what, and where every call is loggedNext
How a connection signs in, who may call what, and where every call is logged.
GDPR / ePrivacy Compliant
We use cookies and similar technologies to ensure the proper functioning of our platform. Analytics cookies help us understand how visitors interact with our website so we can improve our services. You can manage your preferences below.
For more information, see our Privacy Policy and Terms of Service.
Plexara