API · Seguimiento de casos

Conecta tu software al seguimiento de casos de SellViaApp.

Crea y sigue intervenciones, asigna técnicos y gestiona mensajes, documentos, presupuestos, aprobaciones, listas, recurrencias y tiempos desde tu propio sistema.

Base URLhttps://api.sellviaapp.com/
Required headersX-API-Key + Bearer
Developer supportapi@sellviaapp.com

Inicio rápido

Authenticate, choose a route, test.

Get the X-API-Key and generate the Bearer in Dashboard → API. Enter them below, then use “Test · Generate” on an endpoint to obtain the response and cURL, PHP 8 or JavaScript code.

Credentials incompleteEnter the X-API-Key and Bearer token to prepare a test.

Credentials remain in memory for this page only. For a customer-related operation, add customer_id.

Keep in mindHTTPS + JSON · keep both credentials server-side · never send tokens to support.

ERP ↔ SellViaApp

Your ERP can drive the complete mobile experience.

The API is not limited to retrieving cases. Your software can configure the module, supply the data used by the app, assign technicians and retrieve actions completed in the field or by customers.

From your ERP to the app

Organise and send work

Intervention types, forms, customers, technicians, cases, appointments, missions, checklists, documents, quotes, recurring work and knowledge base.

From the app to your ERP

Retrieve real activity

Customer requests, statuses, progress, messages, photos, documents, completed steps, time entries, quote decisions, approvals and signatures.

Controlled synchronisation

Keep one business workflow

Your ERP stores the identifiers returned by SellViaApp, retrieves cases and related data, then applies only relevant changes to your system.

  1. 1
    ConnectUse the X-API-Key and Bearer generated in Dashboard → API.
  2. 2
    ConfigureCreate the required types, forms, technicians, checklists and technical content.
  3. 3
    OperateCreate or update cases, then assign interventions.
  4. 4
    SynchroniseRetrieve cases, messages, documents, time entries and approvals needed by your ERP.
Developer tipStart with Cases and lifecycle, then add the business categories your ERP actually needs. Every endpoint can be tested and generates ready-to-copy code.

Puntos finales

Cases and lifecycle

Create, search, retrieve and update a case: status, priority, progress, appointments, assignment and technician mission.

5 routes
GET /case/list Llav + portador

List the signed-in customer cases; a supplier token can list every case.

GET /case/detail Llav + portador

Retrieve a case with timeline, messages, documents and detailed quotes. The private mission is returned only to the assigned technician and supplier.

POST /case/create Llav + portador

Create a service request linked to the customer.

PATCH /case/update Llav + portador

Update customer, type, status, priority, progress, appointment and assignment.

GET /case/status/list Llav + portador

List workflow statuses and their translated labels.

Puntos finales

Types and forms

Let the ERP manage intervention types and custom fields requested in the mobile app.

8 routes
GET /case/type/list Llav + portador

List available intervention types.

POST /case/type/add Llav + portador

Create an intervention type.

PATCH /case/type/update Llav + portador

Edit, reorder or hide an intervention type.

DELETE /case/type/delete Llav + portador

Delete an unused type or archive a linked type.

GET /case/form/list Llav + portador

List custom service-request fields.

POST /case/form/add Llav + portador

Add information to request from customers.

PATCH /case/form/update Llav + portador

Update a custom request field.

DELETE /case/form/delete Llav + portador

Delete or archive a custom request field.

Puntos finales

Technicians and assignments

Synchronise field teams, skills and roles, then assign every intervention to the right technician.

5 routes
GET /case/technician/list Llav + portador

List technicians separately with job, skills, availability and workload.

GET /case/technician/detail Llav + portador

Retrieve a technician’s complete professional record.

PATCH /case/technician/profile Llav + portador

Create or update a technician account’s professional profile.

PATCH /case/technician/role Llav + portador

Assign the Customer or Technician role to a mobile account.

PATCH /case/technician/update Llav + portador

Allow the assigned technician to update status and progress.

Puntos finales

Missions and checklists

Prepare procedures, retrieve applied steps and record field completion.

7 routes
GET /case/checklist/list Llav + portador

Retrieve the checklist and progress for an authorised case.

PATCH /case/mission/update Llav + portador

Set the private mission visible only to the assigned technician.

PATCH /case/checklist/item/update Llav + portador

Complete or reopen a step; assigned technician or supplier only.

GET /case/checklist/template/list Llav + portador

List checklist templates and their steps.

POST /case/checklist/template/add Llav + portador

Create a global checklist or one linked to an intervention type.

PATCH /case/checklist/template/update Llav + portador

Update a template and safely replace its steps.

DELETE /case/checklist/template/delete Llav + portador

Delete an unused template or archive an applied template.

Puntos finales

