Python API Integration Developer Needed – Amazon, MercadoLibre, Vinted, Instagram, Facebook & TikTok

# Python API Integration Developer Needed – Amazon, MercadoLibre, Vinted, Instagram, Facebook and TikTok ## Project Overview I am looking for an experienced Python developer to build a modular, maintainable data-integration system connecting to six e-commerce and social platforms: 1. Amazon 2. MercadoLibre 3. Vinted 4. Instagram 5. Facebook 6. TikTok This project must use only official APIs, authorized integrations, client-authorized account data, licensed data sources, or other access methods expressly permitted by the relevant platform. Compliance with each platform's Terms of Service, API terms, privacy requirements and rate limits is mandatory. This project does not require and must not include unauthorized web scraping, bypassing access restrictions, CAPTCHA circumvention, rate-limit circumvention, private data collection or any other method prohibited by the relevant platform. --- # Main Objective The objective is to build one Python-based framework containing separate connectors for each supported platform. The system should: * Connect to permitted platform APIs * Retrieve the data available under the authorized API scopes * Normalize the returned data * Export data to JSON and CSV * Handle multiple countries or locales where supported * Provide clear logs and error handling * Be easy to configure and maintain * Include offline test fixtures * Include automated tests * Include full source code and documentation I want a maintainable system rather than six unrelated scripts. --- # Platforms The intended integrations are: ## E-Commerce * Amazon * MercadoLibre * Vinted ## Social Media * Instagram * Facebook * TikTok The developer must first confirm which official or authorized API is appropriate for each platform and what data is available through that API. If a requested data field is not available through an authorized method, this must be clearly documented. Do not replace an unavailable API feature with unauthorized scraping or circumvention. --- # 1. Compliance and API Feasibility Review Before completing the integrations, I want the developer to provide a short feasibility matrix covering all six platforms. For each platform, state: * Official or authorized API being used * Authentication method * Required permissions or account type * Available data fields * Country or locale support * API rate limits where applicable * Any approval requirements * Any important API restrictions * Any requested information that cannot legally or technically be obtained through the permitted API If API approval or a particular business account is required, this should be identified early. Where I have the necessary account or API access, I will provide the required credentials securely after the contract begins. --- # 2. Modular Architecture Each platform should have its own connector so a change to one integration does not break the others. A structure similar to this would be suitable: ```text project/ connectors/ amazon/ mercadolibre/ vinted/ instagram/ facebook/ tiktok/ config/ mappings/ exporters/ fixtures/ logs/ tests/ .env.example requirements.txt README.md main.py ``` Equivalent professional architecture is welcome. --- # 3. Official and Authorized Access Only All integrations must use permitted methods. Examples include: * Official REST APIs * Official SDKs * OAuth-authorized APIs * Client-authorized account APIs * Platform-provided business APIs * Client-provided exports * Properly licensed data providers where permitted The application must respect: * API authentication requirements * Permission scopes * Platform rate limits * Privacy requirements * Data retention requirements where applicable * Platform developer policies The system must not attempt to defeat or bypass restrictions imposed by an API or platform. --- # 4. Data Fields Where the relevant authorized API makes the information available, I would like the normalized output to support fields such as: * Platform * Country or locale * Item, product or post ID * Product or content title * Description or caption * Price * Currency * Seller or authorized account name * Product or media URL * Image or media reference * Availability or status * Publication timestamp * Engagement metrics where permitted * Canonical platform URL * API retrieval timestamp Not every platform will provide every field. The developer should map the available fields into one consistent output structure and clearly identify unsupported fields. --- # 5. Country and Locale Support The architecture should support multiple countries or marketplaces without duplicating the entire application. For example, where the relevant API supports them, Amazon marketplaces may include different countries and regions. MercadoLibre may also require different marketplace or country identifiers. Locale configuration should handle items such as: * Marketplace ID * Country * Currency * Language * API endpoint where applicable * Platform-specific settings If a certain platform requires separate API approval for different regions, please document this. --- # 6. Configuration-Driven Field Mapping Where practical, platform response mappings should be separated from the main business logic. For example: ```text Amazon Product ID: API response field Title: API response field Price: API response field Currency: API response field ``` If an API response schema changes, I would prefer to update mappings or configuration without rewriting large parts of the application. --- # 7. API Error Handling The system should clearly differentiate between different types of API problems. For example: ```text AMAZON API ERROR Status: 401 Reason: Authentication failure Action: Request rejected ``` ```text MERCADOLIBRE API ERROR Status: 429 Reason: API rate limit reached Action: Respect retry instructions and pause requests ``` ```text TIKTOK VALIDATION ERROR Status: 200 Mandatory field missing: post ID Action: Response saved for debugging ``` Errors should never be silently ignored. --- # 8. Mandatory Field Validation A successful API response does not automatically mean the returned record is valid. Each connector should define mandatory fields. If an API returns a successful response but important expected fields are unexpectedly missing, the system should: * Reject or quarantine that record * Log the issue * Identify which fields are missing * Save the raw API response for debugging * Continue processing where appropriate --- # 9. Raw Response Debugging When an authorized API returns a successful response but mandatory fields cannot be mapped correctly, the raw API response should be saved locally for troubleshooting. Example: ```text debug/ amazon/ response_error_001.json mercadolibre/ response_error_002.json ``` The log should identify: ```text Platform: Amazon API Status: Success Missing field: Price Raw response saved: debug/amazon/response_error_001.json Result: Record rejected Suspected cause: API schema or mapping issue ``` Sensitive information must not be written to logs unnecessarily. --- # 10. Offline Test Fixtures Offline testing is required. Please include saved, sanitized API response samples so mappings and parsers can be tested without making repeated live API requests. Example: ```text fixtures/ amazon/ product_standard.json mercadolibre/ product_standard.json vinted/ item_standard.json instagram/ media_standard.json facebook/ content_standard.json tiktok/ content_standard.json ``` Fixtures must not contain credentials, tokens or private personal information. --- # 11. Automated Testing Basic automated tests should be included. Tests should cover: * Loading saved API fixtures * Mapping platform-specific responses * Required field validation * Missing field handling * JSON export * CSV export * API error classification * Raw response debug saving * Locale configuration * Authentication configuration without exposing credentials Pytest or another suitable Python testing framework can be used. --- # 12. Rate Limit Handling The system must respect the official rate limits of each platform. Where applicable it should support: * Retry-after instructions * Exponential backoff * Request queues * Safe retry logic * Rate-limit logging The system must not attempt to evade rate limits by rotating accounts, IP addresses or otherwise circumventing platform controls. --- # 13. Authentication Credentials and access tokens must not be hard-coded. Use environment variables or another secure configuration approach. Example configuration values might include: ```text AMAZON_CLIENT_ID= AMAZON_CLIENT_SECRET= MERCADOLIBRE_CLIENT_ID= MERCADOLIBRE_CLIENT_SECRET= META_ACCESS_TOKEN= TIKTOK_CLIENT_KEY= TIKTOK_CLIENT_SECRET= OUTPUT_FORMAT=json LOG_LEVEL=INFO ``` The actual configuration will depend on the official APIs used. An .env.example file should be supplied without real credentials. --- # 14. Token Management Where OAuth is required, the developer should implement appropriate token handling. This may include: * OAuth authorization * Access token storage * Refresh tokens where supported * Token expiration handling * Authentication errors * Reauthorization instructions Credentials must be handled securely. --- # 15. Output Formats At minimum, the system should support: * JSON * CSV The exported data should use a normalized structure even though each platform's API returns different formats. --- # 16. Command-Line Operation I would like a simple method of running the integrations locally. For example: ```text python main.py --platform amazon python main.py --platform mercadolibre python main.py --platform tiktok ``` The exact command structure is flexible provided it is clearly documented and easy to use. --- # 17. Local Installation The complete project must be easy to install locally. Please provide: * requirements.txt or equivalent dependency configuration * .env.example * README.md * Full source code * Setup instructions Typical installation should be straightforward. Example: ```text python -m venv venv pip install -r requirements.txt python main.py --platform amazon ``` --- # 18. Logging Logs should include useful information such as: * Platform * Timestamp * API operation * Response status * Authentication error * Rate-limit error * Validation error * Missing fields * Retry action * Debug response location Sensitive credentials, tokens and unnecessary personal data must not appear in logs. --- # 19. Documentation A complete README is required. It should explain: * Installation * Python requirements * Environment variables * API credentials required * How authorization works * How to run each connector * Supported data fields * Unsupported data fields * Supported countries and marketplaces * Output formats * Testing * Offline fixtures * Logging * Common API errors * Troubleshooting * How field mappings can be updated * Any API approval requirements I want to be able to operate and maintain the application locally after delivery. --- # 20. Full Source Code Full Python source code must be delivered. The code should be: * Modular * Readable * Well organised * Documented * Maintainable * Reasonably commented No compiled-only application. --- # 21. Initial Bug-Fix Support I need a reasonable testing period after delivery. Please include post-delivery support for genuine implementation problems discovered during initial testing, including: * Authentication configuration issues * Incorrect API mappings * Code errors * Missing dependencies * Broken local setup * Incorrect output * Documentation errors * API response handling bugs Please state how many days of initial bug-fix support are included in your price. Future platform API changes after the project has been successfully accepted can be handled as separate maintenance work. --- # Important Compliance Requirement This project must remain compliant with the Terms of Service and developer policies of Amazon, MercadoLibre, Vinted, Meta, TikTok and any other service involved. Do not propose: * Unauthorized scraping * CAPTCHA bypass * Access-control bypass * Rate-limit circumvention * Account rotation to avoid platform restrictions * Collection of data that the account is not authorized to access * Collection of private or sensitive personal information without appropriate authorization * Reverse engineering prohibited by the relevant platform * Any workaround that violates a platform's Terms of Service If an official API does not provide a requested feature, please document the limitation and suggest only a compliant alternative. --- # Final Deliverables The final project should include: 1. Amazon authorized API connector 2. MercadoLibre authorized API connector 3. Vinted authorized integration where eligible and available 4. Instagram authorized API connector 5. Facebook authorized API connector 6. TikTok authorized API connector 7. Shared Python framework 8. Country and locale configuration 9. Normalized data model 10. JSON export 11. CSV export 12. API error handling 13. Rate-limit handling 14. Mandatory field validation 15. Raw JSON debug responses 16. Sanitized offline test fixtures 17. Automated tests 18. Secure environment configuration 19. Full README 20. Full Python source code 21. Initial bug-fix support If a platform cannot be integrated because the necessary official API access is unavailable to my account, clearly document this rather than implementing a prohibited workaround. --- # Skills Required Strong experience with several of the following is required: * Python * REST APIs * OAuth 2.0 * API Integration * JSON * CSV * Data normalization * Pytest * Error handling * Logging * Environment variables * API authentication * Rate-limit handling * Git * Amazon APIs * MercadoLibre API * Meta APIs * TikTok APIs * E-commerce integrations * Social media API integrations --- # Questions to Answer in Your Proposal Please answer the following rather than sending a generic proposal. 1. Which official or authorized API would you use for each of the six platforms? 2. What account permissions, developer approvals or credentials would I need for each platform? 3. Are there any requested platforms or data types that cannot currently be accessed through an official or otherwise authorized API? 4. How would you design one common data model across six different APIs? 5. How would you handle OAuth tokens and token refresh securely? 6. How would you handle official API rate limits and 429 responses? 7. Will sanitized offline JSON fixtures and automated tests be included? 8. Will the system save raw API responses for debugging when a response succeeds but mandatory fields cannot be mapped? 9. How many days of post-delivery bug-fix support will you include? 10. What is your realistic delivery time for the complete project? 11. Please briefly describe similar API integration work you have completed previously. # Fixed Price Please review the full scope before applying. What is your final fixed price in USD to complete this entire project? Please provide: 1. Your total fixed price 2. Your expected delivery time 3. Your included post-delivery bug-fix period 4. Any API access or paid third-party services that would need to be supplied separately by me Please do not submit a placeholder price and substantially change it later without a genuine change in scope.