It’s been a fast and furious few months since November when we initially released our API.

In that time we’ve received a lot of feedback from our customers engineers and have added numerous new features over the past months. If you haven’t looked at the API documentation or the Changelog recently, I encourage you to take a look. Additionally, we have an engineers listserve that I (Joshua) will be using in the future when there are significant new features added to the API, so email me if you’d like to be on it.

New API Features:

A new feature, released recently, was Entity Relationships. In addition to allowing multiple entities to share single ACH authorizations, it will be used to greatly reduce the frequency of manual follow-up with investors during the AML process. A good practice to start implementing on your own platforms as soon as possible is to always give a company at least one person as a parent entity.

Downtime and Sandbox:

On Saturday (2/21) morning at 1:00am PST the production system will be brought down temporarily—hopefully no more than about 20 minutes—to do some necessary maintenance and data migration. In the future, through this list, downtime notices will be given much further in advance but should be relatively rare.

The primary purpose for this downtime is related to a major change for developers. Currently, the testing process is a little confusing. There are production API keys and test API keys and there’s test data and production data, but it’s all tied to a single account and in the same environment, which regularly leads to questions like, “I created an offering so why don’t I see it on my dashboard?”

We’ve spun up a new sandbox environment that will be taking the place of using test keys in production.

Uhhh… that’s nice and all, but does this mean my test setup is hosed?

In short, no. All test information from will be copied to the new sandbox environment including all accounts, keys, users, etc. The only code changes that will be necessary will be updating your code to use in place of when calling the API. Your production environment will continue as it has without any changes.

We know that, while minor, this does create some additional work and annoyance for developers. Unfortunately, this change has become necessary for a number of reasons and we believe that in the long run and for new developers this setup will create less confusion, fewer bugs and a better developer experience.

If you have any questions or concerns, feel free to contact me directly!

Joshua Hansen, Chief Engineer