Rubbish Love Rubbish API
★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsnone3 EndpointsREST
For Agents
Programmatically get all rubbish submissions, get all runs. Covers 3 operations.
Use for: I need to all rubbish submissions, I want to all runs, Search for movement information about a specific run, List all records from Rubbish API
Not supported: Does not handle payments, communications, or crm — use for hr and recruiting only.
Rubbish provides APIs for accessing litter and cleanup data. Retrieve submissions, runs, and run movement information collected through the Rubbish platform. The API exposes 3 endpoints.
Install Jentic One Beta
Connect the Rubbish API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rubbish API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Rubbish API.
Get all rubbish submissions
Manage hr recruiting data programmatically
Integrate Rubbish API into automated workflows
Query and filter Rubbish API records by parameters
Monitor Rubbish API operational status and events
Use Cases
Patterns agents use Rubbish API for, with concrete tasks.
★ HR and Recruiting Operations
Use the Rubbish API to perform hr recruiting operations programmatically. The API provides 3 endpoints covering core functionality including get all rubbish submissions, get all runs, get movement information about a specific run.
Call GET /api/submissions to get all rubbish submissions
Automated Runs Management
Automate runs operations by combining multiple Rubbish API endpoints. Agents can get all runs and then get movement information about a specific run in a single workflow.
Call GET /api/runs to get all runs, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Rubbish API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'get all rubbish submissions', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — rubbish provides apis for accessing litter and cleanup data.
METHOD
PATH
DESCRIPTION
GET
/api/submissions
Get all rubbish submissions
GET
/api/runs
Get all runs
GET
/api/runs/{runId}
Get movement information about a specific run
GET
/api/submissions
Get all rubbish submissions
GET
/api/runs
Get all runs
GET
/api/runs/{runId}
Get movement information about a specific run
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Rubbish API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get all rubbish submissions') and Jentic returns the matching Rubbish API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Rubbish API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Rubbish API through Jentic.
What authentication does the Rubbish API use?
The Rubbish API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I get all rubbish submissions with the Rubbish API?
Yes. Use the GET /api/submissions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Rubbish API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get all rubbish submissions through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get all rubbish submissions'. Jentic returns the matching Rubbish API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Rubbish API have?
The Rubbish API exposes 3 endpoints covering runs, submissions operations.
GET STARTED