API rate limit / issues from hitting /token endpoint too many times?


On Saturday my team was testing transfer creation in the sandbox and were receiving apparent errors from the /token endpoint.

We use the Golang package https://godoc.org/github.com/kolanos/dwolla-v2-go, so we don’t have quite the visibility that we want into the exact response, but from what we understand the returned json was not able to be parsed correctly and the status code was 403.

Looking at the Dwolla status page, it doesn’t look like there were any issues or outages during that time. Thinking closely about our architecture, I’m curious if there would be any issues on your end from hitting the /token endpoint a bunch of times almost simultaneously? We use AWS lambda, and when we receive X number of inbound webhook requests, up to X number of lambda instances will spin up to process those webhooks. All of the failures I see in our logs are related to the /token endpoint.


Hi @bzswords, this could be the cause of the error you received when hitting the token endpoint. There may be some protection on that endpoint which limits the number of requests within a short timespan. It sounds like you may be calling to retrieve an access token on each request? Access tokens should be valid for up to an hour after being issued. I’d likely recommend using some type of data store for your secure credentials to where you’d call once/twice per hour and then use that token for all calls to the Dwolla API. I’d be happy to dig into your API requests further, feel free to DM me with your app name and I can take a closer look.

@spencer Is (dwolla package - github.com/kolanos/dwolla-v2-go - Go Packages) getting maintained ? it’s been 2 years since last update, just curious to know before integration.

Hi @Alok_Verma , Unfortunately that client library isn’t officially maintained by the Dwolla team, therefore we don’t have much control over development and maintenance. That being said, we do have other clients of ours using it in production. We would also be happy to connect with the maintainer if there are any recommended changes to implement based on API updates and additional feedback from the community. Hopefully this information helps. Please let us know if you identify any issues or concerns with the library that we could help out with!

@spencer Where i can find the other client library for golang?

Hi @Alok_Verma , I believe that is the only golang client library for the Dwolla API. Have you tried it out and do you see any issues with design/usage?

hi @spencer , I have to create funding source using plaid processor token, I’m bit confused if it possible with that library.

Hi @Alok_Verma – I haven’t tested it myself, but from the source code, it appears that plaidToken is supported by the library.

Hopefully based on the raw request body below you are able to construct the Go code accordingly. We require the name and plaidToken key:value pairs as parameters in the request body:

POST https://api-sandbox.dwolla.com/customers/AB443D36-3757-44C1-A1B4-29727FB3111C/funding-sources
Content-Type: application/vnd.dwolla.v1.hal+json
Accept: application/vnd.dwolla.v1.hal+json
Authorization: Bearer pBA9fVDBEyYZCEsLf/wKehyh1RTpzjUj5KzIRfDi0wKTii7DqY

  "plaidToken": "processor-sandbox-161c86dd-d470-47e9-a741-d381c2b2cb6f",
  "name": "Jane Doe’s Checking"