Your tools.
A shared intelligence.

Microsoft Graph

Confirm tenant consent and per-resource permissions. Keep private mail separate from shared workspace content; test revocation and incremental sync.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

Drive, Gmail & Calendar APIs

Scope each Google API independently. Sensitive scopes can require verification; preserve shared-drive membership and individual mailbox consent.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Web API & Events API

Agree channel access, app distribution and retention first. Respect private-channel membership, provider rate limits and message deletion.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Graph / SharePoint REST

Select sites and libraries; validate item-level permissions, document extraction, version handling and access revocation.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

Notion API

Share only approved pages with the integration. Validate child-page access and the current data-source schema before indexing.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Confluence Cloud REST API

Map space and page restrictions; preserve versions and deleted content. Server or Data Center editions need a separate compatibility review.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Box Content API

Preserve collaboration roles, classification and retention constraints. Confirm whether content may be copied into an AI index.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Private SMB bridge

Deploy a private bridge with a bounded service account. Mirror file ACLs, detect changes and test removal of deleted or newly restricted files.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

GitHub REST API

Use a narrowly scoped GitHub App. Preserve repository access and exclude secrets; code execution and merging are separate approvals.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

GitLab REST API

Confirm instance version, group inheritance and token scope. Keep CI secrets and protected repositories out of unapproved retrieval.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Jira Cloud REST API

Carry project permissions and issue-security levels into retrieval. Validate Cloud versus Data Center differences and approval-gate issue changes.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Asana REST API

Agree workspace and project scopes. Preserve private task visibility and verify webhook events before enabling follow-up actions.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Salesforce REST

Map object, record and field-level access. Confirm API entitlements and use a sandbox to validate any approval-gated writes.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

Dataverse / application APIs

Dataverse supports selected apps, not every Dynamics module. Confirm the exact application, endpoint, licence, security roles and field mapping.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

HubSpot CRM APIs

Limit object and property access. Map sensitive CRM fields and verify account-specific API limits before collecting engagement history.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Zoho CRM API

Select the correct regional API domain and OAuth scopes. Reconcile organisation roles, custom modules and field-level restrictions.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Ticketing API

Keep private notes and requester details scoped. Review retention, redaction and the permissions needed for agent-facing answers.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

ServiceNow Table API

Allow-list the instance and tables, mirror ACLs and validate selected fields. Test writes against a disposable target with human approval.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

Marketing API

Prefer aggregate campaign reporting. Respect audience consent and suppression lists; sending or changing a campaign requires explicit approval.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

GraphQL Admin API

Confirm store scopes and protected customer-data approval. Start with operational reads; refunds, fulfilment changes and customer messages require separate controls.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

SAP OData / published APIs

Scope to ERP modules, not HR. Confirm edition, communication arrangements, available entity sets and business authorisations; no autonomous postings.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

Oracle Fusion REST

Confirm the exact Fusion application and release. Preserve business-unit and role boundaries, reconcile source totals and keep posting rights separate.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

JSON-2 / version-specific API

Scope to business modules, excluding HR. Confirm the installed version and API plan: Odoo 19 external API access requires a Custom plan.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Sage Intacct APIs

Confirm API subscription and application authorisation. Scope entities and dimensions, reconcile results and retain a finance sign-off step.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Transaction REST API

Start with read-only transaction reconciliation. Mask customer details and exclude card data; payment initiation and refunds are outside the first pilot.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Transactions API

Confirm the merchant region, currency and API version. Reconcile amounts and fees against provider records; do not expose secret keys or payment credentials.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Remita APIs

Agree the specific Remita service and API generation with the merchant. Production service approval is required; this does not grant access to government accounts.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Product-specific payment APIs

Confirm the contracted product, reporting endpoints and commercial access with Interswitch. A public developer portal is not proof of settlement-data access.

A proposed connection. Confirm the vendor agreement, API access and data contract before committing to delivery.

Temenos Core Banking APIs

