Authentication

All eCore API requests are authenticated with your API token in the Authorization header.

Header Format

Pass your token with the Token prefix:

Authorization: Token YOUR_API_TOKEN

The Bearer prefix is also accepted on every endpoint and is equivalent:

Authorization: Bearer YOUR_API_TOKEN

Use whichever your HTTP client makes easiest — the same token value works either way, on any endpoint.

Base URL

Environment	Base URL
Production	https://backend.ecoreservice.com/api/v1
Test	https://test.ecoreservice.com/backend/api/v1

Endpoint paths in this reference are appended to the base. For example, GET /external/search/ resolves in production to https://backend.ecoreservice.com/api/v1/external/search/.

Note the paths differ slightly between environments: the test host includes a /backend segment (…/backend/api/v1) while production does not (…/api/v1).

Response Envelope

Every response from the API is wrapped in a standard envelope:

{
  "success": true,
  "response": { }
}

• success — boolean. true when the request succeeded, false on error.
• response — the actual payload for the call (an object or array). On errors this carries the error detail.

Reading the examples in this reference: to keep them focused, the response examples on each endpoint page show the contents of response — i.e. the payload you get after unwrapping the envelope. In real traffic that payload is nested under response, alongside the top-level success flag.

Getting Your API Token

Get your API token from the eCore dashboard under Settings → API Tokens.

Keep your token secret — anyone with the token can make requests against your account and spend your wallet credits. Never store tokens in client-side code.

Example Request

curl -X GET \
  "https://backend.ecoreservice.com/api/v1/external/search/?industry=Technology&limit=5" \
  -H "Authorization: Token YOUR_API_TOKEN"

Error Response — Invalid or Missing Token

{
  "detail": "Invalid token."
}

HTTP 401 Unauthorized. See Error Codes for the full list.