API Access Token

v1_upload API

/**
 * REST API end-points for interacting with the 'files' resource.
 *
 * Each end-point below sets up and returns the required form attributes (valid for 15 minutes) for uploading a file directly to AWS s3.
 * See {@link https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-post-example.html here} for an example of how to use the responses from these end-points to upload a file.
 *
 * Resource response fields for all end-points:
 *
 * - 'formAttributes': JSON object of HTML form attributes to use when uploading the file.
 * - 'formAttributes.action': The value for the 'action' attribute of the form.
 * - 'formAttributes.method': The value for the 'method' attribute of the form.
 * - 'formAttributes.enctype': The value for the 'enctype' attribute of the form.
 * - 'formAttributes.key': The unique key for the file in the S3 bucket. When uploading a file using this policy, you must append your filename to the end of this key.
 * - 'formInputs': JSON object of HTML form input 'name' and 'value' pairs to use when uploading the file.
 * - 'formInputs.acl': Value for the form input named 'acl'.
 * - 'formInputs.Content-Type': Value for the form input named 'Content-Type'.
 * - 'formInputs.key': The unique key for the file in the S3 bucket to be used in the form input named 'key'. When uploading a file using this policy, you must append your filename to the end of this key.
 * - 'formInputs.X-Amz-Credentials': Value for the form input named 'X-Amz-Credentials'.
 * - 'formInputs.X-Amz-Algorithm': Value for the form input named 'X-Amz-Algorithm'.
 * - 'formInputs.X-Amz-Date': Value for the form input named 'X-Amz-Date'.
 * - 'formInputs.Policy': Value for the form input named 'Policy'.
 * - 'formInputs.X-Amz-Signature': Value for the form input named 'X-Amz-Signature'.
 *
 */