Use bank-approved interfaces and test data first. Map installed products, entitlements and customer-data controls; stay outside the transaction path.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Finacle API Connect

Confirm the bank’s Finacle release, licensed APIs and vendor-approved contract. No direct database scraping, posting or unrestricted account access.

A proposed connection. Confirm the vendor agreement, API access and data contract before committing to delivery.

DealCloud API

Map the firm’s custom schema and deal-team permissions. Keep confidential diligence and material non-public information behind the source access boundary.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Research API

Confirm content entitlements and explicit rights for indexing, AI processing and redistribution. API access alone is not a licence to reuse research.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

InsuranceSuite Cloud APIs

Validate the installed product, caller identity and resource-access strategy. Minimise claimant data; underwriting and claims decisions remain with authorised people.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Maximo REST / object structures

Scope object structures and site access. Use an operational reporting boundary; isolate safety-critical control and write actions from AI retrieval.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

PI Web API

Use read-only, bounded time ranges through an approved historian endpoint. Never send control commands or expose operational technology directly to the public web.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

NetBox REST API

Use a read-only token and permitted object scopes. Keep sensitive topology, credentials and precise infrastructure locations tightly controlled.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

TM Forum-aligned bridge

TM Forum is a standards family, not a ready-made vendor connector. Confirm which APIs the operator implements and exclude subscriber profiling and network changes.

A proposed connection. Confirm the vendor agreement, API access and data contract before committing to delivery.

Laserfiche Repository API

Confirm cloud or self-hosted API support, repository access and retention. Preserve record permissions and version history when extracting documents.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

KoboToolbox API

Agree consent, project ownership and export scope. Prefer de-identified data; restrict beneficiary identities and exact field locations.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Explicit REST bridge

Agree APIs, credentials, data ownership and record-level permissions with the system owner. NIS, NCoS, NSCDC and FFS systems need separate approvals; no government access is implied.

An existing AIOS contract family. Provider configuration, mapping and live acceptance are still required.

Vendor-approved interface

A public integration API has not been verified. Agree a vendor-approved interface, data-processing terms and de-identification before scoping any patient-record access.

A proposed connection. Confirm the vendor agreement, API access and data contract before committing to delivery.

OpenMRS REST API

Start with de-identified operational records. Map facility roles, consent and retention; no diagnosis or autonomous treatment decision is proposed.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

DHIS2 Web API

Confirm organisation-unit access and dataset permissions. Begin with aggregate indicators; individual-level tracker data needs separate approval.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Vault REST API

Map document versions, lifecycle states and role restrictions. Agree regulated-use validation; AI summaries do not replace approved records or quality sign-off.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Moodle external services

Enable only the required external functions and service roles. Separate public resources from grades, private submissions and student records.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Canvas REST API

Use scoped developer keys and institutional approval. Preserve course enrolment and role boundaries; no automated grading or admissions decisions.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Autodesk Platform Services

Confirm current ACC / Forma product naming, API coverage and project access. Preserve revisions and review responsibility; drawings are not engineering sign-off.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

iManage Work API

Confirm application registration and API access with the firm. Preserve ethical walls, matter permissions, privilege and client confidentiality.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

eSignature REST API

Limit the initial scope to authorised document and envelope reads. Sending, signing or changing agreements remains an explicitly approved human action.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Power BI REST APIs

Confirm workspace roles, licences and dataset permissions. Report access is not unrestricted row access; preserve row-level security and reconcile any exported results.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Snowflake SQL API

Use read-only roles, approved views, masking policies and query budgets. Never grant unrestricted SQL or treat generated analysis as a reconciled financial result.

A researched integration target with vendor documentation. A Databrew adapter still needs implementation and validation.

Integration contract to confirm

Agree supported records, API availability, consent and access rules with the Hirebrew team. No public API or live connection is claimed; personnel records remain separately restricted.

A proposed connection. Confirm the vendor agreement, API access and data contract before committing to delivery.