Amazon Hiring API Interaction System
Budget: $250 – $750 CAD
I am looking for a developer to build a system that interacts directly with the Amazon Hiring APIs used on hiring.amazon.ca in order to automatically detect and book available shifts without using a browser or Chrome extension.
Currently the booking process happens through the website UI, but I want a backend system that communicates directly with the API endpoints to make the process significantly faster and more efficient.
Core Requirements
1. Direct API Communication
The system must communicate directly with the Amazon Hiring GraphQL APIs used by the website.
Examples include APIs responsible for:
• User authentication
• Job card search
• Shift availability
• Shift booking
The system must replicate the same request structure used by the website, including:
• headers
• tokens
• cookies
• GraphQL payloads
2. Proper Login & Token Generation (Very Important)
The system must implement the real login process used by the Amazon Hiring platform.
When a user logs into hiring.amazon.ca / hiring.amazon.com, Amazon generates authentication credentials required to access the APIs.
These include:
• Access Token
• Session Cookies
• Authorization Headers
These tokens are mandatory for interacting with the API.
Required Behavior
The system must:
1. Perform the login request programmatically.
2. Capture the authentication token returned after login.
3. Store the token securely.
4. Attach the token to all API requests.
Example headers used by the API may include:
• accesstoken
• authorization
• x-amz-user-agent
• content-type
Token Management
The system should:
• automatically obtain the token after login
• detect when a token expires
• refresh the token automatically if possible
• request login again if the token becomes invalid
Without a valid token, the API will reject requests.
3. Shift Monitoring System
The system should continuously monitor shifts through the shift search API.
Requirements:
• Poll the API continuously
• Detect newly available shifts immediately
The system should process the API response and detect new job cards or shifts as soon as they appear.
4. Automatic Shift Booking
Once a shift is detected, the system should:
1. Immediately send the shift booking request to the API.
2. Confirm if booking was successful.
3. Log the result.
The booking request must replicate the same GraphQL mutation used by the website.
5. Job ID Based Auto Booking
The system must allow manual entry of a Job ID.
Workflow:
1. User enters a Job ID into configuration.
2. The system continuously monitors shift responses.
3. If the API response contains that specific Job ID, the system should immediately attempt to book that shift.
Example configuration:
job_id: ABC12345
auto_book: true
When that job ID appears in the API response, the system should automatically trigger the booking request.
6. Multi-Account Support
The system should support multiple Amazon accounts.
Each account should run independently with its own:
• login session
• tokens
• cookies
• booking requests
7. Proxy Support
Proxy support should be included to:
• rotate IP addresses
• reduce rate limiting
• distribute requests
Supported proxies:
• HTTP
• HTTPS
• authenticated proxies
The system should allow proxy rotation every few seconds.
8. Error Handling
The system must handle:
• expired tokens
• API errors
• network failures
• rate limiting
• booking failures
It should retry automatically when possible.
9. Logging
The system should maintain logs that include:
• shift detection timestamps
• job ID detection
• booking attempts
• successful bookings
• errors
11. Deployment
The system should run on:
• local computer
• VPS server
Other Features
Optional but preferred features include:
• Telegram notification when a shift is booked
• automatic restart if the bot stops
• Stop once shifts is books
• Run 24/7
Currently the booking process happens through the website UI, but I want a backend system that communicates directly with the API endpoints to make the process significantly faster and more efficient.
Core Requirements
1. Direct API Communication
The system must communicate directly with the Amazon Hiring GraphQL APIs used by the website.
Examples include APIs responsible for:
• User authentication
• Job card search
• Shift availability
• Shift booking
The system must replicate the same request structure used by the website, including:
• headers
• tokens
• cookies
• GraphQL payloads
2. Proper Login & Token Generation (Very Important)
The system must implement the real login process used by the Amazon Hiring platform.
When a user logs into hiring.amazon.ca / hiring.amazon.com, Amazon generates authentication credentials required to access the APIs.
These include:
• Access Token
• Session Cookies
• Authorization Headers
These tokens are mandatory for interacting with the API.
Required Behavior
The system must:
1. Perform the login request programmatically.
2. Capture the authentication token returned after login.
3. Store the token securely.
4. Attach the token to all API requests.
Example headers used by the API may include:
• accesstoken
• authorization
• x-amz-user-agent
• content-type
Token Management
The system should:
• automatically obtain the token after login
• detect when a token expires
• refresh the token automatically if possible
• request login again if the token becomes invalid
Without a valid token, the API will reject requests.
3. Shift Monitoring System
The system should continuously monitor shifts through the shift search API.
Requirements:
• Poll the API continuously
• Detect newly available shifts immediately
The system should process the API response and detect new job cards or shifts as soon as they appear.
4. Automatic Shift Booking
Once a shift is detected, the system should:
1. Immediately send the shift booking request to the API.
2. Confirm if booking was successful.
3. Log the result.
The booking request must replicate the same GraphQL mutation used by the website.
5. Job ID Based Auto Booking
The system must allow manual entry of a Job ID.
Workflow:
1. User enters a Job ID into configuration.
2. The system continuously monitors shift responses.
3. If the API response contains that specific Job ID, the system should immediately attempt to book that shift.
Example configuration:
job_id: ABC12345
auto_book: true
When that job ID appears in the API response, the system should automatically trigger the booking request.
6. Multi-Account Support
The system should support multiple Amazon accounts.
Each account should run independently with its own:
• login session
• tokens
• cookies
• booking requests
7. Proxy Support
Proxy support should be included to:
• rotate IP addresses
• reduce rate limiting
• distribute requests
Supported proxies:
• HTTP
• HTTPS
• authenticated proxies
The system should allow proxy rotation every few seconds.
8. Error Handling
The system must handle:
• expired tokens
• API errors
• network failures
• rate limiting
• booking failures
It should retry automatically when possible.
9. Logging
The system should maintain logs that include:
• shift detection timestamps
• job ID detection
• booking attempts
• successful bookings
• errors
11. Deployment
The system should run on:
• local computer
• VPS server
Other Features
Optional but preferred features include:
• Telegram notification when a shift is booked
• automatic restart if the bot stops
• Stop once shifts is books
• Run 24/7