API archive entry · source-reported
api.ecota.co v2
The API ecotaco allows you to connect, create an account, manage your credit cards and order rides. # Authentication Ecotaco API use a system of application key and authentification token. ## Application key : The application key is generated by Ecota.co and unique to an application. Before accessing EcoTa.co APIs, you need to register your application. Please supply the following information to dev@ecota.co: - Application name - Company (if appropriate) - Contact name, phone and address - Contact email - Is this a web application, a desktop application, or an application running on a device? - Short description of your application It **must** be passed on request : "accounts -> login", "accounts -> facebook login" and "accounts -> register" . ## Authentification token : The authentification token is retrieved at login or register of an user. It **must** be passed in request for authenticate action in Authorization HTTP header. Example : Authorization: Token token=e55887022c1aca4c86abcc49e85ceb8a0c855d2af4d9fac75c08040a583dcde4 # Language On some of our resources, we filter the content displayed based on the Accept-Language header. If the language is not defined or if we don't use
Plan the first integration safely
The access fields below come from the connected directory. Their likely implementation impact is explained without assuming provider-specific behavior.
Authentication
OAuth is reported. Confirm flows, scopes, consent, token lifetime, and refresh rules.
Transport
HTTPS is not confirmed. Do not send credentials or production data until secure transport is verified.
Browser access
CORS is unknown. Treat direct browser access as unconfirmed and test before choosing a client-only architecture.
First-request sequence
- Identify the current base URL, version, and endpoint for the use case.
- Confirm how credentials are issued and where they may be stored.
- Test success, invalid input, throttling, unavailable data, and timeouts.
- Record response fields, pagination, caching, and error shapes.
- Add monitoring, retries with backoff, and an appropriate fallback.
Questions to resolve before production
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Source reference
This page separates source-reported facts from questions that need live provider verification.