← Back to EcomCentral
HOOD.DE MARKETPLACE API

Hood.de Setup Guide

Connect your Hood.de seller account to EcomCentral using your Hood API key from the Verkäufer-Center.

About Hood.de

Hood.de is one of Germany's largest online marketplaces, serving millions of buyers and sellers since 2000. It operates as a fixed-price and auction platform, popular across the DACH region (Germany, Austria, Switzerland) for new and used goods in categories ranging from electronics to fashion and collectibles.

ℹ️ EcomCentral connects to the Hood.de REST API v1 at https://www.hood.de/api/v1 using your seller API key. All requests use the X-Api-Key header for authentication.
⚠️ MEDIUM confidence: The exact endpoint structure and field names are inferred from German marketplace REST patterns. If you encounter unexpected errors, verify against the official Hood.de API documentation in your Verkäufer-Center.

Prerequisites

How to Get Your API Key

  1. Log in to your Hood.de Verkäufer-Center
  2. Navigate to Mein Konto → API-Zugangsdaten (Account → API Settings)
  3. If API access is not yet enabled, click API-Zugang beantragen (Request API Access) and follow the on-screen instructions
  4. Once enabled, copy your API-Schlüssel (API Key) — this is a long alphanumeric token
  5. In EcomCentral, add a new Hood.de connection and paste the key into the api_key field
  6. Click ⚡ Test to verify the connection
✅ Keep your API key confidential. If it is compromised, regenerate it from the same Verkäufer-Center screen and update the EcomCentral connection.

Credentials Reference

KeyRequiredDescriptionExample
api_key Required Hood.de seller API key from Verkäufer-Center → Mein Konto → API-Zugangsdaten. Sent as X-Api-Key header on every request. hd_live_a1b2c3d4…
✅ Alternative key names accepted: apiKey or token — EcomCentral checks all three automatically.
ℹ️ Note: Hood.de uses the product EAN (European Article Number) as the primary SKU identifier for listings. When updating stock, the product ID (not the EAN) is used as the product reference in API calls.

API Endpoints Used

OperationMethodEndpoint
Test connectionGET/orders/?page_size=1
List ordersGET/orders/?page=P&page_size=N
Order detailGET/orders/{id}/
Add trackingPATCH/orders/{id}/ with { "tracking_number":"…", "carrier":"…", "status":"shipped" }
List productsGET/products/?page=P&page_size=N
Product detailGET/products/{id}/
Update stockPATCH/products/{id}/ with { "quantity": N }
ℹ️ All requests carry the X-Api-Key: {your_key} header. List endpoints return { count:N, results:[…] }. Single-item endpoints return the object directly without an envelope wrapper. Pagination uses ?page={n}&page_size={n} query parameters.

Order Statuses

Hood.de uses English status strings in its API. EcomCentral colour-codes them for at-a-glance clarity.

StatusGerman equivalentBadge colour
paid Bezahlt Green
shipped Versendet Green
completed / delivered / closed Abgeschlossen / Geliefert Green
pending Ausstehend Blue
new / processing Neu / In Bearbeitung Blue
awaiting_payment / awaiting_shipment Warte auf Zahlung / Versand Blue
on_hold / partially_shipped / awaiting_pickup Wartend / Teilweise versendet Amber
cancelled / refunded / returned / failed Storniert / Erstattet / Retour Red

Supported Features

FeatureSupportedNotes
View orders (paginated)Order ID, reference number, date, status, total + currency
View order detailBuyer info, billing & shipping addresses, line items with EAN, current tracking
Add tracking numberSets tracking_number, carrier, and status via PATCH /orders/{id}/
View products (paginated)Product ID, EAN (as SKU), title, price, stock quantity
View product detailFull product with description (HTML stripped), category, weight, first image
Update stock quantityBy product_id via PATCH /products/{id}/ with quantity
Test connectionHits GET /orders/?page_size=1 — success confirms API key is valid

Troubleshooting

401 Unauthorized

The API key is wrong or has been revoked. Return to Verkäufer-Center → Mein Konto → API-Zugangsdaten and verify or regenerate your key. Make sure there are no leading/trailing spaces in the pasted value.

403 Forbidden

Your seller account has not been granted API access. In the Verkäufer-Center, navigate to API-Zugangsdaten and click API-Zugang beantragen (Request API Access). Hood.de may require account verification before enabling API access.

404 Not Found

The order or product ID does not exist in your Hood.de account, or the API path has changed. Verify the ID in your Hood.de Verkäufer-Center and check whether a Hood API update has altered the endpoint structure.

Rate Limiting

Hood.de may throttle requests if too many are made in a short window. EcomCentral paginates list calls (20 results per page) to stay within typical rate limits. If you hit a 429 Too Many Requests response, wait a minute before retrying. Avoid running multiple simultaneous connections to the same Hood.de account.

Unexpected Field Names or Missing Data

The Hood.de API field mapping in EcomCentral is built from MEDIUM-confidence inference based on German marketplace REST patterns. If fields such as tracking_number, carrier, or quantity do not update correctly, the actual Hood.de API may use different field names. Consult the official Hood.de API documentation in your Verkäufer-Center and contact EcomCentral support with the corrected field names.

🔧 Quick sanity check — verify your API key is active by testing the connection from the EcomCentral Connections page. A Connected status with an order count confirms your credentials are working correctly.