Skip to main content
GET
/
v1
/
common
/
customer
/
{customerId}
/
detail
Get Customer Detail
curl --request GET \
  --url https://api.provider.fiskil.com/v1/common/customer/{customerId}/detail \
  --header 'Authorization: Bearer <token>'
{
  "data": {
    "customerUType": "person",
    "person": {
      "lastUpdateTime": "2025-02-03T00:00:00.000Z",
      "firstName": "Peter",
      "lastName": "Sherman",
      "middleNames": [
        "Mary"
      ],
      "prefix": "Dr",
      "occupationCodeVersion": "ANZSCO_1220.0_2006_V1.0",
      "phoneNumbers": [
        {
          "isPreferred": true,
          "purpose": "MOBILE",
          "countryCode": 61,
          "number": 4123456789,
          "fullNumber": 614123456789
        }
      ],
      "emailAddresses": [
        {
          "isPreferred": true,
          "purpose": "HOME",
          "address": "psherman@example.com"
        }
      ],
      "physicalAddresses": [
        {
          "addressUType": "simple",
          "simple": {
            "mailingName": "P Sherman",
            "addressLine1": "42 Wallaby Way",
            "postcode": "2000",
            "city": "Sydney",
            "state": "NSW",
            "country": "AUS"
          },
          "purpose": "MAIL"
        }
      ]
    }
  }
}

Authorizations

​
Authorization
string
header
required

The Fiskil Data Provider will include a self-signed JWT as a Bearer token in the Authorization header. You should verify this JWT using the JWKS URL you can find for your Data Provider instance in the Fiskil Console. To verify the JWT you must:

  • Verify the signature
  • Ensure the token has not expired by checking the exp claim
  • The sub and iss claims are your data provider subdomain
  • The aud claim is the URI of the resource being requested (excluding any query parameters)
  • The jti value is unique For further detail on security and authentication refer to our Authentication documentation

Path Parameters

​
customerId
string
required

Unique ID of a customer. This ID must not change for the lifecycle of the customer

Response

Details of the customer with the ID given in the URL path

​
data
object
required