Expand Drawer

Teams

GET

/trestle/odata/Teams

GET

/trestle/rets/search?SearchType=Teams&Class=Teams

info icon

TeamKey is the primary key and uniquely identifies records in the Teams resource.

info icon

The following fields are considered InKeyIndex fields and may be queried in batches up to 300,000 at a time: ModificationTimestamp, TeamKey, TeamLeadKey, TeamLeadMlsId.

Fields

Field Type Size Description
HumanModifiedYN Boolean HumanModifiedYN
ModificationTimestamp InKey DateTimeOffset The date/time the roster (team or office) record was last modified.
OfficeKey String 20 OfficeKey
OriginalEntryTimestamp DateTimeOffset The date/time the roster (team or office) record was originally input into the source system.
OriginatingSystemID String 25 The RESO Unique Organization Identifier's (UOI) OrganizationUniqueId of the originating record provider. The originating system is the system with authoritative control over the record (e.g., the name of the MLS where the team was input). In cases where the originating system was not where the record originated (the authoritative system), see the Originating System fields.
OriginatingSystemKey String 255 The system key, a unique record identifier, from the originating system. The originating system is the system with authoritative control over the record (e.g., the MLS where the team was input). There may be cases where the source system (how the record is received) is not the originating system. See Source System Key for more information.
OriginatingSystemName String 255 The name of the originating record provider, most commonly the name of the MLS. The place where the team is originally input. The legal name of the company.
OriginatingSystemSubName String 255 OriginatingSystemSubName
OriginatingSystemTeamLeadKey String 255 OriginatingSystemTeamLeadKey
Permission ListingPermission 8000 Permission
RecordSignature Int32 4 RecordSignature
SocialMediaType SocialMediaType Enum A list of types of sites or social media that the team Uniform Resource Locator (URL) or ID is referring to (e.g., website, blog, Facebook, Twitter, LinkedIn, Instagram).
SocialMediaTypeUrl String 8000 SocialMediaTypeUrl
SourceSystemID String 25 The RESO Unique Organization Identifier's (UOI) OrganizationUniqueId of the source record provider. The source system is the system from which the record was directly received. In cases where the source system was not where the record originated (the authoritative system), see the Originating System fields.
SourceSystemKey String 255 The system key, a unique record identifier, from the source system. The source system is the system from which the record was directly received. In cases where the source system was not where the record originated (the authoritative system), see the Originating System fields.
SourceSystemName String 255 The name of the team record provider. The system from which the record was directly received. The legal name of the company.
SyndicationFilterValue String 255 SyndicationFilterValue
SyndicationPrimaryOSN String 500 SyndicationPrimaryOSN
TeamAddress1 String 50 The street number, direction, name and suffix of the team.
TeamAddress2 String 50 The unit/suite number of the team.
TeamCarrierRoute String 9 The group of addresses to which the U.S. Postal Service (USPS) assigns the same code to aid in mail delivery. For the USPS, these codes are 9 digits: 5 numbers for the ZIP Code, one letter for the carrier route type, and 3 numbers for the carrier route number.
TeamCity String 50 The city of the team.
TeamCountry Country Enum The country abbreviation in a postal address.
TeamCountyOrParish String 50 The county or parish in which the team is addressed.
TeamDescription String 1024 A description or marketing information about the team.
TeamDirectPhone String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamEmail String 80 The email address of the team.
TeamFax String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamKey Key InKey String 20 A system unique identifier. Specifically, in aggregation systems, the TeamKey is the system unique identifier from the system where the record was retrieved.
TeamKeyNumeric Int64 10 TeamKeyNumeric
TeamLeadKey InKey String 20 The unique system identifier of the team's lead member.
TeamLeadKeyNumeric Int64 10 TeamLeadKeyNumeric
TeamLeadLoginId String 25 The ID used to log on to the MLS system.
TeamLeadMlsId InKey String 25 The local, well-known identifier for the team lead. This value may not be unique, specifically in the case of aggregation systems, and it should be the identifier from the original system.
TeamLeadNationalAssociationId String 25 The national association ID of the team lead (i.e., NRDS number in the U.S.).
TeamLeadStateLicense String 50 The license of the team lead. Multiple licenses should be separated with a comma and space.
TeamLeadStateLicenseState StateOrProvince Enum The state in which the team lead is licensed.
TeamMobilePhone String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamName String 255 The name under which the team operates. If a business, this may be a DBA (doing business as).
TeamOfficePhone String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamOfficePhoneExt String 10 The extension of the given phone number, if applicable.
TeamPostalCode String 10 The postal code of the team.
TeamPostalCodePlus4 String 4 The four-digit extension of the U.S. Zip Code.
TeamPreferredPhone String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamPreferredPhoneExt String 10 The extension of the given phone number, if applicable.
TeamStateOrProvince StateOrProvince Enum The state or province in which the team is addressed.
TeamStatus TeamStatus Enum Determines whether the account is active, inactive or under disciplinary action.
TeamTollFreePhone String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamVoiceMail String 16 North American 10-digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
TeamVoiceMailExt String 10 The extension of the given phone number, if applicable.