TeamDynamix API/Web Services Overview

Summary

This article is intended to provide instructions for how to access the TeamDynamix API/Web Services documentation and other general API-related information. It is not intended to describe how to use, call or otherwise explain this documentation.

How do I access the API/Web Services documentation?

TeamDynamix RESTful Web API Documentation

The TeamDynamix RESTful Web API information is located below. For SaaS customers, replace yourTeamDynamixDomain with your actual TeamDynamix domain (eg: myschool.teamdynamix.com) to view the documentation.

  • SaaS Production: https://yourTeamDynamixDomain/TDWebAPI/
  • SaaS Sandbox: https://yourTeamDynamixDomain/SBTDWebAPI/
  • Installed Environments: https://yourTeamDynamixDomainAndPath/TDWebAPI/

These are the preferred APIs to use and will be continuously maintained and expanded going forwards.

Usage

When using the API, you should access it using your school's TeamDynamix domain substituted in place of yourTeamDynamixDomain. The URLs below work on the example where a school's TeamDynamix domain is abcuniversity.teamdynamix.com.

Production API Access

The production API URL will be abcuniversity.teamdynamix.com/TDWebApi/ when making API calls. The /TDWebApi/ in the URL is what signifies production (no SB prefix before TDWebApi).

Sandbox API Access

The sandbox API URL will be abcuniversity.teamdynamix.com/SBTDWebApi/ when making API calls. The /SBTDWebApi/ in the URL is what signifies sandbox (a SB prefix before TDWebApi).

Request Size Limits

The RESTful Web API has a global 4MB request size limit. This impacts all requests. Examples of scenarios which might be impacted (non-exhaustive list):

  1. Requests with file attachments
  2. POST / PUT / PATCH Requests with large JSON bodies

Again, any request exceeding 4MB in size will be rejected. If this impacts your API usage you may need to investigate the following workarounds:

  • Compress/zip file attachments being sent as attachments. Or, in addition to compression, chunk the files into multiple archive files.
  • Split up POST / PUT / PATCH requests into additional, smaller calls to achieve the same result.
  • If a large JSON body is happening due to a single large description/comment for an item, consider attaching that description/comment as a file attachment instead. You could then compress that file attachment before uploading.

Legacy SOAP Web Services Documentation

For documentation on our legacy, SOAP Web Services, you will need to log into our Community site. You may need to register for an account first. Once you have successfully registered for a Community account and signed in, click the Developers link in the bottom-right corner. After clicking the Developers link, click the SOAP Services link in the main page.

100% helpful - 1 review

Details

Article ID: 579
Created
Thu 10/31/13 10:44 AM
Modified
Fri 1/4/19 10:55 AM