Post Login Subscriber Profile

After login, the authenticated subscriber detail can be requested.

This is usually called when the login authentication API has been successful to return profile information about the logged in subscriber which can be displayed in the UI e.g. name, company, photo etc..

Post Login Subscriber Details

POST Security/PostLoginCRMCredentials

This is a POST method which passes both the API and session keys as headers. If successful, the subscriber profile details can be stored and displayed. No security credentials are sent in these profile details.

Headers

Name
Value

Content-Type

application/json

SiteKey

API Key

DataServicesKey

Session Key

Body

No body is required as the API knows who the subscriber is from their session key.

Response

{
  "Success": true,
  "CDataConnectionKey": {
    "SQLServer": "server-name",
    "Database": "Flexiva",
    "GDrivePath": "UNC-share-name",
    "LoggedInUser": {
        "UserId": 12345,
        "LoginName": "Fred.Bloggs",
        "FullName": "[email protected]",
        "ForenameAndSurname": "Fred Bloggs",
        "CompanyName": "Boggy Frogs",
        "ContactId": 67890,
        "Contact": {
            "DateFirstRegistered": "2025-06-13T12:33:39",
            "Comments": "Added by TriSys API on Friday 13 June 2025 12:30:13",
            "ContactId": 54321,
            "FullName": "Fred Bloggs",
            "Forenames": "Fred",
            "Surname": "Blogs",
            "SurnameInitial": "B",
            "CompanyName": "Boggy Frogs",
            "CompanyId": 4567,
            "CompanyAddressStreet": "Hills Road",
            "CompanyAddressCity": "Cambridge",
            "CompanyAddressCounty": "Cambridgeshire",
            "CompanyAddressPostCode": "CB1 1BH",
            "CompanyAddressCountry": "United Kingdom",
            "JobTitle": "Software Engineer",
            "ContactType": "User",
            "Status": "Active",
            "WorkEMail": "[email protected]",
            "ContactPhotoURL": "https://api.trisys.co.uk/Chat/Profiles//dall-e.png",
            "CompanyIndustry": "Service Industry"
        },
        "CRMContact": {
            "ApexDeveloper": true,
            "SendApexScreenshot": false,
            "CustomForms": [
                {
                    "FileName": "Astronomy.json",
                    "FilePath": "custom/boggy-frogs/forms/astronomy.json",
                    "FullServerPath": nulll
                }
            ],            
            "Subscriber": {
                "AccountMaintainer": true,
                "UserHasRemoteDesktop": false,
                "CompanyHasRemoteDesktops": false,
                "UserHasPlatformixWebSites": false,
                "ASPUserType": "Flexiva",
                "ASPdbName": "Flexiva"
            },
            "ContactId": 123456,
            "FullName": "Fred Bloggs",
            "Forenames": "Fred",
            "Surname": "Bloggs",
            "SurnameInitial": "B",
            "CompanyName": "Boggy Frogs",
            "JobTitle": "Software Engineer",
            "ContactType": "Customer",
            "WorkEMail": "[email protected]"
        }
    },
    "TrialAccount": false,
    "AuthenticatedType": 12,
    "AccountType": 0,
    "ApplicationName": "Flexiva",
    "SQLServerVersion": "Microsoft SQL Server 2022...",
    "SQLServerName": "EC2AMAZ-1234INMU"
  }
}

Supplementary Information

Some of this information is available in the Flexiva application in User Options.

The logged in user is the subscriber, who is logged into a back-end customer database on our cloud as a user, which also has a contact record in our back-end CRM database. These details are not connected to a customers own ReST API for which they will have their own back-end databases.

Last updated