Portal para desarrolladores de ECOSIRE

Cree poderosas integraciones con nuestra API REST integral. Más de 818 puntos finales, especificaciones OpenAPI completas y SDK de TypeScript.

Ver documentación API Obtener clave API

818+

Puntos finales API

Módulos

REST

Arquitectura

Localidades admitidas

API

Inicio rápido

Póngase en marcha con la API ECOSIRE en minutos

autenticar

Utilice OAuth2 a través de claves Authentik o API para obtener un token de portador JWT para acceder a la API.

POST /api/auth/login

Haz tu primera llamada

Utilice el token de portador en el encabezado Autorización para llamar a cualquier punto final de API.

# Listar todos los contactos

curl -H "Authorization: Bearer $TOKEN" \

https://api.ecosire.com/api/contacts

Utilice el SDK

Instale nuestro SDK de TypeScript para llamadas API con seguridad de tipos con manejo de errores integrado.

import { EcosireClient } from "@ecosire/sdk";

const client = new EcosireClient({ apiKey });

const contacts = await client.contacts.list();

57 Modules

Módulos API

Explore 57 módulos que cubren todos los aspectos de las operaciones empresariales

Núcleo

AuthUsersContactsProductsOrdersProjectsSettings

Finanzas

AccountingSalesPurchaseBillingInvoicing

Operaciones

InventoryManufacturingPOSRentalPlanning

Recursos Humanos

EmployeesRecruitmentTime OffAttendanceExpensesPayrollAppraisals

Marketing y crecimiento

Email MarketingEventsMarketing AutomationAnalyticsAffiliatesLoyalty

IA y automatización

ECOSIRE AISelf-Evolving EngineContent GenerationSEO Scanner

Security

Autenticación

Dos métodos de autenticación que se adaptan a sus necesidades de integración

Cookies HttpOnly

Autenticación segura basada en cookies para aplicaciones de navegador. Los tokens nunca están expuestos a JavaScript.

Automático con la aplicación web
HttpOnly, seguro, SameSite=Lax
Rotación de tokens de actualización de 7 días

Ficha al portador

Utilice tokens de portador JWT para integraciones de servidor a servidor y clientes API.

// Authorization header

Authorization: Bearer <your_jwt_token>

// Or via HttpOnly cookie

Cookie: ecosire_auth=<token>

Interactive

API Playground

Try any endpoint directly from your browser. Select an endpoint, fill in parameters, and send live requests to the ECOSIRE API.

ECOSIRE API Playground

api.ecosire.com/api

POST/auth/login

Authorization

Request Body (JSON)

https://api.ecosire.com/api/auth/login

Code Snippet

curl -X POST \ \
  "https://api.ecosire.com/api/auth/login" \ \
  -H "Content-Type: application/json" \
  -d '{   "email": "[email protected]",   "password": "secret" }'

SDK

SDK Code Examples

Install the ECOSIRE SDK in your language of choice and explore 6 common operations with full code snippets.

Installation

Choose your language and install the ECOSIRE SDK

npm install @ecosire/sdk

Code Examples

6 common operations with full SDK snippets

1. Authentication

Obtain a JWT token and include it in subsequent requests.

import { EcosireClient } from '@ecosire/sdk';

const client = new EcosireClient({
  baseUrl: 'https://api.ecosire.com/api',
  apiKey: process.env.ECOSIRE_API_KEY,
});

// Login with credentials
const session = await client.auth.login({
  email: '[email protected]',
  password: 'secret',
});

console.log(session.token);   // JWT token
console.log(session.user);    // { id, email, name, role }

// All subsequent calls auto-attach the token
const contacts = await client.contacts.list();

Webhooks

Webhook Events

ECOSIRE sends real-time webhook events to your server when key actions occur — payments, subscriptions, license activations, and more.

Webhook Event Tester

Explore all 8 webhook events, generate cURL commands, and verify HMAC signatures.

Select Webhook Event

Your Webhook URL (optional)

Checkout Completed

checkout.session.completed

Fired when a customer completes payment in a Stripe Checkout Session.

Trigger: Customer pays for a product in the storefront. Auto-grants licenses and creates order.

Example JSON payload delivered to your webhook endpoint for checkout.session.completed.

json

