# IDN: API offset: "Specified offset is invalid."

**URL:** <https://developer.sailpoint.com/discuss/t/idn-api-offset-specified-offset-is-invalid/22532>\
**Category:** Bugs\
**Tags:** apis, identity-security-cloud\
**Created:** [December 12, 2023, 2:15pm UTC](https://developer.sailpoint.com/discuss/t/idn-api-offset-specified-offset-is-invalid/22532 "2023-12-12T14:15:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamian](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@adamian](https://developer.sailpoint.com/discuss/u/adamian)\
**Post date:** [December 12, 2023, 2:15pm UTC](https://developer.sailpoint.com/discuss/t/idn-api-offset-specified-offset-is-invalid/22532/1 "2023-12-12T14:15:50Z")

</div>

Dear SailPoint IDN Team,

There are currently two behaviors when using an offset greater than the total number of records available:

- for /beta/transforms you get the error:

```json
{
    "detailMessage": "Specified offset is invalid.",
    "stackTrace": [],
    "suppressedExceptions": []
}

```

- for all (?) others (e.g. access-profiles, identity-profiles, roles) you get an empty JSON list (`[]`).

It would be nice to have a consistent behavior (either return an empty list if offset is out of range or force API clients to use the `count=true` query parameter to find out the total number of entries).

Best regards,  
Andrei

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [December 12, 2023, 2:20pm UTC](https://developer.sailpoint.com/discuss/t/idn-api-offset-specified-offset-is-invalid/22532/2 "2023-12-12T14:20:09Z")

</div>

is this an issue with /v3/transforms as well?

---

<div class="post-metadata">

**Author:** ![adamian](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@adamian](https://developer.sailpoint.com/discuss/u/adamian)\
**Post date:** [December 12, 2023, 2:33pm UTC](https://developer.sailpoint.com/discuss/t/idn-api-offset-specified-offset-is-invalid/22532/3 "2023-12-12T14:33:27Z")

</div>

> [@colin\_mckibben](#):
>
> is this an issue with /v3/transforms as well?

Yes.

* * *

And another discrepancy between the different APIs: most APIs accept beside the official `count=true` an insensitive case value (`True`, `TRUE`), but not `/segments` :).  
For /{beta|v3}/segments the header `X-Total-Count` will not be set when `count=True`.