About updating API

Please sign in to leave a comment.

• 

  Travis Depuy

  Hey Pradeep!

  1. OAuth - Great question! We already have it. Just released in December. Check the release details here, or the docs here.
  2. It sounds like you have properties that are populated in the event when the event is created, but those properties are not making out of xMatters in the payload to your listening application? Is that about right? If so, check out the "Include in Outbound Integration" checkbox in the layout of the form. Doc here.

  Let me know how you get on with those. 

  Happy Monday!

     --- Travis

   

  January 23, 2017 16:44

  0
• 

  pradeep kanukuntla

  Hi Travis DePuy,

    Thanks for your updates. I will post a comment after referring your posted URL's.

   

  Thanks

  January 24, 2017 06:15

  0
• 

  pradeep kanukuntla

  Hi Travis DePuy,

          For xMatters OAuth, why should pass username and password in request? If we were removing those two attributes we are getting 401 unauthorized. And even token url is different for different domains. Can there is perticular(single token url for all user's and all domains) token url to generate access token?

          For other details about events, I am satisfied with your URL.

   

  Thanks

  January 24, 2017 07:35

  0
• 

  Travis Depuy

  Hey Pradeep,

      The user information helps determine the level of permissions that should be allowed to the incoming requests. As for the domains, each xMatters instance has a unique url and is tied to the "Company" the instance is for. 

  What are you looking to do with this token?

  Happy Tuesday!

      --- Travis

  January 24, 2017 16:49

  0
• 

  Travis Depuy

  Hey Pradeep,

     Can you clarify this question?

  Can there is perticular(single token url for all user's and all domains) token url to generate access token?

  You will use the GET /oauth/token endpoint to retrieve a token by passing the username, password and client id (and the grant_type of "password"). This will get you a token that you can then use in place of the username and password when you make calls to the XMAPI endpoints by including the token as a Bearer authorization. Example here. The token will expire, but you can use the soon-to-be-expired token to get another token by making another call to GET /oauth/token, but instead of passing the username and password, you would pass the current token. See here.

  I hope that helps clarify. Let me know if anything doesn't make sense.

   

   

  January 25, 2017 04:26

  0
• 

  pradeep kanukuntla

  Hi Travis DePuy,

          My question is, Why token url tied to the "Company" name. Is it possible to exclude "Company" name from that url.

  Thanks 

  January 25, 2017 10:10

  0
• 

  Travis Depuy

  Hey Pradeep. Unfortunately, no. Our architecture right now requires the company. We've run into a few integrations this causes problems with though. Do you have a specific use case or integration in mind? We'd be interested in exploring options. 

  January 25, 2017 17:34

  0
• 

  pradeep kanukuntla

  Hi Travis DePuy,

           Thanks for your updates. Right now i don't have any use case or integration. Sure i will let you inform if i had.

  -->When outbound url triggers, No information related to whom the email was sent to?(is it possible to get?).

  -->Can we set customized responses(other than acknowledge/escalate) for events?

   

   

  Thanks

  January 27, 2017 07:17

  0
• 

  Travis Depuy

  Glad to help.

  1. "Outbound url triggers" - I'm guessing you mean a Notification Response from an outbound integration that runs a script? If so, the callback object will have the user ID of the responder in the "recipient" element. While this doesn't have the email address, you could make an additional XMAPI call to GET /people/{personID}/devices to get the specific email address. 
  2. Yep, you can either "hard code" them in the form, or you can have your POST /trigger API call use a subset of the responses there by passing the UUIDs of the desired responses in the "responses" element of the event payload. 

  Happy Crazy Hat Friday!

  January 27, 2017 16:25

  0
• 

  pradeep kanukuntla

  Hi Travis DePuy,

             Thanks for your updates.

   

   

  January 30, 2017 04:49

  0