Author Topic: Thoughts on Prosper's New API - Good Ideas, Terrible Execution  (Read 14728 times)

twigster

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
    • Email
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #15 on: December 12, 2015, 03:53:20 AM »
Just starting to look at this.  Just amazing to me that Prosper would make Company Name a required field on the form to sign up for API credentials for individuals.....  Company Name is so obviously a field that does not apply to all individuals requesting access it caused me to write prosper about this.  They say they are going to clarify in the documentation, what they should do it make it a non-required field.  FYI; apparently you can just stick anything in there and it works....

Fred93

  • Hero Member
  • *****
  • Posts: 2180
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #16 on: December 12, 2015, 04:23:22 AM »
How about the fact that it is Prosper's third API, but it is clearly identified as Version 1 ?

twigster

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
    • Email
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #17 on: December 12, 2015, 10:23:58 AM »
Quote
How about the fact that it is Prosper's third API, but it is clearly identified as Version 1 ?
maybe the original versions 1 and 2 were just betas? :o

nonattender

  • Hero Member
  • *****
  • Posts: 715
  • I am not here.
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #18 on: December 12, 2015, 04:50:37 PM »
Just starting to look at this.  Just amazing to me that Prosper would make Company Name a required field on the form to sign up for API credentials for individuals.....  Company Name is so obviously a field that does not apply to all individuals requesting access it caused me to write prosper about this.  They say they are going to clarify in the documentation, what they should do it make it a non-required field.  FYI; apparently you can just stick anything in there and it works....

This is part of their 2015 "Year of the Retail Investor" initiative.
A little nonsense now and then is relished by the wisest men.

TLM

  • Newbie
  • *
  • Posts: 4
    • View Profile
    • Email
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #19 on: December 21, 2015, 01:45:26 PM »
Are any of you able to make all the new APIs work?  I can get a token and search listings, but when I ask for an account balance, it replies
"\n{\"code\":\"SYS0001\",\"message\":\"Application Error\"}"
I've also had trouble with the Orders API.

Thanks!

TLM

eightball

  • Newbie
  • *
  • Posts: 13
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #20 on: December 21, 2015, 02:40:05 PM »
Is it possible you're doing a POST for these instead of a GET?

Rob L

  • Hero Member
  • *****
  • Posts: 2083
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #21 on: December 22, 2015, 09:52:58 AM »
Are any of you able to make all the new APIs work?

I suggest you use the free version of the program SoapUI to debug access methods, etc. There are Linux and Win versions.
SoapUI does work with RESTful API's too.
Once you have everything working with SoapUI then code the methods in the language of your choice.

eightball

  • Newbie
  • *
  • Posts: 13
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #22 on: January 16, 2016, 02:28:31 PM »
I can't use the old APIs at all now (since 18:20ET yesterday). I just get a 401. Tried updating legacy API password with no luck. Is it just me?

BritishJim

  • Newbie
  • *
  • Posts: 17
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #23 on: January 16, 2016, 06:42:41 PM »
I've been surprised by the lack of chatter on this. Starting yesterday afternoon (Friday, Jan 15), I got notice from NSR my Prosper API was not working, of which I had not made any changes.  Later, I received the following e-mail from NSR:

Prosper's API has been down since approximately 7:00 p.m. EST, today (1/15/16). The outage is resulting in investment orders not being accepted when submitted by NSR, as well as an inability to update account balances and portfolio data on NSR Platform. Prosper is aware of the issue and is working diligently to get it corrected. Please let us know if you have any questions.

Since no one was saying anything, I assumed it was an NSR problem but now that eightball has reported using API on his own is there a Prosper problem?


Prescott

  • Full Member
  • ***
  • Posts: 125
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #24 on: January 18, 2016, 01:51:12 AM »
It's a Prosper problem, old api is down for retail accounts, the new api is working though. Anyone using their own code should switch over to the NEW API. My understanding is that it could take a few days to a week to get the old api back up.

If you contact the NSR guys they should be able to help you get your account setup on the new api.

eightball

  • Newbie
  • *
  • Posts: 13
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #25 on: January 18, 2016, 05:17:20 PM »
It's baaaaack.

Prescott

  • Full Member
  • ***
  • Posts: 125
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #26 on: January 19, 2016, 01:53:49 AM »
whew! Time to upgrade though...

Silverstorm

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #27 on: February 06, 2016, 06:05:48 PM »
Finally looking at this due to the recent email that accelerated the timetable...can't believe they did that.

Anyway, I'm not able to get a token in the sandbox, but I can get it in production.  I did change my username along the way, so that might be a problem if they aren't keeping those in sync between sandbox and production.  No idea where the old API password UI is, nor how to see what it is on sandbox.

This is frustrating...if I'd known this was coming, I wouldn't have even signed up.  I'd rather just get notes at LC with slightly less return...

Fred93

  • Hero Member
  • *****
  • Posts: 2180
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #28 on: February 06, 2016, 06:43:28 PM »
I'm not able to get a token in the sandbox, but I can get it in production.  I did change my username along the way, so that might be a problem if they aren't keeping those in sync between sandbox and production.

They don't do a lot of maintenance on the sandbox, so your guess is a good one.  Give 'em a call or send email and they will fix.


Quote
This is frustrating...if I'd known this was coming, I wouldn't have even signed up.  I'd rather just get notes at LC with slightly less return...

IMHO, LC notes & Prosper notes have about same IRR, with LC edging a little higher.  I get higher return numbers displayed on the Prosper web site, but that's just due to their funny way of measuring.  Your mileage will no doubt vary.

eightball

  • Newbie
  • *
  • Posts: 13
    • View Profile
Re: Thoughts on Prosper's New API - Good Ideas, Terrible Execution
« Reply #29 on: February 07, 2016, 03:18:21 PM »
Is it unreasonable to expect server-side safeguards like these to protect those who make or use 3rd-party tools?

- account settings for max individual bid amount and daily total
- a setting to prevent buying multiple notes in the same loan
- an ability to withdraw a bid placed within the last N minutes