I have create PNR using sabre rest api. Is there any way to cancel or delete this pnr through the api. I am using version v2.2.0 and mode "create".
It depends on the data your PNR has. There is no way to cancel a whole PNR, it will be purged by the system. You cancel segments instead. At the moment Sabre services that cancel segments can be used with SOAP and session tokens.
Related
I am using DocuSign REST API 3.0 to integrate with my app.
After a DocuSign envelope is voided, if I invoke EnvelopesApi.ListStatusChangesAsync for the envelope, I get back an EnvelopesInformation object, which shows both a VoidedDateTime and a VoidedReason property. This is exactly what I need to update my database but all the documentation tells me I should implement
a webhook to receive status updates instead of invoking the API, so I implemented the webhook.
However, when DocuSign invokes my webhook after I void an envelope, I get an DocuSignEnvelopeInformation object from DocuSign, which does not appear to have a VoidedDateTime or Voided property. There is a VoidedReason property, and there are properties for other status dates, such as Created and Sent. Why no Voided property?
What this means is that after the webhook is invoked (and updates my database with incomplete information), I still have to invoke the API to get the VoidedDateTime into my database. Did I just waste my time implementing the webhook? Or am I missing something?
You should explicitly select Envelope Voided Reason checkbox in your Custom Connect configuration. Once this property is selected then you will be able to know the reason why this envelope was Voided.
Webhook is a notification system, where it will notify your System with some data/metadata about the envelope, and if that data does not seem sufficient for your requirement then you need to use API to pull the rest of the data. If Webhook is not available then you need to do a Polling mechanism using some scheduler to keep polling DocuSign after certain interval which does not seem to be a good design and not very scalable. So Webhook design helps your system to know when to call DocuSign platform.
Please note, it seems you are using SOAP API, but I would recommend to implement a new API integration with DocuSign's Rest API as it will have latest features which might be missing from SOAP API.
I'm adding a support of CyberSource to our system and just got new requirement about 3D Secure support.
I've already implemented some flows using CyberSource REST API:
Payments
Card tokenisation via Flexible token
I'm a little bit confused, because I can't find any information about implementation of Payer Authentication in conjunction with the REST integration. All I found is the documentation for Simple Order API and SCMP API.
Am I missing something? Am I supposed to use any of the aforementioned docs or there is some separate document for REST API? Or I should use different integration method instead of REST?
Update 6-14-18: The payer authentication (3-D Secure) is now available with the REST API.
The payer authentication services are not available through the REST API at this time. I know they will be, but don't know when.
The only other option is using the SOAP API (SOAP Toolkit) or pre-built client (Simple Order API). SCMP is a legacy API and should not be used.
I am creating a batch processing application to process PNRs from multiple PCCs using Sabre soap APIs. The application needs to access PNRs from different PCCs. The Sabre API documentation mentions that you can access PNRs created in a PCC only through the token created in that PCC. The problem is, I would not know the PCC of a PNR till I call the GetItinerary (ReservationRQ) on that PNR. I want to know if we can create an EPR in one PCC or IPCC that can have access to PNRs created in other PCCs so that I can maintain only one token in my application.
To be more specific,I am in process of writing following application logic
The users submit PNRs for processing (Amendments)
The front-end application queues the PNRs in a database table
The batch processing application picks up the PNR
Retrieves PNR details from Sabre using GetReservationRQ)
Batch application processes PNR as per the instructions provided by the user
Repeat steps 4 to 5 for each PNR
Any help is greatly appreciated.
Please let know if you need more detail.
You do can retrieve PNRs from different PCCs using one webservice credentials. An admin will be able to manage the user access to those PCCs setting the branch access from your IPCC.
Hope this helps.
P.
You need to first branch those PCCs in order to access them. If this is the case you can use ContextChangeLLSRQ (Gui equivalent of AAA) to access and operate on other PCCs
What is the impetus for the author of https://github.com/firebase/functions-samples/blob/master/fcm-notifications/functions/index.js Line 74 to use a Legacy API?
Put another way, is it possible to use Firebase FCM non-legacy API to achieve the same outcome?
I checked with the author of that sample. Back when the sample was created, what is now called the legacy API, was the best API available.
When the new v1 API was released we looked into upgrading the sample to use that. But (as Umar commented) since the new API no longer support sending to multiple tokens with one call, that upgrade got deprioritized after some other tasks.
I recommend that you file a bug on the Github repo, to get the sample updated to use the latest API. I'd also recommend filing a feature request to get "sending to multiple tokens in one call" back into the new FCM API, since it seems like a rather useful feature.
Update
It seems that so-called multi-cast send operations are coming to the V1 API. From an #AskFirebase video about FCM:
We are planning to add a multicast feature to HTTP V1 that will allow you to send to multiple tokens in a single API request.
Currently I am able to read Sabre Profiles using EPS through Sabre Scribe. But how do I get to send other RQ (like PriceItinerary, GetReservationRQ) and get RS through Sabre scribe? Any ideas?? Thanks...
To my knowledge the only Web Services information available in in Sabre Red is Sabre Profile data.
I believe you would need to use a Sabre Red App to access any other web services data from Sabre Red. You can use the native search commands in Sabre Red using Scribe to accomplish many of the same tasks, however (e.g. WPNI entries).