Build with IDX Broker Forums Enhancement Requests Request: Pull Clients Domain Name via the API

Tagged: 

Viewing 3 reply threads
  • Author
    Posts
    • imFORZA
      Participant
      Post count: 70

      Would like the ability to pull the clients domain information with the API:

      Client main domain: domain.com
      Default IDX domain: INSTALLNAME.idxbroker.com
      Custom subdomain: CUSTOM.domain.com

      This would be extremely useful for automation tasks, such as verifying the CNAME was properly setup for a client.

      2 ratings, 2 votes2 ratings, 2 votes (+2 rating, 2 votes, rated)
      You need to be a registered member to rate this post.
      Loading...
    • idxbroker
      Keymaster
      Post count: 179

      The systemlinks API method returns current pages and the domain approved for the account would be in these links. So the requested information could be inferred.

      Example: {“uid”:”1234-9876″,”name”:”Address”,”url”:”http:\/\/CUSTOM.domain.com\/idx\/search\/address”,”category”:”search”,”systemresults”:false}

      The main domain is there and if the CNAME was not applied it would return:

      {“uid”:”1234-9876″,”name”:”Address”,”url”:”http:\/\/domain.idxbroker.com\/idx\/search\/address”,”category”:”search”,”systemresults”:false}

      Since INSTALLNAME is the domain you can predict the default domain even if the Custom subdomian is set.

      Does this not satisfy the information needed?

      2 ratings, 2 votes2 ratings, 2 votes (+2 rating, 2 votes, rated)
      You need to be a registered member to rate this post.
      Loading...
    • imFORZA
      Participant
      Post count: 70

      While you are correct I can use the current systemlinks API method to get the current systemlinks which include the domain. However, I would then need to limit the given results to one systemlink and strip out the rest of the known url just to get the domain name. That just seems like it could lead to future issues. What if in the future the systemlinks change? Seem Unlikely? Why would I as a developer want to risk it. I would need to re-code anytime they change. Having a separate and simple API call that only supplies the domains would be a much nicer solution.

      Example of how this might work:

      Assuming the client has a custom subdomain setup called “mysubdomain.domain.com”:

      API CALL: https://api.idxbroker.com/clients/domains

      Sample Result:
      {"installname":"mysubdomain", "clientdomain":"domain.com", "defaultidxdomain":"mysubdomain.idxbroker.com", "customidxdomain":"mysubdomain.domain.com"}

      Maybe having a filter so I can limit the results to just the domain I want, ie. “clientdomain”. Also notice how my example results did not have http:// or https://. I don’t think the API should be outputting urls with http://, but use // instead.

      2 ratings, 2 votes2 ratings, 2 votes (+2 rating, 2 votes, rated)
      You need to be a registered member to rate this post.
      Loading...
    • Nick Leech
      Keymaster
      Post count: 183

      This enhancement has now been officially requested!

      2 ratings, 2 votes2 ratings, 2 votes (+2 rating, 2 votes, rated)
      You need to be a registered member to rate this post.
      Loading...
Viewing 3 reply threads
  • You must be logged in to reply to this topic.