Sign in
Available APIs
v1_asignit v1_asset v1_booking v1_booking_client_contact v1_client v1_client_contact v1_depot v1_document_type v1_driver_licence_type v1_equipment v1_files v1_form v1_invoice v1_person v1_project v1_resource v1_sage_50 v1_skill v1_tag v1_upload v1_vehicle v1_works_docket
Methods
  • s3_upload_person_file POST
  • s3_upload_person_image POST
  • s3_upload_person_skill_file POST
    • Help
    Definitions
    T-2.851.1
    Release Notes

    API Release Notes

    Close

    Version T-2.851.1, released on 3/05/2024

    • Third Party API changes
      • Ordering of results has been removed from the booking_person and works_docket_person endpoints.
      • We have optimised the performance of a number of endpoints that had started to slow down.

    Version T-2.850.3, released on 2/05/2024

    • Third Party API changes
      • v1_booking: Added an endpoint for updating booking requirements
      • v1_booking: Added an endpoint for deleting booking requirements

    Version T-2.844.1, released on 15/04/2024

    • Third Party API changes
      • v1_booking: Added an endpoint for posting bookings
      • v1_booking: Added an endpoint for retrieving booking requirements
      • v1_project: Added fields required_skill_ids and required_vehicle_induction_ids when retrieving projects
      • v1_vehicle: Added an endpoint for retrieving vehicle availability
      • v1_person: Added an endpoint for retrieving a person's blocklist

    Version T-2.840.1, released on 02/04/2024

    • Third Party API: Added fields for GET Works_docket_person
      • driver_for_vehicle_id
      • passenger_for_vehicle_id
      • equipment_ids

    Version T-2.816.5, released on 06/12/2023

    • Third Party API: Added fields for GET Person
      • person_start_date
      • person_probation_date
      • person_active_date
      • person_finish_up_date
      • driver_licence_type_name
      • person_driver_licence_number
      • person_driver_licence_date_granted
      • person_driver_licence_expiry_date

    Version T-2.811.3, released on 31/10/2023

    • Third Party API: Depot
      • 'customer_name' has been added to the output of GET depot

    Version T-2.799.1, released on 01/08/2023

    • Third party API changes
      • Added third party API end-point for availability (person leave). The end point can be found in the v1_person api.
      • v1_person:person endpoint person_lng, person_lat
      • v1_booking:booking has new fields added: booking_lng, booking_lat, booking_touches_shifts
      • booking_touches_shifts can be used to match available periods for weekday day/night shifts using a bitwise comparison. The maping can be found in the person availability api

    Version T-2.793.1, released on 15/08/2023

    • Third Party API
      • An API for Assets has been added under V1_asset.

    Version T-2.792.1, released on 11/08/2023

    • Third Party API
      • Booking write access has been added to the third party V1_booking API
      • Currently limited to writing booking person records. Will be expanded to cover equipment, and vehicles shortly.
      • booking_person_put, booking_person_delete added
      • is_non_billable added to the booking person api
      • booking_write_access added to the third party interface. this must be selected for the third party token to be able to write to bookings

    Version T-2.717.1, released on 23/11/2022

    • Third party API end-points
      • Added third party API end-points for retrieving booking vehicles, booking equipment, forms and form submissions. Requires corresponding third party permissions to be switched on - see 'Integrations' > Select a 'Personal' third party.

    Version T-2.693.2, released on 14/9/2022

    • Third party works dockets API
      • Added third party API end-points for retrieving works docket records. Requires the third party permission 'Works Docket Read Access' to be switched on - see 'Integrations' > Select a 'Personal' third party > 'Works docket read access' field.

    Version T-2.692.2, released on 12/9/2022

    • Third party person API: update person
      • A person can now be updated through the third party API using eth PUT method if the token has write permission
      • Not all fields can be updated
      • This will allow Staffd to update existing users with their new release next week

    Version T-2.689.2, released on 5/9/2022

    • Third party person API: Second Emergency Contact
      • A second emergency contact has been added.
      • Added to input of POST person: person_emergency_contact_name2, person_emergency_contact_phone2, person_emergency_contact_relationship2
      • Added to output of GET person: person_emergency_contact_name, person_emergency_contact_phone, person_emergency_contact_relationship, person_emergency_contact_name2, person_emergency_contact_phone2, person_emergency_contact_relationship2

    Version T-2.655.1, released on 6/5/2022

    • Third party booking API
      • Added to output of get booking: client_order_number
      • Added to output of get booking: client_billing_code

    Version T-2.645.4, released on 21/4/2022

    • Staffd integration : bugfix
      • Newly uploaded employees from Staffd would always default to a "candidate" if an avatar image was also uploaded. Uploaded employees will now have the status that is specified
      • Social inclusions, Gender, and Pronouns are now included in Traffio's third party API. It is expected that Staffd will soon include these fields in uploads to Traffio

    Version T-2.542.1, released on 24/08/2021

    • Issuing new access tokens for third parties will now revoke previous access tokens.
    • Made links which are issued to third parties for generating access tokens, expire after 30 days un-viewed and 24 hours once viewed.

    Version T-2.535.1, released on 17/08/2021

    • Traffio support tools
      • This is for the Traffio Support Team
      • Conversations now have dynamic links to the customer, the contact and their conversations
      • Report links have been added, as well as a new teleportation tool
      • fixed bug with creating new methods, and methods nwo have coloured tags

    Version T-2.534.1, released on 16/08/2021

    • Internal 3rd party integrations
      • You can setup access to your Traffio data using the API by creating your own 'Third Party' integration. See the 'Integrations' main menu (moved from 'My Company').
      • Your integrations are restricted to reading your data while Traffio approved integrations will have limited ability to read and write to your data depending on their requirements.
      • You have full control of which integrations can access your data.

    Version T-2.490.1, released on 14/05/2021

    • Added ability to upload a person's profile image, documents and skill-documents via the third party API.

    Version T-2.360.1, released on 11/05/2020

    • Third Party API
      • Third party API end points have been added for vehicles and equipment
      • API has also been opened up to allow third parties to update ODO readings and schedules of service
      • Vehicle issues may also be reported and maintained through the third party api

    Version T-2.330.1, released on 6/2/2020

    • Third Party API
      • Released today is the Traffio third party API for external software to hook into. You can allow external software vendors to make use of this API by generating a token for them through My Company > Integrations.
      • The first third party software available through the platform is Actiond. Link: https://Actiond.io
      • Actiond provides surveys which gauge client and employee satisfaction
    POST s3_upload_person_file
    /api_third_party/v1_upload/s3_upload_person_file
    @return string Returns form attributes required to upload the file in JSON format.
    Field Description
    The MIME file type of the file. Eg
    The ID of the resource that the file relates to.
      
    POST s3_upload_person_image
    /api_third_party/v1_upload/s3_upload_person_image
    @return string Returns form attributes required to upload the file in JSON format.
    Field Description
    The MIME file type of the file. Eg
    The ID of the resource that the file relates to.
      
    POST s3_upload_person_skill_file
    /api_third_party/v1_upload/s3_upload_person_skill_file
    @return string Returns form attributes required to upload the file in JSON format.
    Field Description
    The MIME file type of the file. Eg
    The ID of the person resource that the file relates to.
    The ID of the skill resource that the file relates to.