Connector Ubiflow

Ubiflow does not offer OAuth for third-party applications. Authentication uses4 static credentials provided by Ubiflow to the housing provider:

• client_id — numeric identifier (e.g.654321)
• client_code — formatag + digits (e.g. ag654321)
• client_login — often the same asclient_code
• client_secret — API password

These 4 values are available at espace-dev.ubiflow.net, in theSettings > APIsection. If it does not appear, ask your Ubiflow contact to enable API access (free, on request).

On Toppla, the connection wizard is at /app/connect/ubiflow and has 3 steps:

1. Guide— visual instructions for retrieving the 4 credentials from Ubiflow.
2. Credentials— a 4-field form with live format validation; the “Test connection” button calls the Ubiflow API to validate credentials before saving.
3. Activation— choose the sync frequency and activate. The first sync starts automatically.

The first 3 identifiers are stored in plain text (they are not sensitive on their own). The client_secret isencrypted in the database using pgcryptoand is never shown in plain text after saving. Toppla decrypts it only when calling the Ubiflow API on the server.

If you suspect a key has been exposed, regenerate the secret in Ubiflow and enter it again in Toppla — the old secret will be revoked in Ubiflow.

• Manual— run the sync from the Connect module whenever needed. Ideal for testing or portfolios that rarely change.
• Every 6 hours— recommended if you publish or unpublish properties several times a day.
• Every 24 hours (default)— covers 95% of use cases: your properties are up to date in the morning and early afternoon.

You can change the frequency at any time from the Ubiflow card in Connect.

Properties synced from Ubiflow appear in My propertieswith an “Ubiflow” badge distinguishing them from manually entered properties. They areread-only : Ubiflow remains the source of truth. Make changes in Ubiflow; they will be applied at the next sync.

For companies browsing the housing marketplace, no distinction is shown — Ubiflow properties appear like any other available property.

• The sync backend is being implemented: currently only the UI wizard and credential test endpoint are available. Automatic recurring sync is coming soon.
• No configurable field mapping: all available Ubiflow properties are synced as they are.
• No real-time Ubiflow → Toppla webhook; only polling at the chosen frequency.
• One Toppla organisation = one Ubiflow account (no multiple accounts).

For any questions about the Ubiflow connector, please write to support@toppla.fr.

Official Ubiflow documentation (reference for Ubiflow developers):

• espace-dev.ubiflow.net
• api.ubiflow.net/api-tools/documentation