{
  "id": "evt_1ABCxyz",
  "object": "event",
  "type": "checkout.session.completed",
  "created": 1711000000,
  "data": {
    "object": {
      "id": "cs_live_abc123",
      "object": "checkout.session",
      "customer_email": "[email protected]",
      "amount_total": 24900,
      "currency": "usd",
      "mode": "payment",
      "payment_status": "paid",
      "metadata": {
        "userId": "usr_01HXYZ",
        "productIds": "[\"prd_01HODOOCRM\"]"
      }
    }
  }
}

All Webhook Events

Event	Trigger	Fields
`checkout.session.completed` Checkout Completed	Customer pays for a product in the storefront. Auto-grants licenses and creates order.	7 fields
`invoice.paid` Invoice Paid	Monthly/annual subscription renewal is processed. Reactivates suspended licenses and logs billing record.	6 fields
`customer.subscription.deleted` Subscription Cancelled	Subscription period ends and cancel_at_period_end was true, or immediate cancellation was requested. Suspends all associated licenses.	5 fields
`customer.subscription.updated` Subscription Updated	Customer changes their plan, payment fails and subscription pauses, or subscription resumes after payment. Syncs license status accordingly.	5 fields
`charge.refunded` Charge Refunded	Admin or customer initiates a refund via Stripe Dashboard or API. Revokes associated licenses and marks the order as refunded.	5 fields
`payment_intent.payment_failed` Payment Failed	Subscription renewal fails or one-time payment is declined. Marks order as payment_failed and sends failure notification email.	5 fields
`license.validated` License Validated	Odoo module calls POST /licenses/validate on server startup. Used for audit logging and anomaly detection.	5 fields
`license.activated` License Activated	First time POST /licenses/activate is called for a domain. Logs the activation for audit and security monitoring.	5 fields

Verify webhook signatures in production

Always verify the stripe-signature header for Stripe events using your STRIPE_WEBHOOK_SECRET. For license events, verify the X-License-Signature header using ECOSIRE_LICENSE_SECRET. Unverified events should be rejected with 401.

Reference

Error Codes

All API errors follow RFC 7807 (Problem Details for HTTP APIs). Every error includes a machine-readable code and human-readable message.

Status	Meaning	When it occurs
200	OK	Successful GET or POST returning data
201	Created	Successful resource creation (POST)
204	No Content	Successful DELETE or PUT with no body
400	Bad Request	Invalid request body, missing required fields, or malformed JSON
401	Unauthorized	Missing, expired, or invalid JWT token
403	Forbidden	Valid token but insufficient role (e.g. requires admin)
404	Not Found	Resource does not exist or has been deleted
409	Conflict	Duplicate resource — email already registered, license already active
422	Unprocessable	Validation failed — Zod schema rejection with field-level details
429	Too Many Requests	Rate limit exceeded — see Retry-After header
500	Server Error	Unexpected server error — stack trace hidden in production

Error Response Shape

{
  "statusCode": 422,
  "error": "Unprocessable Entity",
  "message": "Validation failed",
  "details": [
    { "field": "email", "message": "Invalid email address" },
    { "field": "password", "message": "Must be at least 8 characters" }
  ]
}

Rate Limits

Límites de tarifas

Límites de uso justos para garantizar la estabilidad de la API para todos los usuarios

Punto final	Límite de tarifa
POST /support	5/min
POST /crm/capture	10/min
POST /ecosire-ai/ask	20/min
POST /licenses/validate	30/min
POST /licenses/activate	10/min
POST /newsletter/subscribe	5/min
Authenticated endpoints	100/min

Rate Limit Response Headers

X-RateLimit-LimitMaximum requests allowed in the window

X-RateLimit-RemainingRequests remaining in the current window

X-RateLimit-ResetUnix timestamp when the window resets

Retry-AfterSeconds to wait before retrying (on 429)

SDK

Recursos y SDK

Todo lo que necesitas para construir tu integración

Documentos API interactivos

Explore y pruebe cada punto final con nuestra interfaz Swagger UI. Pruebe las llamadas API directamente desde su navegador.

Abrir documentos

Especificaciones de OpenAPI

Descargue la especificación completa de OpenAPI 3.0 en formato JSON. Importe a Postman, Insomnia o sus propias herramientas.

Descargar JSON

SDK de mecanografiado

Cliente API con seguridad de escritura con autocompletado, manejo de errores y lógica de reintento incorporada.

npm install @ecosire/sdk

API Keys

API Key Management

Create and manage API keys from your dashboard. Each key can be scoped to specific permissions and rotated independently.

Create API Keys

