Skip to content
English
  • There are no suggestions because the search field is empty.

Get Started With The C60 Data Synch API

C60's data synch API allows our customers to upload their data into the C60 platform to identify the insights and opportunities available to them.

In order to get started you will need the following items to be provided to you by the C60 customer success team

  • The C60 data dictionary
  • The C60 data synch API JSON schema
  • Your C60 business ID
  • Your C60 api-key

Data Synch API Technology

  • Protocol: HTTPS
  • Payload: JSON
  • Security: JWT

C60 data synch API's are available 24 hrs a day Monday to Friday

How To Use The Data Synch API

In order to synch your data with the C60 platform there are 2 APIs that need to be used.

1. Access API

  • This API endpoint is used to authenticate your identity before accepting the data being sent
  • It will generate the JWT token required to use the data synch api
  • It must be called each time you want to synch your data with C60
  • It must be called before you can use the data synch API
  • Swagger console: https://psvcpccss.azurewebsites.net/swagger/
  • API Endpoint URL: https://psvcpccss.azurewebsites.net/authtoken
  • Input: api-key and business ID
  • Output: JWT token

2. Data Synch API

C60 requires your historical data and your daily incremental data in order to power the insights and opportunities.

  • Your first data synch should contain your historical data up to the current date
  • Your subsequent data synch should contain the new records that have been added since the last successful data synch as an incremental upload.
  • Data synch should be done at least once a day
  • This API endpoint is used to upload your data to the c60 platform
  • You must generate the JWT token using the C60 Access API before calling this endpoint
  • Your data must be uploaded as a compressed JSON file conformant to the C60 JSON schema
    • JSON file must be encoded in utf-8 (utf-8-sig and others are not supported)
    • supported compression file formats: .zip,.tar, .gz and .rar
  • Swagger console: https://psvcdtsynch.azurewebsites.net/swagger/
  • API Endpoint URL: https://psvcdtsynch.azurewebsites.net/synchronize
  • HTTP Header Content-Type must be set to multipart/form-data
  • Input: compressed JSON file, business ID, api-key, JWT token
  • Output: acknowledgment

If a data synch fails you can re-upload the same day or the next day with all new records combined in one data synch call

3. DriverScheduleDataSynch API

C60 requires your historical data and your daily incremental driver schedule data in order to power the insights and opportunities.

  • Your first driver schedule data synch should contain your historical data up to the current date
  • Your subsequent driver scheduledata synch should contain the new records that have been added since the last successful data synch as an incremental upload.
  • Data synch should be done at least once a day
  • This API endpoint is used to upload your data to the c60 platform
  • You must generate the JWT token using the C60 Access API before calling this endpoint
  • Your data must be uploaded as a compressed JSON file conformant to the C60 JSON schema
    • JSON file must be encoded in utf-8 (utf-8-sig and others are not supported)
    • supported compression file formats: .zip,.tar, .gz and .rar
  • Swagger console: https://psvcdtsynch.azurewebsites.net/swagger/
  • API Endpoint URL: https://psvcdtsynch.azurewebsites.net/driverscheduledatasynch
  • HTTP Header Content-Type must be set to multipart/form-data
  • Input: compressed JSON file, business ID, api-key, JWT token
  • Output: acknowledgment

 

If a data synch fails you can re-upload the same day or the next day with all new records combined in one data synch call

 

If you have any questions or are encountering issues do not hesitate to reach out to your c60 customer success representative.