what progress do you have with sending data to Fabman DB (FM) by API?
We’re planning to offer three additional API endpoints (as we briefly discussed during the meeting):
- An endpoint to tell Fabman that a member wants to start a machine.
- If the member is allowed to use the machine, Fabman will start a corresponding activity log record and show the machine as “busy”.
- if the member is not allowed to use the machine at that particular time, it will return a 403 error with a detailed reason why the member isn’t allowed.
- An endpoint to tell Fabman that a machine was stopped. This will close corresponding activity log record and create appropriate charges (if necessary).
- An endpoint to attach arbitrary key-value metadata to any existing log record. You could use this to keep track of details about a 3D print job, machine runtime information, etc.
Do you need anything else?
We’re currently putting the finishing touches on a big, big update. As soon as it’s out the door, we’ll start working on those endpoints – I’ll let you know when it’s available.
Do you have any plans to make some testing DB where it could be possible to test some functions and don’t mess with real data?
You can simply sign up for an additional Fabman account and fill it with test data. Send us a message with your account details if the trial period is not long enough for your tests.
We also have “roadmap” for FM & OP integration and we can share it with you if you are interested.
Yes, please! 
I’m very interested in what you’ve planned. You can either post it in the forum or send us an email, whatever you prefer.