We’re happy to announce an online developer support system, available at http://jira.fbsdata.com/, for supporting developers who are building applications using the flexmls API. Using Jira, our issue tracking system, you may now report bugs, ask questions, or suggest features or improvements. You may also see what other issues other developers have submitted, and may vote on issues that others have added that you’d like to see implemented.
If you’re currently developing applications using the flexmls API and would like to submit requests, send an email to firstname.lastname@example.org with your API key in the body of the message, and we’ll send Jira login information to the email address that we have on our records for that API key. If you do not have an API key and would like to join our developer program, you may request one here. Developers who join the developer program after today will automatically receive Jira credentials, so there’s only a need to contact us if you do not have a Jira account.
We’re pleased to be able to offer this enhanced level of support and hope it better meets your needs as you develop applications on the flexmls API. Please let us know in the comments or at the API support email address above if you have any questions, comments or concerns regarding this new support system.
We’re happy to announce that these features have been added to the flexmls API:
- IDX API clients may now determine if a field will be visible in a response from the Listings service via a new MlsVisible attribute in the Standard Fields service. This is useful for informing user interface choices; if the MLS doesn’t allow the field’s data to be delivered, then those fields may be hidden throughout the user interface.
- User qualifications such as designations are now retrievable via the Accounts service.
- New sub-services have been added to the System Info service show what account-related metadata is defined for the MLS, which currently includes account designations like e-Pro, etc.
- A Settings attribute is now available in the /my/account service. This returns information about whether the user has restrictions on what may be searched in a SearchRestriction attribute. For example, some users are only allowed to search active listings. If SearchRestriction is empty, the user may search any field. Currently, two search restrictions are supported: MlsStatus and PostalCode. The API client may use these settings to inform what search options are available in the application’s user interface.
- IDs have been added to individual contact information items in the Accounts service. This may be used by client applications that wish to refer to contact information via ID for storage for later use instead of storing the actual contact information directly.
Please let us know if you have any questions or problems.