# Paging issue with Graph API

**URL:** <https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358>\
**Category:** SHF Discussion and Questions\
**Tags:** webservice-connector, identity-security-cloud, aggregation\
**Created:** [February 17, 2026, 2:48pm UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358 "2026-02-17T14:48:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abhim1](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/abhim1/32/39020_2.png) [@Abhim1](https://developer.sailpoint.com/discuss/u/Abhim1)\
**Post date:** [February 17, 2026, 2:48pm UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/1 "2026-02-17T14:48:12Z")

</div>

Hi Sailors,

My issue is similar to the below post.  
[Paging step based on response attribute containing @ symbol](https://developer.sailpoint.com/discuss/t/paging-step-based-on-response-attribute-containing-symbol/37439).

I am trying to configure a Graph API endpoint using Webservices SAAS connector and with the below paging command it is getting terminated in the first page. Kindly provide your suggestions.

`TERMINATE\_IF $response.[‘@odata.nextLink’]$ == NULL  
$endpoint.fullUrl$ = $response.[‘@odata.nextLink’]$`

The response is

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/2/9/297d1ad755ef6f8249b0a1502d77334f930ea4db.png)

---

<div class="post-metadata">

**Author:** ![Deepak\_Chaudhary](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/deepak_chaudhary/32/34380_2.png) [@Deepak\_Chaudhary](https://developer.sailpoint.com/discuss/u/Deepak_Chaudhary)\
**Post date:** [February 17, 2026, 4:41pm UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/2 "2026-02-17T16:41:09Z")

</div>

> [@Abhim1](#):
>
> My issue is similar to the below post.  
> [Paging step based on response attribute containing @ symbol](https://developer.sailpoint.com/discuss/t/paging-step-based-on-response-attribute-containing-symbol/37439).
> 
> I am trying to configure a Graph API endpoint using Webservices SAAS connector and with the below paging command it is getting terminated in the first page. Kindly provide your suggestions.
> 
> `TERMINATE_IF $response.[‘@odata.nextLink’]$ == NULL $endpoint.fullUrl$ = $response.[‘@odata.nextLink’]$`

@Abhim1 could you please replace your current configuration with the following:  
TERMINATE\_IF $response.[‘\ @odata.nextLink’]$ == NULL

The correct configuration for the paging step should use a grave accent (backtick) to escape the special character.

---

<div class="post-metadata">

**Author:** ![Abhim1](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/abhim1/32/39020_2.png) [@Abhim1](https://developer.sailpoint.com/discuss/u/Abhim1)\
**Post date:** [February 17, 2026, 5:45pm UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/3 "2026-02-17T17:45:16Z")

</div>

> [@Deepak\_Chaudhary](#):
>
> TERMINATE\_IF $response.[‘\ @odata.nextLinkodata.nextLink’]$ == NULL

I still see the same result, It is aggregating the top 1000 records

---

<div class="post-metadata">

**Author:** ![kompala](https://avatars.discourse-cdn.com/v4/letter/k/ea5d25/32.png) [@kompala](https://developer.sailpoint.com/discuss/u/kompala)\
**Post date:** [February 18, 2026, 3:21am UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/4 "2026-02-18T03:21:39Z")

</div>

@Abhim1 Are you able to get the value when you do `response.[‘@odata.nextLink’]` ?

---

<div class="post-metadata">

**Author:** ![Abhim1](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/abhim1/32/39020_2.png) [@Abhim1](https://developer.sailpoint.com/discuss/u/Abhim1)\
**Post date:** [February 18, 2026, 4:31am UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/6 "2026-02-18T04:31:35Z")

</div>

Thank you all for your suggestions.

I found the issue i.e the Webservices SAAS connector interprets the special characters differently.

The escape character is “ ` “

The Paging steps that worked is as below

```auto
TERMINATE_IF $response.[‘`@odata.nextLink’]$ == NULL

 $endpoint.fullUrl$ = $response.[‘`@odata.nextLink’]$

```

---

<div class="post-metadata">

**Author:** ![PhilRawlings1](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/philrawlings1/32/37266_2.png) [@PhilRawlings1](https://developer.sailpoint.com/discuss/u/PhilRawlings1)\
**Post date:** [February 20, 2026, 8:44am UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/7 "2026-02-20T08:44:47Z")

</div>

Different machines display characters differently. Namely the ‘ in this instance.  
The above doesn’t work on mine, however this does and is taken directly from VSC:

“paginationSteps”: "TERMINATE\_IF $response.[‘`@odata.nextLink’]$ == NULL\n\n$endpoint.fullUrl$ = $response.['`@odata.nextLink']$"`

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [April 21, 2026, 8:45am UTC](https://developer.sailpoint.com/discuss/t/paging-issue-with-graph-api/196358/8 "2026-04-21T08:45:17Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.