# Deal splits - Internal server error

**URL:** <https://community.hubspot.com/t/deal-splits-internal-server-error/113479>\
**Category:** APIs & Integrations\
**Tags:** object\
**Created:** [August 1, 2024, 2:09pm UTC](https://community.hubspot.com/t/deal-splits-internal-server-error/113479 "2024-08-01T14:09:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GBoivin](https://avatars.discourse-cdn.com/v4/letter/g/ebca7d/32.png) [@GBoivin](https://community.hubspot.com/u/GBoivin)\
**Post date:** [August 1, 2024, 2:09pm UTC](https://community.hubspot.com/t/deal-splits-internal-server-error/113479/1 "2024-08-01T14:09:27Z")

</div>

Hi,

I am trying to retrieve deal splits from our app client. For some reason, it works perfectly for some deals but results in an internal error for others.

For example:

```lia-code-sample
curl --request POST \
 --url https://api.hubapi.com/crm/v3/objects/deals/splits/batch/read \
 --header 'authorization: Bearer MYBEARER' \
 --header 'content-type: application/json' \
 --data '{
 "inputs": [
 {
 "id": "2947161292"
 }
 ]
}'

```

work perfectly !!

```lia-code-sample
curl --request POST \
 --url https://api.hubapi.com/crm/v3/objects/deals/splits/batch/read \
 --header 'authorization: Bearer MYBEARER' \
 --header 'content-type: application/json' \
 --data '{
 "inputs": [
 {
 "id": "17555105680"
 }
 ]
}'

```

Give

```lia-code-sample
{
 "status": "error",
 "message": "internal error",
 "correlationId": "3b35326e-a077-4078-8d33-7290506fe8f1"
}

```

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [August 2, 2024, 4:34pm UTC](https://community.hubspot.com/t/deal-splits-internal-server-error/113479/2 "2024-08-02T16:34:55Z")

</div>

Hey, @GBoivin 👋 I set up two deal splits and tested this in Postman, but I cannot reproduce the error. Did you get it worked out?

If not:

- is it only happening with one deal?
- is the error consistent?
- can you share any additional details?

Thank you! — Jaycee