eloboost24.eu valid

Eloboost24 Seller API

REST API for marketplace sellers to manage listings (items, accounts, currency and top-ups), image galleries, and sale webhooks programmatically. Base URL: `https://eloboost24.eu/api/v1`.

For agents: REST API for marketplace sellers to manage listings, image galleries and sale webhooks; includes Markdown and OpenAPI docs and a help centre.

seller apimarketplace listingsrest apiwebhooksopenapi

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T10:45:57.999Z. Cached copy · Source on eloboost24.eu

# Eloboost24 Seller API

> REST API for marketplace sellers to manage listings (items, accounts, currency and top-ups), image galleries, and sale webhooks programmatically. Base URL: `https://eloboost24.eu/api/v1`.

## Authentication

Every request must be authenticated with an API key, sent as either header:

- `Authorization: Bearer <your-api-key>`
- `X-Api-Key: <your-api-key>`

Generate a key on your dashboard's Integrations page (https://eloboost24.eu/dashboard/integrations). API access requires admin approval before keys become active.

## Rate limits

Limits are per account (all of your API keys share one budget; unauthenticated traffic falls back to IP). Every response includes `X-RateLimit-Limit` and `X-RateLimit-Remaining`. Exceeding a limit returns `429 Too Many Requests` with a `Retry-After` header (seconds until that window resets).

Default limits when your key has no elevated daily override:

- Read endpoints (GET): 150 requests/minute, 10000 requests/day.
- Write endpoints (POST/PUT/PATCH/DELETE): 60 requests/minute, 3000 requests/day.
- Webhook test deliveries (`POST https://eloboost24.eu/api/v1/webhooks/{id}/test`): 5 requests/minute, 100 requests/day.

Windows are rolling: the minute counter resets 60 seconds after the first request that opened it, and the day counter resets 24 hours after the first request that opened it — not at midnight UTC.

## Resources

- Galleries (`https://eloboost24.eu/api/v1/gallery`): create and manage named image galleries reusable across listings.
- Items (`https://eloboost24.eu/api/v1/item`): CRUD for marketplace item listings, with game-specific fields.
- Accounts (`https://eloboost24.eu/api/v1/account`): CRUD for marketplace account listings, with game-specific fields.
- Currency (`https://eloboost24.eu/api/v1/currency`): CRUD for marketplace in-game currency listings, with game-specific fields.
- Top-ups (`https://eloboost24.eu/api/v1/topup`): CRUD for marketplace top-up listings, with game-specific fields and per-delivery-method packages.
- Webhooks (`https://eloboost24.eu/api/v1/webhooks`): register HTTPS endpoints to receive `offer.sold` and `item.sold` events, signed with `X-EB24-Signature-V2`.

## Documentation

- [Full API reference (Markdown)](https://eloboost24.eu/docs/api.md): every endpoint, parameter, and response in plain text.
- [OpenAPI specification (JSON)](https://eloboost24.eu/docs/api.json): machine-readable contract for code generation.
- [Interactive API docs](https://eloboost24.eu/docs/api): human-friendly browser UI.
- [Help Centre](https://eloboost24.eu/help-centre): customer FAQ, seller guides, and legal pages.


## Help Centre pages

- [Account security](https://eloboost24.eu/help-centre/customers/account-safety/account-security)
- [Account security for contractors](https://eloboost24.eu/help-centre/partners/rules-safety/contractor-security)
- [Account standing: warnings and strikes](https://eloboost24.eu/help-centre/partners/selling/account-standing)
- [Acheter des sess
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=eloboost24.eu · GET /v1/domain/eloboost24.eu · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for eloboost24.eu:
1. POST https://agentwebmap.com/v1/sites/eloboost24.eu/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://eloboost24.eu/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/eloboost24.eu/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/eloboost24.eu).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.