API
| Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate | E |
| 272 Capp St. | Layout | Exits | Bathrooms | Network | Audio | AV | Construction | Electrical | Storage STREET | Patio | Parking | Fence | Access | Gate | Payphone | Doorbell | Back patio | Roof | Neighbors |
E |
| Storage | Do not hack | Bins | Lockers | Hackitorium Shelves | Electronics Shelves | Music Shelves | Project Shelves | SCP-7R45H | E |
| Operations (c) | Safety | Secretariat | Board | Housekeeping | Access | SecWG | Finances | Fundraising | Utilities | Mailbox | Bylaws | Roles | V · T · E |
| Working Groups (c) | WikiWG: Documentation | SafeSpaceWG | SecWG: Access | FinanceWG | FacilitiesWG | V · T · E |
Noisebridge's general use API for accessing space status, membership, and other fun services.
Maintained by the ApiWG.
See also Historic/API
Design Goals[edit | edit source]
If we were to make something like a "Noisebridge web portal" what are things folks would want from it?
Actions I would like to automate:
- Cross post event announcements in different platforms (server-feedback / Noisebridge API)
- Opening the door for folks remotely
- Report expense
- Send announcement to the physical space via Mary
- Reserve equipment
- Space open sign
- Etc
Status[edit | edit source]
Members[edit | edit source]
- chatbot (discord) -- suggester
- (Mcint curious from afar)
- Justinmorrison
Help wanted[edit | edit source]
Easy ways to achieve any parts of these goals. Help coding. Discuss on discord. Especially in server-feedback / Noisebridge API