Skip to main content
Use the @bijection/connectors/suitecrm entrypoint to declare SuiteCRM resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Module records

pull: date_modified windows over the V8 JSON:API, no deletions

The following example matches configuration standard.

Configuration: standard

Case: suitecrm/records/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: suitecrm. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a suitecrm OAuth bearer; setup endpoint is the V8 base, such as https://crm.example.com/legacy/Api/V8/. records.pull reads module/<Module> filtered date_modified gte, sorted by date_modified, 100 rows by page[number], re-asking from one second before the latest date_modified read, and carries the latest one to the next pass. SuiteCRM documents no way to read deleted records, so nothing is withdrawn; the date_modified and filter spellings are not documented, so the read accepts an ISO 8601 instant or YYYY-MM-DD HH:MM:SS (UTC) and refuses anything else. No account identity and no write are declared. Nothing here has run against SuiteCRM.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.