Command 50 — List of client life-cycle stagesrework
V1 took a date range (FromDate, ToDate) and an origin (ClientRefererID) and returned the stage changes of the clients in that range: one row each time a client moved to a new life-cycle stage, dated on the day of the change. V2 has no equivalent of that history. The closest tool is the acquisition work list: a list of the clients that are currently in the stages you choose, which you create and then read page by page, and which the clinic can also work from the application.
Permissions
Section titled “Permissions”V2 checks an app permission on every call — V1 checked none — and a call whose permission is missing answers 400 with errorCode 15, the same status as an invalid payload (see 4.4). Grant these to the API user before porting the command; the names are the ones of the permission tree in flowww.
| Call | Permission |
|---|---|
POST /client/advanced-search | Clients → Advanced Search - Search |
GET /client/{clientID} | Clients → Clients - Edit |
POST /acquisition | Clients → New |
POST /acquisition/{AcqID}/client/{ClientID}/action | Clients → Execute action |
GET /acquisition | Clients → Acquisition |
DELETE /acquisition/{AcqID} | Clients → Clients - Delete acquisition list |
GET /acquisition/{AcqID} | Clients → View |
The flow
Section titled “The flow”curl --location --request POST 'https://euapi.flowww.net/v1/fwa_external_get.asp?cmd=50&doctor=USER_LOGIN&pass=USER_PASS&country=ES&key=SYSTEM_KEY&FromDate=01/01/2026&ToDate=31/03/2026&ClientRefererID=7'curl --location 'https://api.flowww.net/v2/acquisition?clinicID=1' \ --header 'Authorization: Bearer <api_key>' \ --header 'Content-Type: application/json' \ --data '{ "AcqName": "Q1 leads from the web", "AcqStart": "01/01/2026", "AcqEnd": "31/03/2026", "AcqClinicID": "0", "AcqRefererID": "7", "AcqLifeCycleStage": "1,2" }'
→ 200 with an empty body: the id of the new list is not returned.curl --location 'https://api.flowww.net/v2/acquisition?clinicID=1' \ --header 'Authorization: Bearer <api_key>'Look for your AcqName in the answer and keep its AcqID. Give each list a unique name so you can find it: the call takes ?AcqName= to filter by name, and pages ten at a time with ?Page=.
curl --location 'https://api.flowww.net/v2/acquisition/{AcqID}?Page=0' \ --header 'Authorization: Bearer <api_key>'Field mapping
Section titled “Field mapping”| API V1 | API V2 | Notes |
|---|---|---|
FromDate / ToDate | AcqStart / AcqEnd | Different meaning. V1: the date of the stage change. V2: the date the client was registered, or converted from that origin. Same dd/MM/yyyy format. Optional in V2. |
ClientRefererID | AcqRefererID | Now a comma-separated list, and 0 means every origin. |
| every stage change | AcqLifeCycleStage | Mandatory: the stage ids the list targets. The list contains the clients currently in those stages. |
| — | AcqClinicID | Mandatory: comma-separated clinic ids, 0 for all of them. |
Because the work list is a first-class object in V2, you also get the follow-up side for free: POST /acquisition/{AcqID}/client/{ClientID}/action records on each lead a call (CAL), a dismissal (SKP), a postponement (POS, with AcqAPostpone) or the close because the client already has an appointment (APP) or a quote (BUD), GET /acquisition lists the work lists, and DELETE /acquisition/{AcqID} removes one.
What changes compared with V1
Section titled “What changes compared with V1”| Topic | API V1 | API V2 |
|---|---|---|
| What you get | One row per stage change, with the stage reached and the date. | One row per client currently in the chosen stages. Neither the date of the change nor the client’s stage is returned in the list; the origin comes as its description, not its id. |
| Mandatory filters | FromDate, ToDate and ClientRefererID. | AcqName, AcqClinicID, AcqRefererID and AcqLifeCycleStage. Clients with no origin are not included. |
| Repeated reads | Always the same rows for the same range. | Clients already worked in the list (called, dismissed, postponed) drop out of it. |
| Paging | None. | Both reads page with Page, starting at 0: GET /acquisition brings ten lists per page, and GET /acquisition/{AcqID} the clients of one. Stop when a page brings fewer items than the previous one. |
| The list itself | Nothing was stored. | The list is saved in the system and visible in the application. Delete it with DELETE /acquisition/{AcqID} when you no longer need it. |
If what you need is the history of stage changes, subscribe to crm.client.updated (see 4.9) and keep the history on your side from now on.
Errors
Section titled “Errors”| Answer | Meaning | What to do |
|---|---|---|
400 16 | Empty AcqName, missing stages, clinics or origins, or an unknown list. | Complete the body or check the AcqID. |
400 invalid-request-data | A field is not valid. | Fix the field. Avoid double quotes in AcqName. |
400 (errorCode 15) | The API user lacks the Clients → Tools for customer acquisition permissions. | Grant them. |