Generate new API keys from Dashboard → Settings → API Keys. Each key has a name, optional expiry date, and role scope.

Scoped Permissions

Keys can be scoped to read-only, read-write, or admin. Admin keys can manage other keys and access all endpoints.

Key Rotation

Rotate keys at any time without downtime. The old key remains valid for 24 hours after rotation for a smooth transition.

Usage Analytics

View per-key request counts, error rates, and last-used timestamps from the API Keys dashboard page.

Environment Keys

Maintain separate keys for development, staging, and production. Production keys log all requests for audit purposes.

Webhook Secrets

Webhook endpoints also use a separate ECOSIRE_LICENSE_SECRET for HMAC-SHA256 signature verification on license events.

Using an API Key

# Pass the key as a Bearer token in the Authorization header
curl https://api.ecosire.com/api/contacts \
  -H "Authorization: Bearer ecos_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

# Or use HttpOnly cookies (browser-based auth — set automatically on login)
# Cookie: ecosire_auth=<jwt_token>

FAQ

Preguntas frecuentes

Preguntas comunes sobre la API de ECOSIRE

¿Cómo obtengo acceso a la API?

Regístrese para obtener una cuenta ECOSIRE y navegue hasta Panel > Claves API para generar sus credenciales API. El acceso API está disponible en todos los planes.

¿Existe un nivel gratuito?

Sí, todas las cuentas ECOSIRE incluyen acceso API. Los límites de tarifas varían según el plan. El nivel gratuito admite hasta 1000 llamadas API por día.

¿Qué métodos de autenticación se admiten?

Admitimos OAuth2 a través de Authentik (recomendado para aplicaciones web), tokens de portador JWT (para servidor a servidor) y claves API (para integraciones simples).

¿Tiene soporte para webhooks?

Sí, ECOSIRE admite webhooks para notificaciones de eventos en tiempo real. Configure los puntos finales del webhook en Panel > Configuración > Webhooks.

¿Qué es el SLA de tiempo de actividad de API?

Mantenemos un tiempo de actividad del 99,9 % para todos los puntos finales API. La página de estado y el historial de incidentes están disponibles en status.ecosire.com.

¿Listo para construir?

Obtenga su clave API y comience a crear integraciones en minutos.

Obtener clave API Ver documentación

import { EcosireClient } from '@ecosire/sdk'; const client = new EcosireClient({ baseUrl: 'https://api.ecosire.com/api', apiKey: process.env.ECOSIRE_API_KEY, }); // Login with credentials const session = await client.auth.login({ email: '[email protected]', password: 'secret', }); console.log(session.token); // JWT token console.log(session.user); // { id, email, name, role } // All subsequent calls auto-attach the token const contacts = await client.contacts.list();

{ "id": "evt_1ABCxyz", "object": "event", "type": "checkout.session.completed", "created": 1711000000, "data": { "object": { "id": "cs_live_abc123", "object": "checkout.session", "customer_email": "[email protected]", "amount_total": 24900, "currency": "usd", "mode": "payment", "payment_status": "paid", "metadata": { "userId": "usr_01HXYZ", "productIds": "[\"prd_01HODOOCRM\"]" } } } }

Event

checkout.session.completed

Checkout Completed

invoice.paid

Invoice Paid

customer.subscription.deleted

Subscription Cancelled

customer.subscription.updated

Subscription Updated

charge.refunded

Charge Refunded

payment_intent.payment_failed

Payment Failed

license.validated

License Validated

license.activated

License Activated

Status

Meaning

200

201

Created

204

No Content

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

409

Conflict

422

Unprocessable

429

Too Many Requests

500

Server Error

{ "statusCode": 422, "error": "Unprocessable Entity", "message": "Validation failed", "details": [ { "field": "email", "message": "Invalid email address" }, { "field": "password", "message": "Must be at least 8 characters" } ] }

Punto final

Límite de tarifa

POST /support

5/min

POST /crm/capture

10/min

POST /ecosire-ai/ask

20/min

POST /licenses/validate

30/min

POST /licenses/activate

10/min

POST /newsletter/subscribe

5/min

Authenticated endpoints

100/min

# Pass the key as a Bearer token in the Authorization header curl https://api.ecosire.com/api/contacts \ -H "Authorization: Bearer ecos_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" # Or use HttpOnly cookies (browser-based auth — set automatically on login) # Cookie: ecosire_auth=<jwt_token>