API · Case tracking

Connect your software to SellViaApp case tracking.

Create and track services, assign technicians, exchange messages and documents, and manage quotes, approvals, checklists, recurrences and time entries from your own system.

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

Quick start

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.

Endpoints

Cases and lifecycle

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

5 routes
GET /case/list Key + Bearer

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

GET /case/detail Key + Bearer

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 Key + Bearer

Create a service request linked to the customer.

PATCH /case/update Key + Bearer

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

GET /case/status/list Key + Bearer

List workflow statuses and their translated labels.

Endpoints

Types and forms

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

8 routes
GET /case/type/list Key + Bearer

List available intervention types.

POST /case/type/add Key + Bearer

Create an intervention type.

PATCH /case/type/update Key + Bearer

Edit, reorder or hide an intervention type.

DELETE /case/type/delete Key + Bearer

Delete an unused type or archive a linked type.

GET /case/form/list Key + Bearer

List custom service-request fields.

POST /case/form/add Key + Bearer

Add information to request from customers.

PATCH /case/form/update Key + Bearer

Update a custom request field.

DELETE /case/form/delete Key + Bearer

Delete or archive a custom request field.

Endpoints

Technicians and assignments

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

5 routes
GET /case/technician/list Key + Bearer

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

GET /case/technician/detail Key + Bearer

Retrieve a technician’s complete professional record.

PATCH /case/technician/profile Key + Bearer

Create or update a technician account’s professional profile.

PATCH /case/technician/role Key + Bearer

Assign the Customer or Technician role to a mobile account.

PATCH /case/technician/update Key + Bearer

Allow the assigned technician to update status and progress.

Endpoints

Missions and checklists

Prepare procedures, retrieve applied steps and record field completion.

7 routes
GET /case/checklist/list Key + Bearer

Retrieve the checklist and progress for an authorised case.

PATCH /case/mission/update Key + Bearer

Set the private mission visible only to the assigned technician.

PATCH /case/checklist/item/update Key + Bearer

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

GET /case/checklist/template/list Key + Bearer

List checklist templates and their steps.

POST /case/checklist/template/add Key + Bearer

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

PATCH /case/checklist/template/update Key + Bearer

Update a template and safely replace its steps.

DELETE /case/checklist/template/delete Key + Bearer

Delete an unused template or archive an applied template.

Endpoints

Time tracking

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

5 routes
GET /case/time/list Key + Bearer

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

POST /case/time/start Key + Bearer

Start a live timer for the assigned technician.

POST /case/time/stop Key + Bearer

Stop and calculate the active time entry.

POST /case/time/add Key + Bearer

Manually add a date, start time and end time.

POST /case/time/delete Key + Bearer

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

Endpoints

Messages, photos and documents

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

10 routes
POST /case/message/send Key + Bearer

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

GET /case/document-type/list Key + Bearer

List document types visible in the mobile app.

POST /case/document-type/add Key + Bearer

Create a document type for the shop.

PATCH /case/document-type/update Key + Bearer

Edit, reorder or hide a document type.

DELETE /case/document-type/delete Key + Bearer

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

GET /case/document/list Key + Bearer

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

POST /case/document/add Key + Bearer

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

GET /case/document/get Key + Bearer

Download the Base64 content of an authorised document.

GET /case/document/preview Key + Bearer

Load an optimised image thumbnail before opening and zooming.

DELETE /case/document/delete Key + Bearer

Delete a document that is not attached to a quote.

Endpoints

Quotes, approval and signature

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

4 routes
POST /case/quote/create Key + Bearer

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

POST /case/quote/respond Key + Bearer

Accept or reject a quote sent to the customer.

POST /case/validation/request Key + Bearer

Request customer approval and signature.

POST /case/validation/send Key + Bearer

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

Endpoints

Planning, recurrence and reports

Automate recurring interventions and produce structured final-report data.

6 routes
GET /case/recurrence/list Key + Bearer

List recurring services.

POST /case/recurrence/add Key + Bearer

Create a recurrence from a source case.

PATCH /case/recurrence/update Key + Bearer

Update a recurring service.

DELETE /case/recurrence/delete Key + Bearer

Stop a recurring service.

POST /case/recurrence/process Key + Bearer

Generate recurring services that are due.

GET /case/report/summary Key + Bearer

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

Endpoints

Notifications

Retrieve customer or technician alerts and synchronise their read status.

2 routes
GET /case/notification/list Key + Bearer

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

POST /case/notification/read Key + Bearer

Mark one or every notification as read.

Endpoints

Knowledge base

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

12 routes
GET /case/knowledge/categories Key + Bearer

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

GET /case/knowledge/search Key + Bearer

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

GET /case/knowledge/detail Key + Bearer

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

GET /case/knowledge/document Key + Bearer

Download an authorised Base64 attachment.

POST /case/knowledge/category/add Key + Bearer

Create a knowledge category.

PATCH /case/knowledge/category/update Key + Bearer

Edit, reorder or hide a category.

DELETE /case/knowledge/category/delete Key + Bearer

Delete a category while retaining its entries as uncategorised.

POST /case/knowledge/article/add Key + Bearer

Create a FAQ, information entry, procedure or documentation.

PATCH /case/knowledge/article/update Key + Bearer

Edit and publish an entry.

DELETE /case/knowledge/article/delete Key + Bearer

Delete an entry and its attachments.

POST /case/knowledge/document/add Key + Bearer

Attach a document up to 8 MB.

DELETE /case/knowledge/document/delete Key + Bearer

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.

400Invalid request
401Authentication required
403Access denied
404Resource or route not found
409Business conflict
422Validation failed
429Too many requests
5xxTechnical incident

API workbench

Endpoint

GET

Generated code contains the credentials you entered. Keep them server-side and never share an unredacted screenshot.

Ready to test