# V2 LeadSource Endpoint is down

**URL:** <https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021>\
**Category:** API Q&A\
**Tags:** leadsource\
**Created:** [April 22, 2026, 3:31pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021 "2026-04-22T15:31:08Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christian\_Wiles](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/christian_wiles/32/15144_2.png) [@Christian\_Wiles](https://integration.keap.com/u/Christian_Wiles)\
**Post date:** [April 22, 2026, 3:31pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/1 "2026-04-22T15:31:08Z")

</div>

```auto
{
  "code": 500,
  "message": "There was a problem loading these Lead Source records",
  "status": "Internal Server Error",
  "details": [
    {
      "domain": "leadsource",
      "resource": "GET /rest/v2/leadSources"
    }
  ]
}

```

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [April 22, 2026, 3:38pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/2 "2026-04-22T15:38:41Z")

</div>

Hi Christian, thanks for flagging this.

I just tested it on my end and it’s working as expected. When you have a moment, could you share the details of the request you’re making (or the curl you’re using)? That would help us compare and narrow down what might be happening here.

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [April 22, 2026, 5:41pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/3 "2026-04-22T17:41:32Z")

</div>

@Christian_Wiles - If the Filter parameter is not correctly set, you will get those type of errors. Make sure the equal signs are being formatted correctly.

---

<div class="post-metadata">

**Author:** ![Christian\_Wiles](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/christian_wiles/32/15144_2.png) [@Christian\_Wiles](https://integration.keap.com/u/Christian_Wiles)\
**Post date:** [April 24, 2026, 11:04am UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/4 "2026-04-24T11:04:57Z")

</div>

Omar, respectfully, we are using the GET method in the URL and providing only the access token. This is working on all of our tables in bulk where v2 has a legitimate GET endpoint, with the exception of lead sources and payments. Here are the two URLs that we are having a problem with.

If the v2 method is get and it is a list, then we should be able to return the entire list, correct?

```auto
https://api.infusionsoft.com/crm/rest/v2/leadSources?access_token=123456789asdfghjk

```

```auto
https://api.infusionsoft.com/crm/rest/v2/sales/payments?access_token=123456789asdfghjk

Here are the error messages:

{
  "code": 500,
  "message": "Unknown error",
  "status": "Internal Server Error",
  "details": [
    {
      "domain": "sales",
      "resource": "GET /rest/v2/sales/payments"
    }
  ]
}

```

[6:58 AM]

```auto
{
  "code": 500,
  "message": "There was a problem loading these Lead Source records",
  "status": "Internal Server Error",
  "details": [
    {
      "domain": "leadsource",
      "resource": "GET /rest/v2/leadSources"
    }
  ]
}

```

```auto
{
  "code": 500,
  "message": "Unknown error",
  "status": "Internal Server Error",
  "details": [
    {
      "domain": "sales",
      "resource": "GET /rest/v2/sales/payments"
    }
  ]
}

```

Success with this as an example

```auto
https://api.infusionsoft.com/crm/rest/v2/products?access_token=123456789asdfghjk

```

Success:

{  
“products”: [  
{  
“id”: “1733”,  
“name”: “Deluxe Thanks Again No Feedback”,  
“price”: {  
“amount”: 0,  
“currency\_code”: “USD”,  
“formatted\_amount”: “$0.00”  
},  
“active”: true,  
“shippable”: false,  
“weight”: 0,  
“taxable”: false,  
“categories”: [],  
“options”: [],  
“inventory”: {  
“inventory\_limit”: 0,  
“out\_of\_stock\_enabled”: false,  
“email\_for\_inventory\_notifications”: null  
},  
“subscription\_only”: false,  
“storefront\_hidden”: false,  
“country\_taxable”: false,  
“state\_taxable”: false,  
“city\_taxable”: false,  
“subscription\_plans”: [  
{  
“id”: “1137”,  
“active”: true,  
“prorate”: false,  
“billing\_cycle”: “MONTHLY”,  
“billing\_frequency”: 1,  
“number\_of\_cycles”: 0,  
“plan\_price”: {  
“amount”: 0,  
“currency\_code”: “USD”,  
“formatted\_amount”: “$0.00”  
},  
“order\_index”: 1  
}  
],  
“is\_package”: false,  
“needs\_digital\_delivery”: false,  
“has\_legacy\_image”: false,  
“create\_time”: “2026-04-14T16:50:20Z”,  
“update\_time”: “2026-04-14T16:51:22Z”

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [April 24, 2026, 12:14pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/5 "2026-04-24T12:14:24Z")

</div>

@Christian_Wiles - To future proof your code, I recommend that you put the Access Token into the Header of the cURL call.

```auto
Authorization: Bearer 123456789asdfghjk

```

Not sure if this is causing you the problem with the “?access\_token” URL parameter.

@OmarAlmonte can verify things on his end.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [April 24, 2026, 12:14pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/6 "2026-04-24T12:14:35Z")

</div>

@Christian_Wiles Would you mind sending me a direct message with the app ID(s) you’re using when encountering these errors? That will allow us to take a closer look and investigate more thoroughly.

As a quick note, the access token should be passed as a Bearer token in the Authorization header rather than in the query parameters as @Pav mentioned. However, this would not be the cause of the errors you’re seeing, so there is likely something else contributing to the issue.

Thanks,  
Omar

---

<div class="post-metadata">

**Author:** ![Christian\_Wiles](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/christian_wiles/32/15144_2.png) [@Christian\_Wiles](https://integration.keap.com/u/Christian_Wiles)\
**Post date:** [April 27, 2026, 10:39am UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/7 "2026-04-27T10:39:46Z")

</div>

We have solved this problem.

It was not a problem with the endpoint. It was actually a problem where the leadsource did not have an active or inactive status setting.

This may have been because we had created a lead source via API and not set those fields when we created the lead source.

We can close this issue.

Thank you for the feedback @Pav @OmarAlmonte !

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [April 27, 2026, 12:29pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/8 "2026-04-27T12:29:10Z")

</div>

Thanks for the update, Christian. Glad to hear you were able to resolve it. We’ll still track this internally, as there’s an opportunity for us to improve the error handling in that scenario.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [August 11, 2026, 1:56pm UTC](https://integration.keap.com/t/v2-leadsource-endpoint-is-down/94021/9 "2026-08-11T13:56:31Z")

</div>

Hi @Christian_Wiles, we released improvements for error handling in this endpoint, thanks for the feedback!