OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured APIs across the declared product scope
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
Projection entity sets expose structured records, subject to per-projection grants.
IFS Cloud projection API Explorer ↗
OData projection APIs · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
The read examples use top/skip pagination; collection consistency must be verified for the chosen projection.
IFS OData aggregation and paging examples ↗
Pagination with skip and top · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
OData filters and ordering are documented. Aggregation examples do not prove arbitrary joins across all projections.
IFS OData aggregation and paging examples ↗
Filter, orderby and apply examples · Checked 2026-10-16
Access cost barrier -
-
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
IFS Cloud API usage policy ↗
IFS Cloud API usage policy · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
The documented IAM setup lets a customer administrator authorize an external projection client.
IFS Cloud OAuth integration quick start ↗
Create an IAM client · Checked 2026-10-16
Downstream permission 7.5/10
Published purpose and confidentiality boundaries
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
Projection APIs support external integrations; entity APIs and database BI views have distinct trusted-system restrictions. This is not unlimited redistribution permission.
IFS Cloud API usage policy ↗
Projection and entity API usage · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface -
-
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
API Explorer describes projection CRUD verbs, but the reviewed material does not establish a named business-object create/update contract. Verify the selected projection operations before scoring writes.
IFS Cloud projection API Explorer ↗
Projection APIs and supported methods · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
A customer IAM client can call granted projections; native endpoint configuration is not required.
IFS Cloud OAuth integration quick start ↗
Make an authenticated request · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
A general updated-record extraction contract is not established for every assessed object.
IFS Cloud API usage policy ↗
IFS Cloud API usage policy · Checked 2026-10-16
Limit visibility -
-
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
The reviewed interface does not establish a universal numeric request quota and recovery contract.
IFS Cloud API usage policy ↗
IFS Cloud API usage policy · Checked 2026-10-16
CDC and deletion capture -
-
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
Complete deletion identity coverage is not established on this assessed route.
IFS Cloud API usage policy ↗
IFS Cloud API usage policy · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
A fresh authorized collection traversal can rebuild the scoped current record set. It does not replay intermediate states or recover historical deleted payloads; verify paging completeness before replacing a prior copy.
IFS OData aggregation and paging examples ↗
Current-state collection retrieval · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
Projection results provide structured records to the authorized external client.
IFS OData aggregation and paging examples ↗
Read response examples · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
IFS Cloud API usage policy ↗
IFS Cloud API usage policy · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
Selected records can leave through projection results; complete application reconstruction is unverified.
IFS Cloud projection API Explorer ↗
Projection scope · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
An external integration can call projection APIs; reusable native definitions are not established.
IFS Cloud OAuth integration quick start ↗
Integration quick start · Checked 2026-10-16
Rights to custom logic -
-
IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes.
Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
IFS Cloud API usage policy ↗
IFS Cloud API usage policy · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A customer administrator creates an IAM client and service-account mapping for OAuth client credentials. Projection grants constrain the resulting token; Basic authentication is reserved for upgrade scenarios.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
OData projection endpoints expose authorized records and metadata. Documented examples include filters, ordering, pagination and aggregation, but each projection needs its own supported-operation check.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer IAM client for projection APIs | OAuth client credentials | Customer | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Public technical guidance does not establish a complete subscription floor or fixed API surcharge. Confirm the contracted projection entitlement rather than treating API class names as prices.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
API Explorer describes projection CRUD verbs. This review does not establish a named business-object create/update contract; inspect the selected projection schema before assigning an operation.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
The read contract supports repeatable collection retrieval. It does not establish a universal deletion feed or retained replay window for every projection.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. Complete deletion identity coverage is not established on this assessed route. | IFS Cloud API usage policy ↗IFS Cloud API usage policyChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. A fresh authorized collection traversal can rebuild the scoped current record set. It does not replay intermediate states or recover historical deleted payloads; verify paging completeness before replacing a prior copy. | IFS OData aggregation and paging examples ↗Current-state collection retrievalChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
A client can retain structured projection results. Full attachments, history, configuration and independently executable native extensions are not established by these interfaces.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customer applications can orchestrate projection operations. This review establishes external code only (native workflow portability needs separate evidence).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured APIs across the declared product scopeIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. Projection entity sets expose structured records, subject to per-projection grants. | IFS Cloud projection API Explorer ↗OData projection APIsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. The read examples use top/skip pagination; collection consistency must be verified for the chosen projection. | IFS OData aggregation and paging examples ↗Pagination with skip and topChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. OData filters and ordering are documented. Aggregation examples do not prove arbitrary joins across all projections. | IFS OData aggregation and paging examples ↗Filter, orderby and apply examplesChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. The documented IAM setup lets a customer administrator authorize an external projection client. | IFS Cloud OAuth integration quick start ↗Create an IAM clientChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation. | IFS Cloud API usage policy ↗IFS Cloud API usage policyChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | Published purpose and confidentiality boundariesIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. Projection APIs support external integrations; entity APIs and database BI views have distinct trusted-system restrictions. This is not unlimited redistribution permission. | IFS Cloud API usage policy ↗Projection and entity API usageChecked 2026-10-16 |
| Which external write operations are documented? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. API Explorer describes projection CRUD verbs, but the reviewed material does not establish a named business-object create/update contract. Verify the selected projection operations before scoring writes. | IFS Cloud projection API Explorer ↗Projection APIs and supported methodsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. A customer IAM client can call granted projections; native endpoint configuration is not required. | IFS Cloud OAuth integration quick start ↗Make an authenticated requestChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. A general updated-record extraction contract is not established for every assessed object. | IFS Cloud API usage policy ↗IFS Cloud API usage policyChecked 2026-10-16 |
| How are integration limits disclosed? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. The reviewed interface does not establish a universal numeric request quota and recovery contract. | IFS Cloud API usage policy ↗IFS Cloud API usage policyChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. Projection results provide structured records to the authorized external client. | IFS OData aggregation and paging examples ↗Read response examplesChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination. | IFS Cloud API usage policy ↗IFS Cloud API usage policyChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. An external integration can call projection APIs; reusable native definitions are not established. | IFS Cloud OAuth integration quick start ↗Integration quick startChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -IFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished. | IFS Cloud API usage policy ↗IFS Cloud API usage policyChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedIFS Cloud 26R1 customer-authorized OData projections, selected entity sets and operations; entity APIs, direct database BI views and complete tenant restore are separate routes. Selected records can leave through projection results; complete application reconstruction is unverified. | IFS Cloud projection API Explorer ↗Projection scopeChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Access cost barrier: The complete fixed access entitlement and API fees relative to the lowest paid plan are not established by the reviewed technical documentation.
- Write interface: API Explorer describes projection CRUD verbs, but the reviewed material does not establish a named business-object create/update contract. Verify the selected projection operations before scoring writes.
- Refresh mechanism: A general updated-record extraction contract is not established for every assessed object.
- Limit visibility: The reviewed interface does not establish a universal numeric request quota and recovery contract.
- Post-cancellation access: The reviewed extraction documentation does not establish contractual retrieval rights after cancellation or license termination.
- Rights to custom logic: Ownership, reusable export and independent execution rights for native workflow artifacts remain unestablished.
- CDC and deletion capture: Complete deletion identity coverage is not established on this assessed route.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.