com.Posting/
Compost Collectors provides a set of standardized services, and invoices could be generated for users in any location, whether an office or a field agent. To facilitate the flexibility of invoice creation, the Compost Collectors API is designed to provide users a remote information source designed to interface with a local database or other storage method to generate user-specific invoices, stored locally but configured using standardized business data.
- servicesV1
- Access all services
- servicesV2/{id}
- Access services by id
- servicesV3/{name}/{description}
- Create new service
- materialsV1
- Access all materials
- materialsV2/{id}
- Access materials by id
- materialsV3/{name}/{comments}
- Create new material
- periodsV1
- Access all periods
- periodsV2/{id}
- Access periods by id
- periodsV3/{frequency}/{time_unit}
- Create new period
- pricesV1
- Access all prices
- pricesV2/{id}
- Access prices by id
- pricesV3/{cost}/{unit}
- Create new price
GET
POST
Plain text
HTML
JSON
Abigail Genz - Team coordinator, leader and task delegator.
Tim Mirkes - The coder in the weeds. Not to be confused with the catcher in the rye.
Nate Peck - Creative team collaborator and descriptive writer.
Develop a functional API to provide configuration information for use in the construction of service invoices for the Compost Collectors business.
- Communication
- Active Listening
- Github
- IntelliJ
- Java
- SQL
- Database Design
- Organization
- Entrepreneurship
- Critical thinking
Abigail Genz: No IT professional experience so far, but has skills like time management, organization and problem-solving skills from previous customer service jobs.
Tim Mirkes: I worked for almost 10 years with a GIS/spatial data company, picking up SQL and a touch of Python along the way, and a vested interest in the structure and detail of software design.
Nate Peck: Customer service technical support, QA automated testing, agile-ish methodologies.