Seller Integrations

Seller API

Manage seller-authorized products and orders using ALEFBA API v1.

Available

Base URL

https://alefba.eu/api/v1

Authentication

Every Seller API request must include a live API key:

Authorization: Bearer alefba_live_YOUR_API_KEY

Health check

GET/api/v1/ping

Confirms that the key is valid and the protected API is reachable.

curl --request GET \
  --url "https://alefba.eu/api/v1/ping" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer alefba_live_YOUR_API_KEY"

Products

GET/api/v1/products

GET/api/v1/products?id=123

POST/api/v1/products

PUT/api/v1/products?id=123

List products

curl --request GET \
  --url "https://alefba.eu/api/v1/products" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer alefba_live_YOUR_API_KEY"

Retrieve one product

curl --request GET \
  --url "https://alefba.eu/api/v1/products?id=123" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer alefba_live_YOUR_API_KEY"

Create a product

Send a JSON request body matching the fields accepted by the live Products endpoint.

curl --request POST \
  --url "https://alefba.eu/api/v1/products" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer alefba_live_YOUR_API_KEY" \
  --data '{
    "name": "Example product",
    "price": 29.99
  }'

Update a product

curl --request PUT \
  --url "https://alefba.eu/api/v1/products?id=123" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer alefba_live_YOUR_API_KEY" \
  --data '{
    "name": "Updated product"
  }'

Orders

GET/api/v1/orders

GET/api/v1/orders?id=123

List orders

curl --request GET \
  --url "https://alefba.eu/api/v1/orders" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer alefba_live_YOUR_API_KEY"

Authorization and isolation

Seller credentials must only expose resources authorized for the account linked to that API key. A client must not assume that numeric identifiers belonging to another seller are accessible.

Common errors

Status	Use
`400`	Invalid JSON or invalid request data.
`401`	Missing, invalid or revoked API key.
`404`	The requested seller resource was not found or is not accessible.
`429`	The daily request limit was reached.
`500`	An unexpected server error occurred.

Product request fields: The example body is illustrative. Keep the fields aligned with the live products.php implementation before publishing them as a fixed contract.