# IFS Cloud Projection API URL Builder

> Source: https://netray.co/tools/ifs-cloud-projection-odata-url-builder
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Fill in host, realm, projection and entity set to generate the token request and a ready OData GET URL for IFS Cloud projections.

## Category

developer

## Erp

IFS Cloud

## Audience

- IFS developer
- Integration engineer
- IFS administrator

## Tool

**Kind:** template

**Output:** code

**Language:** http

**Fields:**

#### IFS Cloud host

**Key:** host

**Type:** text

**Default:** mycompany.ifs.cloud

**Help:** Host name only, no https://

#### Auth realm

**Key:** realm

**Type:** text

**Default:** mycompanyprod

**Help:** The realm segment used in your IAM token URL.

#### Client ID

**Key:** client_id

**Type:** text

**Default:** my_integration_client

#### Projection name

**Key:** projection

**Type:** text

**Default:** CustomerOrderHandling

**Help:** The projection service name without .svc

#### Entity set

**Key:** entity_set

**Type:** text

**Default:** CustomerOrderSet

#### $select fields

**Key:** select

**Type:** text

**Default:** OrderNo,CustomerNo,State

**Help:** Comma separated, no spaces

#### $filter

**Key:** filter

**Type:** text

**Default:** State eq 'Planned'

#### $orderby

**Key:** orderby

**Type:** text

**Default:** OrderNo desc

#### $top

**Key:** top

**Type:** number

**Default:** 50

**Blocks:**

#### 1. Request an access token

**Body:** POST https://{{host}}/auth/realms/{{realm}}/protocol/openid-connect/token
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials&client_id={{client_id}}&client_secret=<your-secret>

#### 2. Query the projection

**Body:** GET https://{{host}}/main/ifsapplications/projection/v1/{{projection}}.svc/{{entity_set}}?$select={{select}}&$filter={{filter}}&$orderby={{orderby}}&$top={{top}}
Authorization: Bearer <access_token>
Accept: application/json

#### 3. Read the service metadata

**Body:** GET https://{{host}}/main/ifsapplications/projection/v1/{{projection}}.svc/$metadata
Authorization: Bearer <access_token>
Accept: application/xml

**Notes:** URL encode spaces and quotes in the filter before using it from code (a space becomes %20). Entity set and field names must match the projection metadata for your release. Use the $metadata call to confirm them. The client needs a granted permission set for the projection. Never put client secrets in source control.

## Content

**Intro:** IFS Cloud exposes business data through projections that follow OData conventions. Getting the URL and the token call right is the first hurdle for any integration. This builder produces both from a few fields so you can test in a REST client in minutes.

**Sections:**

#### How to use the builder

**Body:** Enter your IFS Cloud host and realm, then the projection and entity set you want to read. Add a select list, a filter and a top value to keep responses small. Copy the generated token request and GET request into your REST client, replace the placeholders for the secret and the token, and run them in order.

**Bullets:**

- Host name without https://
- Projection name without the .svc suffix
- Start with a small $top while testing
- Check $metadata for exact names

#### The URL structure

**Body:** Projection requests follow the pattern host, then /main/ifsapplications/projection/v1/, then the projection service name with .svc, then the entity set. Query options such as $select, $filter, $orderby and $top use standard OData syntax. Authentication uses an access token from the IAM realm of your environment, obtained with the client credentials grant for service integrations.

#### Filtering and paging

**Body:** String values in filters are wrapped in single quotes, and comparison operators are words such as eq, ne, gt and lt. Combine conditions with and or or. For large result sets, use $top together with the paging links the service returns instead of requesting everything at once. Select only the fields you need, which reduces payload and avoids exposing columns you do not require.

#### Common mistakes

**Body:** Frequent problems are using the wrong realm in the token URL, forgetting that the integration client needs a permission set for the projection, and typing entity set names from memory. Another is sending an unencoded filter from code. A 401 usually points to the token or realm, a 403 to missing permissions, and a 404 to a wrong projection or entity set name for your release.

**Cta:** If you are building IFS integrations or want a read-only AI layer on IFS data, Netray can help design it so the queries are visible and role aware.

**Faq:**

#### Does this work for every IFS Cloud release?

**Answer:** The pattern is common across IFS Cloud, but projection names, entity sets and fields change between releases. Always confirm against the $metadata of your own environment before building on a field name.

#### Where do I get the client ID and secret?

**Answer:** An IFS administrator creates an integration client in the identity setup of your environment and grants the permission sets it needs. Ask your administrator rather than reusing a person's credentials.

#### Can I write data with the same URL?

**Answer:** Projections support create and update operations too, but writes need the right permissions and careful validation. This builder covers reads only. Test writes in a non-production environment first.

#### Is anything sent to Netray?

**Answer:** No. The builder fills text in your browser. Do not paste real secrets into the page. Leave the secret as a placeholder and set it in your REST client.

## Search terms

IFS Cloud projection API, IFS Cloud OData URL, IFS Cloud REST API example, IFS projection url format, IFS Cloud access token client credentials, IFS Cloud odata filter, IFS Cloud API query builder, IFS Cloud integration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json