Boom and Bucket - Integration API

Number of APIs: 13

The Boom and Bucket integration API provides endpoints for onboarding machines and for retrieving summarized valuation insights.

Authorization

The Boom and Bucket integration API uses X-API-Key query parameter or as a header to authenticate requests. This parameter needs to be provided with every api request.

For example

https://api.boomandbucket.com/marketplaceservice/marketplace/fleet-management-integration/onboard-equipment?X-API-KEY=

API Rate Limiting Policy

Our API is designed to provide a consistent and reliable service to all users. To ensure this, we have implemented a rate limiting policy that allows a maximum of 10 requests per second.

Rate Limits

The rate limit for our API is 10 requests per second (RPS). This rate limit applies per API key, not per user or application.

How It Works

Every API request you make subtracts from your remaining request quota. If you exceed the limit of 10 requests per second, you will receive a 429 Too Many Requests HTTP status code.

Response Headers (Coming soon)

Every API response includes three headers to help you understand your current rate limit status:

X-RateLimit-Limit: The maximum number of requests you can make per second.
X-RateLimit-Remaining: The number of requests left for the current window.
X-RateLimit-Reset: The time when the rate limit will reset, in UTC epoch seconds.

Exceeding The Rate Limit

When you exceed the rate limit, the API responds with HTTP status 429 Too Many Requests. You should design your application to handle this possibility and implement a backoff strategy. For example, you could wait until the rate limit resets (as specified in the X-RateLimit-Reset header) before making additional requests.

The information provided by this API should be used in conjunction with professional advice and market knowledge to make informed decisions about equipment valuation.