Time tracking

Start, stop, add and audit technician time for every case.

5 routes
GET /case/time/list Llav + portador

List time entries and total tracked time for an authorised case.

POST /case/time/start Llav + portador

Start a live timer for the assigned technician.

POST /case/time/stop Llav + portador

Stop and calculate the active time entry.

POST /case/time/add Llav + portador

Manually add a date, start time and end time.

POST /case/time/delete Llav + portador

Soft-delete a time entry with a mandatory reason retained in the audit trail.

Puntos finales

Messages, photos and documents

Exchange data with the app, classify documents, send photos and retrieve authorised files.

10 routes
POST /case/message/send Llav + portador

Add a message to the case; the sender is identified automatically from the authenticated account.

GET /case/document-type/list Llav + portador

List document types visible in the mobile app.

POST /case/document-type/add Llav + portador

Create a document type for the shop.

PATCH /case/document-type/update Llav + portador

Edit, reorder or hide a document type.

DELETE /case/document-type/delete Llav + portador

Delete an unused type or archive a type already in use.

GET /case/document/list Llav + portador

List all authorised documents newest first with their customer, technician or administrator source.

POST /case/document/add Llav + portador

Add one or more photos, PDFs, documents or signatures, optionally linked to a checklist step.

GET /case/document/get Llav + portador

Download the Base64 content of an authorised document.

GET /case/document/preview Llav + portador

Load an optimised image thumbnail before opening and zooming.

DELETE /case/document/delete Llav + portador

Delete a document that is not attached to a quote.

Puntos finales

Quotes, approval and signature

Create detailed quotes, retrieve customer decisions and manage final intervention approval.

4 routes
POST /case/quote/create Llav + portador

Create and send a detailed quote with lines, discounts, VAT and an optional attachment.

POST /case/quote/respond Llav + portador

Accept or reject a quote sent to the customer.

POST /case/validation/request Llav + portador

Request customer approval and signature.

POST /case/validation/send Llav + portador

Record the customer signature, either directly by the customer or on the assigned technician’s phone.

Puntos finales

Planning, recurrence and reports

Automate recurring interventions and produce structured final-report data.

6 routes
GET /case/recurrence/list Llav + portador

List recurring services.

POST /case/recurrence/add Llav + portador

Create a recurrence from a source case.

PATCH /case/recurrence/update Llav + portador

Update a recurring service.

DELETE /case/recurrence/delete Llav + portador

Stop a recurring service.

POST /case/recurrence/process Llav + portador

Generate recurring services that are due.

GET /case/report/summary Llav + portador

Prepare the final report with fields and before/after photos.

Puntos finales

Notificaciones

Retrieve customer or technician alerts and synchronise their read status.

2 routes
GET /case/notification/list Llav + portador

List automatic notifications for the signed-in customer or technician.

POST /case/notification/read Llav + portador

Mark one or every notification as read.

Puntos finales

Knowledge base

Supply procedures, FAQs and technical documents available to technicians in the mobile app.

12 routes
GET /case/knowledge/categories Llav + portador

List knowledge-base categories. On mobile, access is restricted to active technicians.

GET /case/knowledge/search Llav + portador

Quickly search FAQs, information, procedures and documents by keyword. Mobile access is technician-only.

GET /case/knowledge/detail Llav + portador

Open an entry and list its attachments without loading large files.

GET /case/knowledge/document Llav + portador

Download an authorised Base64 attachment.

POST /case/knowledge/category/add Llav + portador

Create a knowledge category.

PATCH /case/knowledge/category/update Llav + portador

Edit, reorder or hide a category.

DELETE /case/knowledge/category/delete Llav + portador

Delete a category while retaining its entries as uncategorised.

POST /case/knowledge/article/add Llav + portador

Create a FAQ, information entry, procedure or documentation.

PATCH /case/knowledge/article/update Llav + portador

Edit and publish an entry.

DELETE /case/knowledge/article/delete Llav + portador

Delete an entry and its attachments.

POST /case/knowledge/document/add Llav + portador

Attach a document up to 8 MB.

DELETE /case/knowledge/document/delete Llav + portador

Delete an attachment.

Reference

Responses and errors

Each row has a “Parameters and responses” button showing required or optional fields, possible statuses and JSON examples. An empty list means the resource is not populated yet, not that the endpoint is down.

400Solicitud de invalidez
401Autenticación necesaria
403Acceso denegado
404Recursos o ruta no encontrada
409Conflicto comercial
422Falló la validación
429Demasiadas solicitudes
5xxIncidencia técnica

Entorno de trabajo API

Endpoint

GET

El código generado contiene las credenciales introducidas. Guárdalas en el servidor y nunca compartas una captura sin ocultarlas.

Listo para probar